FE-692: Planning groundwork

docs/archive/PLAN_HISTORY.md

@@ -152,4 +152,10 @@ Archived when Track A (interaction model) completed and the frontier shifted to
 
 - 2026-04-24 — **Workflow ownership extraction** — workflow projector extraction, turn-response transition extraction, chat-route transition/application extraction, and phase-close / force-close write-path ownership landed behind runtime-owned seams.
 
+## 2026-05-05 Sync Archive
+
+Archived out of `memory/PLAN.md` during design-doc reconciliation once the live frontier narrowed to continuous workspace plus only the last three completed items.
+
+- 2026-04-24 — **Distribution hardening release path** — `package.json` declares the Node 22+ engine floor, explicit shipped files, and public scoped publish config; `npm run release` drives release-it at repo root, rebuilds and dry-runs the packaged artifact, and documents npm auth prerequisites. Verified: `npm run verify`. Watch: CI trusted publishing remains intentionally out of scope.
+
 Use `memory/PLAN.md` for the live frontier only.

docs/design/REVISIT_MODULE.md → docs/archive/design/REVISIT_MODULE.md

@@ -1,7 +1,8 @@
 # Knowledge-Graph Revisit Module Design
 
-> Design exploration from 2026-04-12. Referenced by SPEC.md D80.
-> Status: **subsumed 2026-04-30** — the cascade-preview lifecycle (`previewCascade`, `beginRevisit`, `openRevisitThread`, `resolveRevisitItem`, `completeRevisit`) and the per-item walk semantics described here remain valid as the V3 hard-edit path inside the side-chat panel. The **modal secondary thread** described in this doc is replaced by the side-chat panel's secondary-thread mode (see `docs/design/SIDE_CHAT.md` §5.3 and §6.3). For the live frontier authority, prefer `memory/SPEC.md` (D80, D130) and `memory/PLAN.md`.
+> Design exploration from 2026-04-12. Referenced historically by SPEC.md D80.
+> Status: archived. The user-facing revisit/cascade goal remains live, but the side-chat V2/V3 framing and the `revisit_session` persistence shape are superseded by the chat + reconciliation-need substrate in `docs/design/MULTI_CHAT.md` and the later semantic mutation history in `docs/design/PATCH_LEDGER.md`.
+> Canonicality: this is a historical module design note, not the live frontier authority. For what is true now and what should happen next, prefer `memory/SPEC.md` and `memory/PLAN.md`.
 
 ## Shape
 

docs/design/WORKFLOW_OWNERSHIP.md → docs/archive/design/WORKFLOW_OWNERSHIP.md

@@ -1,7 +1,7 @@
 # Workflow Ownership: projection vs transition
 
-> Clarification note for the current planning frontier.
-> Status: explanatory design note, not canonical product truth.
+> Clarification note for the workflow ownership frontier.
+> Status: archived. The read/write ownership split has been implemented; this note is historical design context, not canonical product truth.
 > For live authority, prefer `memory/SPEC.md` and `memory/PLAN.md`.
 > Related design context: `docs/design/state-machines/README.md`.