## Six phantom paths in the shard-timing snapshot
```
AssertionError: timing snapshot references missing test files:
packages/core/src/__tests__/dependency-blocked-todo-report.test.ts
packages/core/src/__tests__/workflow-parity.test.ts
packages/engine/src/__tests__/dependency-blocked-todo-reporter.test.ts
packages/engine/src/__tests__/reliability-interactions/meta-archive-guard-composition.test.ts
packages/engine/src/__tests__/reliability-interactions/meta-chain-auto-close.test.ts
packages/engine/src/__tests__/self-healing-meta-archive-guards.test.ts
```
The guard's own note says why this matters past the red assertion:
*"stale or phantom-path entries silently degrade CI shard balancing and
can hide merge-gate regressions."*
**The balancing cost is not academic.**
`self-healing-meta-archive-guards` carried **20700 ms**. A shard has
been budgeting 20.7 seconds for a file that cannot run, plus five more.
## Deleted, not moved — checked one at a time
A moved test should be **repointed** to keep its measurement; only a
deleted one should be dropped. So I resolved each rather than assuming:
| file | deleted by |
| --- | --- |
| `dependency-blocked-todo-report` / `-reporter` | `710d56b2db` — U4
trim, the feature deletion |
| `workflow-parity` | `4158cf1ab7` — Phase A workflow-owned lifecycle |
| `meta-archive-guard-composition`, `meta-chain-auto-close`,
`self-healing-meta-archive-guards` | `0e3d2a2265` — meta-task
auto-archive/auto-close deletion |
All six died with their features. None has a surviving equivalent
anywhere in `packages/`.
## Pruned, not regenerated
Regenerating means a full measured suite run and rewrites all 2499
entries — burying six deletions inside a wholesale diff nobody can
review. `capturedAt` is **6.8 days old against a 30-day budget**, so the
snapshot is otherwise current and the other **2493 measurements are
untouched**.
The diff is exactly six deleted lines, `capturedAt` unchanged.
## Revert proof
Pruning a list is worthless if the assertion cannot fail afterwards, so
I re-introduced a phantom entry:
```
with a fake path → ℹ pass 11 ℹ fail 1 (references missing test files)
removed → ℹ pass 12 ℹ fail 0
```
## Third of the red suites, and still not a sweep
Mechanical, like `verify-fast` (#3038). Unlike
`workflow-reliability-release-check`, whose acceptance map cites 13 test
files with **8 missing** and **2 of 5 rows carrying zero surviving
evidence** — that one needs its owner, and a repoint would launder the
gap (diagnosed on #3036).
Same failure phrasing, opposite safety. That is why these are going one
at a time.
## Verification (measured)
- this suite — **12 passed / 0 failed** (was 1 failed)
- snapshot integrity — 2493 files retained, `capturedAt` unchanged, no
reformatting
No changeset: CI tooling data.
49fb39e644