Skip to content

FE-704: Sync planning after multi-chat substrate + V2 plumbing #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kostandinang merged 2 commits into from
May 8, 2026
Merged

FE-704: Sync planning after multi-chat substrate + V2 plumbing #100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b59ddee
FE-704: Sync planning after multi-chat substrate + V2 plumbing
kostandinang May 7, 2026
42c109e
FE-704: Use stable side-chat trigger references
kostandinang May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/archive/PLAN_HISTORY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,4 +158,12 @@ Archived out of `memory/PLAN.md` during design-doc reconciliation once the live

- 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.

## 2026-05-07 Sync Archive

Archived out of `memory/PLAN.md` after FE-697 multi-chat substrate landed and FE-673 side-chat V2 plumbing reached branch-complete. Three older completed entries rotated out to keep the live ledger at the last three items.

- 2026-04-30 — **FE-639 relation-first observer capture first cut** — eligible answered turns enter one background observer-capture backlog, observer prompts use compact existing-knowledge anchors, observer output persists validated graph-delta relationship candidates, and accepted review grounding refs reuse the same conservative relation policy. Verified: `npm run verify`. Watch: A66 remains open until corpus/manual graph-review proves edge precision and density are useful.
- 2026-04-29 — **Workflow ownership extraction (FE-616)** — workflow projector extraction, turn-response transition extraction, chat-route transition/application extraction, and phase-close / force-close write-path ownership now live behind runtime-owned seams. Verified: `npm run verify`. Unblocks continuous workspace.
- 2026-04-27 — **Runtime JSON payload hardening** — Express API parsing now accepts chat-sized request bodies above the default parser ceiling and returns a JSON 413 response instead of Express HTML when a payload exceeds the app limit. Verified: `npm run verify`. Watch: if real chat requests still exceed the 5 MB limit, investigate client history / tool-result pruning rather than only raising the ceiling.

Use `memory/PLAN.md` for the live frontier only.
Loading
Loading