pearcord/pearcord-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Phase 840: document quad-peer sync pending mesh path (v0.8.807)

Browse Source 
README notes quad sync pending reuses Phase 819 outbox flush on 4-peer mesh.

Co-authored-by: Cursor <[email protected]>
This commit is contained in:
Raven Scott
2026-06-04 04:54:40 -04:00
co-authored by Cursor
parent 83cb583785
commit 0e5b19ab05
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2
View File
@@ -2,6 +2,8 @@
Application facade: one `PearcordPlatform` class that wires identity, database, guild mesh, DMs, invites, voice, discovery, bots, and dozens of feature modules for the Pearcord desktop sidecar and companion. **Mixin sources:** [`mixins/README.md`](mixins/README.md) — `domain/`, `json-export/`, `runtime/{core,mesh,guild-sync,search-discovery,partition-heal,view,voice-dm,features}/`. Architecture: [PLATFORM_MIXINS.md](../../docs/PLATFORM_MIXINS.md). Regenerate after manifest edits: `cd apps/pearcord && npm run regenerate:platform-mixins`. OTA prestage recursively verifies symbols under `mixins/` — [RELEASE.md](../../docs/RELEASE.md#prestage-sync-file-deps).
**Phase 840 (v0.8.807):** Quad-peer sync pending uses Phase 819 gossip outbox flush path on 4-peer mesh. Bundle: `npm run test:ci-phase840`.
**Phase 839 (v0.8.806):** Quad-peer roster sync complete uses Phase 781/820 path on 4-peer mesh. Bundle: `npm run test:ci-phase839`.
**Phase 838 (v0.8.805):** Quad-peer pins use Phase 792/805 pin path on 4-peer mesh. Bundle: `npm run test:ci-phase838`.