mirror of
https://github.com/vitorpamplona/amethyst.git
synced 2026-08-10 08:27:04 +00:00
Vitor PamplonaandClaude Opus 4.8
ac1ca888c7
A refounded Concord community (CORD-06 rotates community_root + bumps the epoch) keeps its pre-refounding messages under the prior epoch's derived Chat Plane stream key. The client only ever fetches the current epoch, so older history is invisible and the feed says "All caught up". Add the diagnostics to reach it: - `amy concord import` — fetch this account's own kind-13302 list, decrypt it, and upsert every community WITH its heldRoots (the prior-epoch access roots Amethyst persists across Refoundings). Decrypts against the account identity, not signer.pubKey (which for a bunker is the ephemeral transport key, not the self-encryption peer). - `amy concord read <community> <channel> --epoch <n> [--root <hex>]` — read a prior epoch's Chat Plane; the root auto-resolves from the stored heldRoots when --root is omitted. Output includes the epoch + derived plane. - StoredCommunity.heldRoots persistence. Verified live against Soapbox #nostrhub: epoch 0 (a held root) returns 7 messages the app never shows; epoch 2 (current) returns 2 — reproducing the gap and confirming heldRoots-walking recovers the history. Design for the in-app fix (walk heldRoots on the read side) lives in commons/plans/2026-07-17-concord-epoch-walking-backfill.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>