Measured wall times: gate 14.0s, boot smoke 20.4s (-6.3s), changed-only
pnpm test 17.5s; quarantine ledger 0. Shard-timing snapshot rebuilt
from today's CI shard artifacts (run 31929730933) plus a locally
measured full dashboard suite so dashboard lane weighting keeps its
per-file data. The trim shows: the former top-6 core PG offenders are
gone from the slowest-20 (sqlite-migrator 2m29s serial -> 20.4s;
SettingsModal.general off the table entirely). Caveat: the dashboard
rows come from the pre-trim analysis measurement, so entries like
SettingsModal.scheduling-merge (30.2s, now ~13s) are pessimistic until
the next dashboard re-measure.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
## 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.
Refresh the weekly test velocity baseline after the pnpm test lane recovered.
- Update the latest baseline with green gate, boot smoke, and pnpm test timings.
- Drop stale timing rows for removed or split test files.
- Append the new weekly history entry with current slowest-file data.
Files changed:
docs/test-velocity-baseline.md | 48 +++++++---------
scripts/test-timings.json | 14 +----
scripts/test-velocity-history.json | 112 +++++++++++++++++++++++++++++++++++++
3 files changed, 133 insertions(+), 41 deletions(-)
Fusion-Task-Id: FN-7092
Fusion-Task-Lineage: 0b2cfa7a-953b-4cf8-ac4b-c81a0580a4e0
Co-authored-by: Fusion (runfusion.ai) <noreply@runfusion.ai>
Refresh the weekly test velocity baseline with current timing evidence.
- Update the rendered baseline report with the latest capture timestamps and velocity deltas.
- Replace stale slowest-file timing rows with the refreshed snapshot entries.
- Append the latest velocity history sample used by the weekly report.
Files changed:
docs/test-velocity-baseline.md | 61 +-
scripts/test-timings.json | 1772 +++++++++++++++++++++++++++++-------
scripts/test-velocity-history.json | 112 +++
3 files changed, 1580 insertions(+), 365 deletions(-)
Fusion-Task-Id: FN-6968
Fusion-Task-Lineage: 940f3581-3650-4feb-8730-d6dbb760e30c
Clean up stale test timing metadata after the cwd fallback test removal.
- remove the obsolete timing entry for cwd-integration-fallback-removed.test.ts
- keep scripts/test-timings.json aligned with the current reliability-interactions test set
Files changed:
scripts/test-timings.json | 1 -
1 file changed, 1 deletion(-)
Fusion-Task-Id: FN-5969
Fusion-Task-Lineage: 8e8541a6-6198-4472-a40a-1161cc8443bd
