docs: clear phantom-doc refs in TICKETS.md + CLAUDE.md (bb6a89c cleanup propagation)

fox's commit `bb6a89c` (2026-05-09, "30% reduction") deleted
seven docs but the indexes weren't updated to remove the dangling
references. End-of-session sweep caught + cleared:

== Phantom refs in TICKETS.md "Distinction from other docs" ==

5 dangling references to deleted docs:

  - concept-relations-design.md  → deleted in bb6a89c
  - mesh-deploy.md               → deleted in bb6a89c
  - self-reference-design.md     → deleted in bb6a89c
  - verifier-semantic-gap-design.md → deleted in bb6a89c
  - qa-modes-bench-2026-04-30.md → deleted in bb6a89c

Replaced with the high-value arch docs fox's bb6a89c commit
message explicitly named as kept:

  - seven-point-program.md (north-star directive)
  - cti-architecture.md (kept)
  - mesh.md (mesh-deploy removed; mesh.md kept)
  - benchmarks.md (operational; kept per commit message)
  - bench-maxing.md (operational; kept)
  - qa-modes-bench.md (rolling addenda — distinct from the
    dated -2026-04-30 file that was deleted)
  - soft-hash-channel-analysis.md (#000018 closure)
  - soft-hash-channel-t3-bound.md (#000036 derivation)
  - tool-action-dag-design.md (already present; kept)

== Phantom refs in CLAUDE.md `## Docs index` ==

5 dangling references (one of them duplicated — fox typo'd
self-reference-design.md on two consecutive lines with the
same description):

  - mesh-deploy.md
  - qa-modes-bench-2026-04-30.md
  - bench-emergent-design.md
  - verifier-semantic-gap-design.md
  - self-reference-design.md (duplicate entry)

Replaced with current arch docs:

  - mesh.md (mesh wire + group-key)
  - soft-hash-channel-analysis.md + soft-hash-channel-t3-bound.md
  - calculator-test-patterns.md (#000044 sister discipline)
  - spec-methodology.md (#000019)
  - v7w-frontier-catalog.md (#000013)
  - v8-fork-score.md (#000012)
  - pi-star-composition.md (#000015)

== Inline ref in CLAUDE.md §"Retrieval pipeline" ==

L328 cited `docs/concept-relations-design.md` for the
1.6%-storage-tax rationale. Doc deleted; rationale now lives
inline in `arborist/concepts/extract.py` + the data is
self-describing. Updated the prose to note the deletion +
where the design now lives.

== Why this matters ==

A phantom doc reference is the doc-index equivalent of a stale
phase descriptor — it sends future readers to a file that
doesn't exist. Same root cause as today's §-status drift
(in-progress prose freezing while load-bearing surface updates).
The bb6a89c commit was thorough about deletion but didn't
sweep the indexes; this commit closes that loop.

Hygiene: doc-only commit, no schema, no tests touched. Full
suite 2347 passed + 37 skipped earlier; 60 active AUTOCOUNT
claims still clean (3 passed in 2.80s).

CLAUDE.md

@@ -324,8 +324,10 @@ enough; revert at your peril. Order:
    Intel-titled docs drop from AMD queries; reverse holds. Backed
    by the per-shard `concept_relations` SQLite table (corpus-derived,
    not hand-curated). 1.6% storage tax measured at backfill on 6 GB
-   wiki — kept flat, no further compaction. See
-   `docs/concept-relations-design.md` for the storage choice rationale.
+   wiki — kept flat, no further compaction. (Storage choice rationale
+   lived in `docs/concept-relations-design.md` prior to its deletion
+   in `bb6a89c` — the design is now documented inline in
+   `arborist/concepts/extract.py` + the data is self-describing.)
 6. **Stem-aware token matching** — possessive / plural collapse
    (`superman's → supermans → superman`).
 7. **Per-source context cap** — `max_context_chars / top_k`. Prevents
@@ -450,19 +452,27 @@ North-star:
 Architecture / ongoing work:
 
 - `docs/cti-architecture.md` — CTI Clause Tree Intelligence.
-- `docs/mesh.md`, `docs/mesh-deploy.md` — mesh wire + deploy.
+- `docs/mesh.md` — mesh wire format + group-key state machine.
 - `docs/benchmarks.md` — orientation: harnesses, fixtures,
   signal floor, make targets, bench-row schema, addenda index.
   Read first when running a bench.
 - `docs/qa-modes-bench.md` — bench journal (rolling addenda).
   Headlines + cross-references to per-ticket bench data.
-- `docs/qa-modes-bench-2026-04-30.md` — JSON-mode hardening journey
-  (prior bench reference).
 - `docs/bench-maxing.md` — bench discipline (5pp signal floor etc).
-- `docs/bench-emergent-design.md` — random-word stress-test design.
-- `docs/verifier-semantic-gap-design.md` — soft-signal NLI proposal.
-- `docs/self-reference-design.md`,
-  `docs/self-reference-design.md` — recursive distillation.
+- `docs/soft-hash-channel-analysis.md` — #000018 closure; analysis
+  of soft-hash covert channel risks under M0/M1/M2 threat models.
+- `docs/soft-hash-channel-t3-bound.md` — #000036 closed-form
+  per-window budget bound; pairs with t3_bound_calculator.
+- `docs/calculator-test-patterns.md` — sister discipline for
+  testing calculator-style code (12 patterns; see #000044 for
+  numeric drift discipline).
+- `docs/spec-methodology.md` — #000019 specification methodology
+  for π* canonical projections.
+- `docs/v7w-frontier-catalog.md` — #000013 v7-W spatial-temporal
+  frontier catalog (4 ε-frontiers).
+- `docs/v8-fork-score.md` — #000012 ForkScore Phase 1a reference.
+- `docs/pi-star-composition.md` — π* cross-domain composition
+  reference (#000015 deliverable).
 
 Tickets: `docs/TICKETS.md` is the authoritative index with `Next
 ID`. Closed tickets stay in place as the design log. New tickets

docs/TICKETS.md

@@ -37,16 +37,27 @@ go/no-go, or scoped enhancements queued for future implementation.
 that are NOT tickets — they describe state of the world rather than
 proposing change. Examples that stay un-numbered:
 
-- `cti-architecture.md` (architecture reference)
-- `mesh.md`, `mesh-deploy.md` (architecture + ops reference)
-- `qa-modes-bench-2026-04-30.md` (point-in-time bench journal)
-- `verifier-semantic-gap-design.md`,
-  `self-reference-design.md` (older design docs that
-  pre-date the ticket convention; leave as-is unless retroactively
-  promoting one to a ticket adds value)
-- `concept-relations-design.md` (architecture reference for the
-  per-shard `concept_relations` synonym/rivalry layer + the 1.6%
-  storage-tax rationale; landed 2026-05-01)
+- `seven-point-program.md` (north-star architectural directive
+  distilled 2026-05-01; every new ticket / feature / prompt edit
+  walks past this; bench harness reports per-mode directive
+  coverage)
+- `cti-architecture.md` (architecture reference for the Clause
+  Tree Intelligence claim-lattice-pointer mode)
+- `mesh.md` (mesh wire format + group-key state machine)
+- `benchmarks.md` (bench harness orientation — fixtures, signal
+  floor, make targets, bench-row schema, addenda index; read
+  first when running a bench)
+- `bench-maxing.md` (bench discipline — 5pp signal floor, n=3
+  default, avoid negation in prompts, honest verdicts over
+  optimistic ones)
+- `qa-modes-bench.md` (rolling bench-journal addenda with
+  cross-references to per-ticket bench data)
+- `soft-hash-channel-analysis.md` (analysis doc closing #000018
+  open questions §9.1 / §9.2 / §9.3; companion to
+  `soft-hash-channel-t3-bound.md`)
+- `soft-hash-channel-t3-bound.md` (#000036 formal derivation of
+  the per-window covert-channel budget; companion to the analysis
+  doc, both feed the t3_bound_calculator)
 - `tool-action-dag-design.md` (research path for an action-
   provenance layer downstream of `final_label`. Captured pre-ticket
   per the 2026-05-07 arborist-vs-donto comparison; promotes to a