[lukemaj]

What: Show Chromeria as a whole app with six Live T3 base parts and scoped Chromeria crystal marks.
Why: Tracked fork work previously floated without the capabilities it extends, and the map could not distinguish existing capabilities from other-project context.
So what: This is PR-B, stacked on PR-A #375 through branch feat/374-holistic-map; the planner owns independent reviews, retargeting to main after A merges, and delivery acceptance.

Requirements and who asked: Implement the maintainer's agreed council design and acceptance contract in #374.
Deleted: No runtime registry join, handwritten origin tokens, Mermaid crystal labels, mobile Map surface, or merged-PR ledger.
Bottleneck: Represent an existing capability truthfully without confusing it with Done or Context, while preserving Mermaid node identity inside subgraphs.
Checked myself: Ran the real parser, compatibility decoder, fold/gaps, mark selector, pinned Mermaid renderer and real docs/map.md fixtures; checked affected contracts/web/server types and targeted formatting/lint.

Refs #374. Implementation is complete; independent reviews and deployment acceptance remain with the planner, so this PR does not auto-close the issue.

Add the exact %% ID: live binding. Contradictory live/context/ref bindings surface through unreadable-ref diagnostics and never resolve as Live or Context. Older snapshots decode missing live as false. Live has no GitHub state, has its own fmLive class and label, and is excluded from untracked gaps.

Draw the six existing T3 capabilities in one subgraph, with one attachment per tracked fork part. Keep OpenBot outside as context. Render the existing Chromeria crystal only in the accessible part list, based on the snapshot's case-insensitive github.com/toolboxmd/chromeria identity, refs present, and neither Live nor Context. Document Live, mark scope and absorption handling; register the added contract test in the carried-edit registry.

Proof on Node v24.13.1:

• vp test run scripts/fork-maintenance.test.ts apps/server/src/issues/featureMap.test.ts apps/web/src/components/featureMap/featureMap.logic.test.ts apps/web/src/components/featureMap/featureMap.mermaid.test.tsx packages/contracts/src/featureMap.test.ts: 5 files, 86 tests passed.
• Subgraph and real-map renderer tests preserve all 28 part node identities, apply all six Live classes, and reject cluster IDs as parts. Actual Mermaid renders in jsdom with SVG layout stubs; this is not browser visual verification.
• vp run --filter '@t3tools/contracts' --filter '@t3tools/web' --filter t3 typecheck: all three packages passed; existing non-failing Effect suggestions remain outside the changed files.
• Targeted vp fmt --check (oxfmt) and vp lint (oxlint): passed without findings. git diff --check: passed.
• node scripts/fork-features.mjs check: fork-features: OK (42 features).
• Committed-candidate fork-stack check follows below.

Surface coverage: the existing Map tab in web and Electron desktop consumes the additive contract; local/remote/tunnel reads keep the same snapshot path. Providers, agent tools and mobile navigation are unchanged. No browser or dev server was started, no live userdata was accessed, and no visual screenshot proof is claimed because browser verification was explicitly not authorized. No versions changed, per repository policy.

Implementation: GPT-6.1-Sol, medium reasoning, Codex harness in T3 Code.

[lukemaj]

PR-B candidate 11508503f199231896bf23cc15a04977ee643306 passes bash scripts/fork-check.sh against freshly fetched upstream: merge base f798cb299ac9eab9d51ef63b5159de14a2b6aa18, fork-features: OK (42 features)., fork-check: OK.

Final focused result: Test Files 5 passed (5) and Tests 86 passed (86). Contracts, web and server typechecks passed. Targeted oxfmt/oxlint and git diff --check passed. The worktree is clean, both branches are pushed, and PR-B's base is PR-A's branch feat/374-holistic-map.

No Mermaid subgraph/node-identity blocker occurred. Browser visual verification, before/after images, independent reviews, merge and deployment remain unperformed. The planner retains those delivery steps and must retarget this PR after A merges. No live userdata or dev server was used.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ No successful main baseline artifact is available yet. This run establishes the initial measurement.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	—	4.9 KiB	—	6.8 KiB	✅
Codex	Thread snapshot wire	—	3.8 KiB	—	4.9 KiB	✅
Codex	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Codex	Live turn WebSocket decoded	—	20.8 KiB	—	29.3 KiB	✅
Codex	Live turn messages	—	1	—	8	✅
Claude	Total thread wire	—	5.0 KiB	—	6.8 KiB	✅
Claude	Thread snapshot wire	—	3.8 KiB	—	4.9 KiB	✅
Claude	Live turn WebSocket wire	—	1.2 KiB	—	2.0 KiB	✅
Claude	Live turn WebSocket decoded	—	21.2 KiB	—	29.3 KiB	✅
Claude	Live turn messages	—	2	—	8	✅

Baseline: unavailable · PR result: 1150850 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 108.5 KiB
• Claude decoded thread snapshot: 108.8 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.