[WIP] Plan TraceDecay V2 brain rewrite

[ScriptedAlchemy]

WIP: plan only

This PR contains only the total TraceDecay V2 redesign plan: one canonical master plan plus 27 linked subsystem/crate plans (28 files total). It deliberately contains no implementation.

Product direction

• Rebuild TraceDecay as one coherent cross-project, cross-repository, cross-worktree system: event stream, knowledge graph, retrieval, facts/memory, code/git/thread/agent/turn/task/timeline graphs, APIs, CLI/MCP, daemon, hooks, and UI.
• Build a native TraceDecay task graph/Kanban product by porting Hermes Kanban behavior and code where appropriate and improving it where TraceDecay's graph, scheduler, multi-agent, multi-model, and multi-repository requirements demand more. This is not a Hermes adapter; only executor/provider integrations are adapters.
• Replace the project-only dashboard with an All/Brain workspace, interactive graph and timeline explorers, task/plan views, reasoning/code/artifact lineage, and replay/debug playgrounds for retrieval, hooks, hints, redaction, curation, and scheduling.
• Make autonomous curation, memory/skill evolution, near-real-time model-assisted hints, nearby-agent awareness, conflict/duplicate-work prevention, retrieval IDs, supersession-aware search, precision evaluation, privacy/redaction, and public API/SDK contracts first-class.

Accepted-base reconciliation

• Rebased on master at 3567e31e (chore: release v0.0.48 (#418)).
• Incorporates merged PR fix(storage): add explicit split-store consolidation #425's canonical worktree/session identity and holder-identity changes.
• Records the accepted base's passing Linux/macOS/build/format/clippy checks and existing Windows shard failures instead of assuming green Windows behavior.
• Includes a required Hermes heritage ledger: pinned source/test/UI spans, license/provenance, direct-port vs behavioral-port vs redesign/drop decisions, destination owners, implementation PRs, and source-to-regression-test mapping.

Evidence and privacy

• Planning used TraceDecay's supported LCM, fact, code, git, analytics, diagnostic, and automation surfaces plus current open/merged PR evidence and targeted web/primary-source research.
• Private chronological exports remain outside Git under /fast/tracedecay-redesign-research (directory 0700, files 0600): 34,333 discovered role-user records and a 9,969-record best-effort human-authored subset through 2026-07-10T02:21:15.411Z.
• Retained sanitized content SHA-256: user a4d95d08a75cb04f130087a419fbc805cab6f5ee9a5e06da4e727908d3f7e366; human 35caa1af1095d4a50211e4e590639f493e95862854ff50edb646acd769f7bfea.
• No transcript/database fixture is committed or indexed by this PR.

Validation

• 28/28 intended plan files; no other changed paths.
• Internal relative links and heading anchors valid; Markdown fences balanced.
• Failure modes FM-001 through FM-103 are contiguous and unique.
• 680 public contract declarations checked with no incompatible duplicate definitions.
• Corpus ordering, identities, timestamps, retained-content hashes, and redacted-copy equality validated.
• Final direct plan scan and origin/master..HEAD history scan: zero gitleaks findings.

Draft/WIP remains intentional until the plan is reviewed as a single flowing architecture.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8596cf3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ScriptedAlchemy]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 986f25cca6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Schedule the catalog before generated-metadata consumers

When the Phase 3 ladder is followed literally, this schedules PR 22F–22H before PR 22A even though the 22F–22H checklist requires plan 08's generated SurfaceKind everywhere. PR 22A is the step that creates the generated capability/tool catalog and its surface/availability artifacts, so the accounting/adoption work either blocks or has to invent duplicate local surface metadata; move 22A ahead of the first generated-catalog consumer or split the dependent 22H work after it.

Useful? React with 👍 / 👎.