[ScriptedAlchemy]

Why

The owner is redesigning TraceDecay's code index and graph storage and asked to clean up prior design work that is no longer relevant. This first unit removes only passages that are already stale against the code shipping today. It does not implement or describe the redesign.

What changed

• Removed the retired dense-retrieval plan and retargeted every plan reference to it.
• Removed stale storage claims: the Grafeo version pin, vector ownership, the no-production graph-at-rest status, superseded Bytes gates, the Plan 39 published pin, vector task, and reclaim prescription, the Plan 40 revision-7 status and compatibility staging, and the Plan 38 branch-DB mechanism.
• Replaced the storage plan's forward-migration and two-release importer prescription with the current reset rule.

Scope

Covers only the "Safe to remove now" entries and the "STALE NOW" storage rows. Keeps everything marked removable when the redesign lands and every KEEP row, including SQLite sessions and durable memory.

Tradeoffs

The generated structure snapshot is pinned to revision 0b04bce, so regenerating it after these removals is byte-identical. It still records the retired plan at that revision. I did not hand-edit it.

Blast Radius

Documentation only. No runtime behavior, store shape, or build input changes.

Verification

• Regenerated mockups/ui-concept-v2/app/src/structure/snapshot.json with its generator and compared it: IDENTICAL.
• Link check over every changed document: all local links resolve. One pre-existing broken anchor in Plan 15 (00-plan-set-index.md#rejected-approaches) is unchanged by this work.
• git grep for Plan 31, 31-native-fastembed, and Plans 25/31: no matches outside the pinned snapshot.
• git diff --check: clean.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 81e9db4

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