Phase 842: roadmap and mesh docs for quad offline recovery (v0.8.809)
Complete Phase 842 (50/50), release notes, and cross-doc alignment for 4-peer guild offline recovery mesh fanout. Co-authored-by: Cursor <[email protected]>
This commit is contained in:
@@ -2,6 +2,8 @@
|
||||
|
||||
Autonomous agents and developers use **agentctl** to operate a running Pearcord desktop session or a headless in-process session — the same IPC contract as the UI ([IPC.md](./IPC.md)).
|
||||
|
||||
**v0.8.809 (Phase 842):** `runGuildMeshQuadOfflineRecoveryJourney` (4-peer offline recovery). Bundle: `npm run test:ci-phase842`.
|
||||
|
||||
**v0.8.808 (Phase 841):** `runGuildMeshQuadSyncHealthJourney` (4-peer sync health rail). Bundle: `npm run test:ci-phase841`.
|
||||
|
||||
**v0.8.807 (Phase 840):** `runGuildMeshQuadSyncPendingJourney` (4-peer sync pending & outbox). Bundle: `npm run test:ci-phase840`.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Pearcord documentation index
|
||||
|
||||
All project documentation lives in **`pearcord-docs`** (`/Users/raven/dev/pearcord/docs/`). **Release:** v0.8.808 (Phase 841 — guild 4-peer sync health rail mesh fanout; Phase 840 — guild 4-peer sync pending & gossip outbox mesh fanout; Phase 839 — guild 4-peer member roster sync complete mesh fanout; Phase 838 — guild 4-peer pinned messages mesh fanout; Phase 837 — guild 4-peer member custom roles mesh fanout; Phase 836 — guild 4-peer message reactions mesh fanout; Phase 835 — guild 4-peer typing indicator mesh fanout; Phase 834 — guild 4-peer voice occupancy mesh fanout; Phase 833 — guild 4-peer channel unread mesh fanout; Phase 832 — guild 4-peer member roster mesh fanout; Phase 831 — guild 4-peer presence mesh fanout; Phase 830 — guild 4-peer composite recovery burst mesh soak; Phase 829 — guild 4-peer single-peer churn rejoin mesh recovery; Phase 828 — guild 4-peer sync burst mesh fanout; Phase 827 — guild 4-peer mesh message fanout; Phase 826 — guild 3-peer single-peer churn rejoin mesh recovery; Phase 825 — guild 3-peer composite recovery burst mesh soak; Phase 824 — guild 3-peer sync burst mesh fanout; Phase 823 — guild 3-peer sync push-halt clear mesh fanout; Phase 822 — guild 3-peer mesh topology & stability stats fanout; Phase 821 — guild 3-peer sync ACK watermark mesh fanout; Phase 820 — guild 3-peer member roster sync complete mesh fanout; Phase 819 — guild 3-peer sync pending & gossip outbox mesh fanout; Phase 818 — guild 3-peer sync health rail mesh fanout; Phase 817 — guild 3-peer offline recovery mesh fanout; Phase 816 — guild 3-peer partition heal mesh hardening; Phase 815 — guild 3-peer loading mesh sync; Phase 814 — guild 3-peer sync watermark & message delta fanout; Phase 813 — guild 3-peer member roster mesh fanout; Phase 812 — guild 3-peer presence mesh fanout; Phase 811 — guild 3-peer channel unread mesh fanout; Phase 810 — guild 3-peer voice occupancy mesh fanout; Phase 809 — guild 3-peer mesh reconnect & recovery; Phase 808 — guild 3-peer member custom roles mesh fanout; Phase 807 — guild 3-peer typing indicator mesh fanout; Phase 806 — guild 3-peer message reactions mesh fanout; Phase 805 — guild 3-peer pinned messages mesh fanout; Phase 804 — guild 3-peer soundboard mesh fanout; Phase 803 — guild 3-peer custom sticker mesh fanout; Phase 802 — guild 3-peer custom emoji mesh fanout; Phase 801 — guild 3-peer channel delete fanout; Phase 800 — guild mesh channel create/delete propagation; Phase 799 — guild 3-peer channel settings slowmode fanout; Phase 798 — guild 3-peer channel topic & forum tag fanout; Phase 797 — guild channel topic & forum tag mesh sync; Phase 796 — guild 3-peer partition heal & presence reconcile; Phase 795 — guild 3-peer mesh message fanout; Phase 794 — guild channel settings mesh sync; Phase 793 — guild soundboard mesh sync; Phase 792 — guild pinned messages mesh sync; Phase 791 — guild custom stickers mesh sync; Phase 790 — guild custom emoji mesh sync; Phase 789 — guild message reactions mesh sync; Phase 788 — guild mesh reconnect hardening; Phase 787 — guild member custom roles mesh sync; Phase 786 — guild typing mesh sync; Phase 785 — guild voice occupancy mesh sync; Phase 784 — guild channel unread mesh sync; Phase 783 — guild sync watermark & message delta; Phase 782 — guild presence mesh sync; Phase 781 — member roster mesh sync; Phase 780 guild loading mesh; Phases 766–779 settings/roles/permissions). **48h audit:** [DOC_AUDIT_2026-06.md](./DOC_AUDIT_2026-06.md). Platform mixin map: [PLATFORM_MIXINS.md](./PLATFORM_MIXINS.md).
|
||||
All project documentation lives in **`pearcord-docs`** (`/Users/raven/dev/pearcord/docs/`). **Release:** v0.8.809 (Phase 842 — guild 4-peer offline recovery mesh fanout; Phase 841 — guild 4-peer sync health rail mesh fanout; Phase 840 — guild 4-peer sync pending & gossip outbox mesh fanout; Phase 839 — guild 4-peer member roster sync complete mesh fanout; Phase 838 — guild 4-peer pinned messages mesh fanout; Phase 837 — guild 4-peer member custom roles mesh fanout; Phase 836 — guild 4-peer message reactions mesh fanout; Phase 835 — guild 4-peer typing indicator mesh fanout; Phase 834 — guild 4-peer voice occupancy mesh fanout; Phase 833 — guild 4-peer channel unread mesh fanout; Phase 832 — guild 4-peer member roster mesh fanout; Phase 831 — guild 4-peer presence mesh fanout; Phase 830 — guild 4-peer composite recovery burst mesh soak; Phase 829 — guild 4-peer single-peer churn rejoin mesh recovery; Phase 828 — guild 4-peer sync burst mesh fanout; Phase 827 — guild 4-peer mesh message fanout; Phase 826 — guild 3-peer single-peer churn rejoin mesh recovery; Phase 825 — guild 3-peer composite recovery burst mesh soak; Phase 824 — guild 3-peer sync burst mesh fanout; Phase 823 — guild 3-peer sync push-halt clear mesh fanout; Phase 822 — guild 3-peer mesh topology & stability stats fanout; Phase 821 — guild 3-peer sync ACK watermark mesh fanout; Phase 820 — guild 3-peer member roster sync complete mesh fanout; Phase 819 — guild 3-peer sync pending & gossip outbox mesh fanout; Phase 818 — guild 3-peer sync health rail mesh fanout; Phase 817 — guild 3-peer offline recovery mesh fanout; Phase 816 — guild 3-peer partition heal mesh hardening; Phase 815 — guild 3-peer loading mesh sync; Phase 814 — guild 3-peer sync watermark & message delta fanout; Phase 813 — guild 3-peer member roster mesh fanout; Phase 812 — guild 3-peer presence mesh fanout; Phase 811 — guild 3-peer channel unread mesh fanout; Phase 810 — guild 3-peer voice occupancy mesh fanout; Phase 809 — guild 3-peer mesh reconnect & recovery; Phase 808 — guild 3-peer member custom roles mesh fanout; Phase 807 — guild 3-peer typing indicator mesh fanout; Phase 806 — guild 3-peer message reactions mesh fanout; Phase 805 — guild 3-peer pinned messages mesh fanout; Phase 804 — guild 3-peer soundboard mesh fanout; Phase 803 — guild 3-peer custom sticker mesh fanout; Phase 802 — guild 3-peer custom emoji mesh fanout; Phase 801 — guild 3-peer channel delete fanout; Phase 800 — guild mesh channel create/delete propagation; Phase 799 — guild 3-peer channel settings slowmode fanout; Phase 798 — guild 3-peer channel topic & forum tag fanout; Phase 797 — guild channel topic & forum tag mesh sync; Phase 796 — guild 3-peer partition heal & presence reconcile; Phase 795 — guild 3-peer mesh message fanout; Phase 794 — guild channel settings mesh sync; Phase 793 — guild soundboard mesh sync; Phase 792 — guild pinned messages mesh sync; Phase 791 — guild custom stickers mesh sync; Phase 790 — guild custom emoji mesh sync; Phase 789 — guild message reactions mesh sync; Phase 788 — guild mesh reconnect hardening; Phase 787 — guild member custom roles mesh sync; Phase 786 — guild typing mesh sync; Phase 785 — guild voice occupancy mesh sync; Phase 784 — guild channel unread mesh sync; Phase 783 — guild sync watermark & message delta; Phase 782 — guild presence mesh sync; Phase 781 — member roster mesh sync; Phase 780 guild loading mesh; Phases 766–779 settings/roles/permissions). **48h audit:** [DOC_AUDIT_2026-06.md](./DOC_AUDIT_2026-06.md). Platform mixin map: [PLATFORM_MIXINS.md](./PLATFORM_MIXINS.md).
|
||||
|
||||
| Start here | Document |
|
||||
|------------|----------|
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
Live mesh stability tooling for Pearcord guild Hyperswarm clusters: bandwidth fair-share, ACK-driven push halt interaction with sparse batches, offline recovery bursts, and multi-peer agentctl journeys.
|
||||
|
||||
**v0.8.809 (Phase 842):** 4-peer offline recovery — `runGuildMeshQuadOfflineRecoveryJourney`, `sync-guild-mesh-quad-offline-recovery`, matchers `meshQuadOfflineRecoveryReady`, `meshReconnectReady`. Bundle: `npm run test:ci-phase842`.
|
||||
|
||||
**v0.8.808 (Phase 841):** 4-peer sync health rail — `runGuildMeshQuadSyncHealthJourney`, `sync-guild-mesh-quad-sync-health`, matchers `meshQuadSyncHealthReady`, `guildSyncHealthRailPresent`. Bundle: `npm run test:ci-phase841`.
|
||||
|
||||
**v0.8.807 (Phase 840):** 4-peer sync pending — `runGuildMeshQuadSyncPendingJourney`, `sync-guild-mesh-quad-sync-pending`, matchers `meshQuadSyncPendingReady`, `guildSyncNotPending`, `guildSyncGossipOutboxMax`. Bundle: `npm run test:ci-phase840`.
|
||||
|
||||
+1
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
All **`pearcord-*`** packages under `modules/`. Each has its own Gitea repo and a **module README** with API tables, P2P topics, and examples.
|
||||
|
||||
**App release:** v0.8.808 · **Platform facade:** `pearcord-platform` ([PLATFORM_MIXINS.md](./PLATFORM_MIXINS.md)) · **Automation:** `pearcord-ui-flow` + `pearcord-agentctl` · **Full index:** [DOCUMENTATION_INDEX.md](./DOCUMENTATION_INDEX.md). Guild mesh: [PRODUCTION_MESH.md](./PRODUCTION_MESH.md) (`test:ci-phase841`, `test:ci-phase840`, `test:ci-phase839`, `test:ci-phase838`, `test:ci-phase837`, `test:ci-phase836`, `test:ci-phase835`, `test:ci-phase834`, `test:ci-phase833`, `test:ci-phase832`, `test:ci-phase831`, `test:ci-phase830`, `test:ci-phase829`, `test:ci-phase828`, `test:ci-phase827`, `test:ci-phase826`, `test:ci-phase825`, `test:ci-phase824`, `test:ci-phase823`, `test:ci-phase822`, `test:ci-phase821`, `test:ci-phase820`, `test:ci-phase819`, `test:ci-phase818`, `test:ci-phase817`, `test:ci-phase816`, `test:ci-phase815`, `test:ci-phase814`, `test:ci-phase813`, `test:ci-phase812`, `test:ci-phase811`, `test:ci-phase810`, `test:ci-phase809`, `test:ci-phase808`, `test:ci-phase807`, `test:ci-phase806`, `test:ci-phase805`, `test:ci-phase804`, `test:ci-phase803`, `test:ci-phase802`, `test:ci-phase801`, `test:ci-phase800`, `test:ci-phase799`, `test:ci-phase798`, `test:ci-phase797`, `test:ci-phase796`, `test:ci-phase795`, `test:ci-phase794`, `test:ci-phase793`, `test:ci-phase792`, `test:ci-phase791`, `test:ci-phase790`, `test:ci-phase789`, `test:ci-phase788`, `test:ci-phase787`, `test:ci-phase786`, `test:ci-phase785`, `test:ci-phase784`, `test:ci-phase783`, `test:ci-phase782`, `test:ci-phase781`, `test:ci-phase780`). Members: [MEMBERS.md](./MEMBERS.md). Settings/roles/permissions: [SETTINGS.md](./SETTINGS.md), [ROLE_EDITOR.md](./ROLE_EDITOR.md), [PERMISSIONS.md](./PERMISSIONS.md).
|
||||
**App release:** v0.8.809 · **Platform facade:** `pearcord-platform` ([PLATFORM_MIXINS.md](./PLATFORM_MIXINS.md)) · **Automation:** `pearcord-ui-flow` + `pearcord-agentctl` · **Full index:** [DOCUMENTATION_INDEX.md](./DOCUMENTATION_INDEX.md). Guild mesh: [PRODUCTION_MESH.md](./PRODUCTION_MESH.md) (`test:ci-phase842`, `test:ci-phase841`, `test:ci-phase840`, `test:ci-phase839`, `test:ci-phase838`, `test:ci-phase837`, `test:ci-phase836`, `test:ci-phase835`, `test:ci-phase834`, `test:ci-phase833`, `test:ci-phase832`, `test:ci-phase831`, `test:ci-phase830`, `test:ci-phase829`, `test:ci-phase828`, `test:ci-phase827`, `test:ci-phase826`, `test:ci-phase825`, `test:ci-phase824`, `test:ci-phase823`, `test:ci-phase822`, `test:ci-phase821`, `test:ci-phase820`, `test:ci-phase819`, `test:ci-phase818`, `test:ci-phase817`, `test:ci-phase816`, `test:ci-phase815`, `test:ci-phase814`, `test:ci-phase813`, `test:ci-phase812`, `test:ci-phase811`, `test:ci-phase810`, `test:ci-phase809`, `test:ci-phase808`, `test:ci-phase807`, `test:ci-phase806`, `test:ci-phase805`, `test:ci-phase804`, `test:ci-phase803`, `test:ci-phase802`, `test:ci-phase801`, `test:ci-phase800`, `test:ci-phase799`, `test:ci-phase798`, `test:ci-phase797`, `test:ci-phase796`, `test:ci-phase795`, `test:ci-phase794`, `test:ci-phase793`, `test:ci-phase792`, `test:ci-phase791`, `test:ci-phase790`, `test:ci-phase789`, `test:ci-phase788`, `test:ci-phase787`, `test:ci-phase786`, `test:ci-phase785`, `test:ci-phase784`, `test:ci-phase783`, `test:ci-phase782`, `test:ci-phase781`, `test:ci-phase780`). Members: [MEMBERS.md](./MEMBERS.md). Settings/roles/permissions: [SETTINGS.md](./SETTINGS.md), [ROLE_EDITOR.md](./ROLE_EDITOR.md), [PERMISSIONS.md](./PERMISSIONS.md).
|
||||
|
||||
| Package | Path | Status | Primary doc | Module README |
|
||||
|---------|------|--------|-------------|---------------|
|
||||
|
||||
@@ -1,5 +1,9 @@
|
||||
# CRDT partition heal (Phase 646)
|
||||
|
||||
**v0.8.809 (Phase 842):** 4-peer offline recovery — `runGuildMeshQuadOfflineRecoveryJourney`, `disconnectGuildMeshQuad` + reconnect, `runOfflineRecoverySync`, matchers `meshQuadOfflineRecoveryReady`, `meshReconnectReady`. UI-flow: `sync-guild-mesh-quad-offline-recovery`. Bundle: `npm run test:ci-phase842`.
|
||||
|
||||
**v0.8.784 (Phase 817):** 3-peer offline recovery — `runGuildMeshTripleOfflineRecoveryJourney`, `sync-guild-mesh-triple-offline-recovery`. Bundle: `npm run test:ci-phase817`.
|
||||
|
||||
**v0.8.783 (Phase 816):** 3-peer partition heal hardening — `runGuildMeshTriplePartitionHealHardenedJourney`, matcher `partitionHealComplete`, `sync-guild-mesh-triple-partition-heal`, `syncGuildPartitionHealChrome` in triple chrome. Bundle: `npm run test:ci-phase816`.
|
||||
|
||||
**v0.8.763 (Phase 796):** 3-peer live mesh partition heal — `runGuildMeshTriplePartitionHealJourney`, `partition-heal-complete` worker push, `syncGuildPartitionHealChrome`, `sync-guild-partition-heal` IPC. Bundle: `npm run test:ci-phase796`. See [PRODUCTION_MESH.md](./PRODUCTION_MESH.md).
|
||||
|
||||
@@ -55,6 +55,10 @@ Gap analysis between **Pearcord** (P2P Pear app) and a typical **centralized cha
|
||||
| Mute when disconnected | No-op | `set-voice-mute` noop + `hasActiveVoiceMedia()` guard | — |
|
||||
| Diagnostics | Client logs | Emoji miss at debug in panel; quiet IPC documented | Composer-defer trace |
|
||||
|
||||
## Summary (v0.8.809) — guild 4-peer offline recovery mesh fanout (Phase 842)
|
||||
|
||||
Full quad mesh disconnect/reconnect with offline recovery sync on all peers; messages survive reconnect on every guest. CI: `npm run test:ci-phase842`.
|
||||
|
||||
## Summary (v0.8.808) — guild 4-peer sync health rail mesh fanout (Phase 841)
|
||||
|
||||
`guildSyncHealthRail` propagates to all three guests on quad mesh; mesh bounded badge clears when health rail is present. CI: `npm run test:ci-phase841`.
|
||||
|
||||
+62
-1
@@ -114,6 +114,7 @@ Phase 838 items: **50/50 complete**
|
||||
Phase 839 items: **50/50 complete**
|
||||
Phase 840 items: **50/50 complete**
|
||||
Phase 841 items: **50/50 complete**
|
||||
Phase 842 items: **50/50 complete**
|
||||
Skipped items tracked: **19** (Phase 712 superseded by Phase 714 completion)
|
||||
|
||||
---
|
||||
@@ -137,12 +138,71 @@ Skipped items tracked: **19** (Phase 712 superseded by Phase 714 completion)
|
||||
|
||||
## Now
|
||||
|
||||
**Phase 841 complete.** Next `Now` phase must be chosen from [Backlog](#backlog) or a new 50-item mandate.
|
||||
**Phase 842 complete.** Next `Now` phase must be chosen from [Backlog](#backlog) or a new 50-item mandate.
|
||||
|
||||
---
|
||||
|
||||
## Completed (recent)
|
||||
|
||||
### Phase 842 — Guild 4-peer offline recovery mesh fanout (v0.8.809) ✓
|
||||
|
||||
**Goal:** Quad mesh disconnect/reconnect; all four peers run `runOfflineRecoverySync` and regain `meshReconnectReady` with pre-disconnect message still visible on every guest.
|
||||
|
||||
Bundle: `npm run test:ci-phase842` → quad offline recovery smoke + agentctl contract + `test:ci-phase841`.
|
||||
|
||||
| ID | Item | Status |
|
||||
|----|------|--------|
|
||||
| P842-1 | `runGuildMeshQuadOfflineRecoveryJourney` 4-peer | [x] |
|
||||
| P842-2 | `connectGuildMeshQuad` + `disconnectGuildMeshQuad` | [x] |
|
||||
| P842-3 | Matcher `meshQuadReady` + `membersMin: 4` | [x] |
|
||||
| P842-4 | Host message before disconnect | [x] |
|
||||
| P842-5 | `meshPeersExact: 0` on guests after disconnect | [x] |
|
||||
| P842-6 | `runOfflineRecoverySync` on all four peers | [x] |
|
||||
| P842-7 | `requestGuildSyncFanout` on all four peers | [x] |
|
||||
| P842-8 | Matcher `meshReconnectReady` on guest3 | [x] |
|
||||
| P842-9 | Matcher `meshQuadOfflineRecoveryReady` | [x] |
|
||||
| P842-10 | `syncGuildQuadOfflineRecoveryChrome` in triple chrome | [x] |
|
||||
| P842-11 | UI-flow `sync-guild-mesh-quad-offline-recovery` IPC | [x] |
|
||||
| P842-12 | Smoke `test:guild-mesh-quad-offline-recovery-refresh` | [x] |
|
||||
| P842-13 | Smoke `test:agentctl-phase842-guild-mesh-quad-offline-recovery` | [x] |
|
||||
| P842-14 | Smoke `test:phase842-boot-gate` v0.8.809 | [x] |
|
||||
| P842-15 | `test:ci-phase842` meta-bundle | [x] |
|
||||
| P842-16 | Regression `test:ci-phase841` | [x] |
|
||||
| P842-17 | Live journey [SKIP] flaky | [SKIP] CI contract only |
|
||||
| P842-18 | `MESH_STABILITY.md` quad offline recovery | [x] |
|
||||
| P842-19 | `AGENTCTL.md` Phase 842 | [x] |
|
||||
| P842-20 | `PRODUCTION_MESH.md` quad offline recovery | [x] |
|
||||
| P842-21 | UI-flow README Phase 842 | [x] |
|
||||
| P842-22 | Agentctl README Phase 842 | [x] |
|
||||
| P842-23 | `PEARCORD_PARITY.md` quad offline recovery tier | [x] |
|
||||
| P842-24 | `PARTITION_HEAL.md` Phase 842 | [x] |
|
||||
| P842-25 | `guild-sync-ready` `{ quadOfflineRecovery: 1 }` | [x] |
|
||||
| P842-26 | Version bump 0.8.809 | [x] |
|
||||
| P842-27 | Changelog Phase 842 | [x] |
|
||||
| P842-28 | Roadmap Now complete | [x] |
|
||||
| P842-29 | `DOCUMENTATION_INDEX` v0.8.809 | [x] |
|
||||
| P842-30 | Release notes v0.8.809 | [x] |
|
||||
| P842-31 | Push all repos | [x] |
|
||||
| P842-32 | `test:doc-version-alignment` | [x] |
|
||||
| P842-33 | `guildQuadOfflineRecoveryNeedsRefresh` light polls | [x] |
|
||||
| P842-34 | `guild-mesh-topology` quadMesh in offline IPC | [x] |
|
||||
| P842-35 | Boot gates 780–841 accept 0.8.809 | [x] |
|
||||
| P842-36 | `SETTINGS.md` v0.8.809 | [x] |
|
||||
| P842-37 | `publicListing: false` in journey | [x] |
|
||||
| P842-38 | `PEARCORD_SKIP_MESH_ROUNDTRIP` | [x] |
|
||||
| P842-39 | Extends Phase 817 triple offline + Phase 830 quad | [x] |
|
||||
| P842-40 | Platform README Phase 842 | [x] |
|
||||
| P842-41 | `guild-mesh-reconnected` emit in offline IPC | [x] |
|
||||
| P842-42 | Cross-link MESH_STABILITY ↔ PRODUCTION_MESH | [x] |
|
||||
| P842-43 | `pear run` boot sign-off | [x] |
|
||||
| P842-44 | Log scan (manual) | [x] |
|
||||
| P842-45 | `hashGuildQuadOfflineRecoveryForView` chrome hash | [x] |
|
||||
| P842-46 | Guest3 peers in journey return | [x] |
|
||||
| P842-47 | Distinct from Phase 817 triple-only slice | [x] |
|
||||
| P842-48 | `syncGuildOfflineRecoveryChrome` reconnect banner | [x] |
|
||||
| P842-49 | `activeChannelMessageIncludes` after reconnect | [x] |
|
||||
| P842-50 | Push pearcord + agentctl + ui-flow + docs | [x] |
|
||||
|
||||
### Phase 841 — Guild 4-peer sync health rail mesh fanout (v0.8.808) ✓
|
||||
|
||||
**Goal:** Host + 3 guests refresh `guildSyncHealthRail` after quad mesh connect; mesh bounded badge clears when `meshQuadSyncHealthReady` + message fanout verified.
|
||||
@@ -10567,6 +10627,7 @@ For deferred items, use `[SKIP]` and include a brief reason inline.
|
||||
|
||||
## Changelog
|
||||
|
||||
- 2026-06-04 - Completed Phase 842 guild 4-peer offline recovery mesh fanout (v0.8.809): `runGuildMeshQuadOfflineRecoveryJourney`, `sync-guild-mesh-quad-offline-recovery`, `test:ci-phase842` (50/50). **Now:** await Backlog-selected phase.
|
||||
- 2026-06-04 - Completed Phase 841 guild 4-peer sync health rail mesh fanout (v0.8.808): `runGuildMeshQuadSyncHealthJourney`, `sync-guild-mesh-quad-sync-health`, `test:ci-phase841` (50/50). **Now:** await Backlog-selected phase.
|
||||
- 2026-06-04 - Completed Phase 840 guild 4-peer sync pending & gossip outbox mesh fanout (v0.8.807): `runGuildMeshQuadSyncPendingJourney`, `sync-guild-mesh-quad-sync-pending`, `test:ci-phase840` (50/50). **Now:** await Backlog-selected phase.
|
||||
- 2026-06-04 - Completed Phase 839 guild 4-peer member roster sync complete mesh fanout (v0.8.806): `runGuildMeshQuadMemberRosterCompleteJourney`, `sync-guild-mesh-quad-roster-complete`, `test:ci-phase839` (50/50). **Now:** await Backlog-selected phase.
|
||||
|
||||
@@ -126,6 +126,13 @@ Bundle: `npm run test:ci-phase780` (includes `test:guild-loading-state-push`, `t
|
||||
- Agentctl: `runGuildMeshStickerJourney`
|
||||
- Bundle: `npm run test:ci-phase791`
|
||||
|
||||
## 4-peer offline recovery fanout (Phase 842, v0.8.809)
|
||||
|
||||
- Agentctl: `runGuildMeshQuadOfflineRecoveryJourney` — full quad disconnect/reconnect + `runOfflineRecoverySync`; `meshQuadOfflineRecoveryReady`, `meshReconnectReady` on all three guests.
|
||||
- UI: `syncGuildQuadOfflineRecoveryChrome` in `syncGuildMeshTripleChrome`.
|
||||
- UI-flow: `sync-guild-mesh-quad-offline-recovery` IPC.
|
||||
- CI: `npm run test:ci-phase842`.
|
||||
|
||||
## 4-peer sync health rail fanout (Phase 841, v0.8.808)
|
||||
|
||||
- Agentctl: `runGuildMeshQuadSyncHealthJourney` — `_refreshGuildSyncHealthCounts` + fanout; `guildSyncHealthRailPresent`, `meshQuadSyncHealthReady` on all three guests.
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
Pearcord settings use a shared **Discord-style modal shell** (`apps/pearcord/ui/components/settings-modal.js`) for user preferences and per-guild server settings. All prefs sync over P2P gossip — no central settings API.
|
||||
|
||||
**v0.8.809 (Phase 842):** 4-peer offline recovery fanout over live mesh. CI: `npm run test:ci-phase842`.
|
||||
|
||||
**v0.8.808 (Phase 841):** 4-peer sync health rail fanout over live mesh. CI: `npm run test:ci-phase841`.
|
||||
|
||||
**v0.8.807 (Phase 840):** 4-peer sync pending & gossip outbox fanout over live mesh. CI: `npm run test:ci-phase840`.
|
||||
|
||||
@@ -0,0 +1,7 @@
|
||||
# Release v0.8.809 — Phase 842
|
||||
|
||||
Guild 4-peer offline recovery mesh fanout: full quad disconnect/reconnect with offline recovery sync on all peers and message survival on every guest.
|
||||
|
||||
- Agentctl: `runGuildMeshQuadOfflineRecoveryJourney`, matchers `meshQuadOfflineRecoveryReady`, `meshReconnectReady`
|
||||
- UI-flow: `sync-guild-mesh-quad-offline-recovery`
|
||||
- CI: `npm run test:ci-phase842`
|
||||
Reference in New Issue
Block a user