docs/tickets/#000012: §7 status refresh + file-rename + 2 AUTOCOUNT tags

§7 lead "In progress · Phase 1a landed 2026-05-08" was stale —
file header (current) says "Phase 1a (ForkScore) landed
2026-05-08; Phase 1b (consensus paper) landed 2026-05-10; Phase
1c (branch-set persistence) remains proposed-not-opened."
Refresh to match file header so the index claim and the body
section are saying the same thing.

§7 Phase 1a body referenced "tests/test_v8_fork_score.py — 25
cases" on two counts of drift:

1. **Filename stale**: file was renamed to
   `tests/test_substrate_fork_score.py` in `a4058a4` 2026-05-10
   under the v-prefix-retirement convention (substrate-paper
   version vs schema-version disambiguation). The original path
   no longer resolves.

2. **Count + scope conflated**: 25 cases at the time, but the
   surface has since split into two test files:
   - `tests/test_fork_score.py` (18 tests) pins the pure
     ScoredFork dataclass + scoring contract.
   - `tests/test_substrate_fork_score.py` (27 tests) pins the
     `arborist substrate score` CLI surface.

Refresh: name both files explicitly + AUTOCOUNT-tag each count
so future drift fires (#000044 discipline). Note the rename
provenance for future readers walking the design log.

Six in-progress tickets audited for §-status drift in today's
sweep wave:

  #000034  §7 lead       stale (now refreshed in 952abc5)
  #000035  §7 lead       clean
  #000036  §7 + closure  stale (refreshed in 952abc5)
  #000037  §20 + §17.1   stale (refreshed in 3b30126 + 952abc5)
  #000025  §11 lead      stale (refreshed in 3b30126)
  #000012  §7 lead       stale (THIS COMMIT)

5 of 6 had body-section drift. Pattern is consistent: file
header is the load-bearing surface fox updates; body sections
are point-in-time prose snapshots that freeze at landing time.
Sweep-on-amend is the right discipline; this commit closes the
last in-progress ticket §-status drift surface for today.

#000006 (rolling research log) and #000044 (closed today,
retroactive design log) excluded from sweep — different shapes.
Closed tickets prior to today excluded entirely per #000044 §5
discipline ("closed-ticket point-in-time snapshots stay
UNtagged / refreshing them changes archival meaning").

Verification:

  $ pytest tests/test_doc_counts.py
  3 passed in 2.48s

Tags by metric after this commit: 48 tests + 6 fixture-rows +
3 db-rows + 3 db-where = 60 active claims (was 58; +2 from this
commit's two new tests-metric tags on fork_score test files).
This commit is contained in:
russell@unturf.com 2026-05-10 18:50:11 -04:00
parent 952abc5085
commit 820409bf4f
No known key found for this signature in database

View file

@ -256,7 +256,8 @@ follow-up tickets that cite this one.
## 7. Status
**In progress · Phase 1a landed 2026-05-08.**
**In progress · Phase 1a + Phase 1b landed 2026-05-10; Phase 1c
remains proposed-not-opened.**
### Phase 1a — ForkScore (landed)
@ -282,10 +283,20 @@ function ahead of the consensus paper:
([0, SIGNAL_FLOOR)), REJECT (negative score OR hard-regression
flag OR `NEG_INF_REGRESSION` flag).
- Reference doc: `docs/v8-fork-score.md`.
- Tests: `tests/test_v8_fork_score.py` — 25 cases covering the
adapter, all verdict paths, hard-regression detection,
inf-bonus capping, neg-inf rejection, weight-set tuning,
breakdown completeness, CLI smoke. Full suite: 1186 passed.
- Tests: <!--AUTOCOUNT:tests:tests/test_fork_score.py-->18<!--/AUTOCOUNT-->
cases in `tests/test_fork_score.py` pin the pure ScoredFork
dataclass + scoring contract (SIGNAL_FLOOR=0.05,
HARD_REGRESSION_FLOOR=0.05, score = sum-of-breakdown closure,
NEG_INF_REGRESSION hard-reject). The CLI surface is covered
by <!--AUTOCOUNT:tests:tests/test_substrate_fork_score.py-->27<!--/AUTOCOUNT-->
additional cases in `tests/test_substrate_fork_score.py`
adapter tests + 4 in-process CLI tests via `build_parser()` +
1 real subprocess invocation catching entry-point / sys.argv
drift the in-process tests miss. Test file renamed from
`tests/test_v8_fork_score.py` in `a4058a4` 2026-05-10 per the
v-prefix-retirement convention (substrate-paper version vs
schema-version disambiguation). Suite at Phase 1a landing
(2026-05-08): 1186 passed; today: 2337 passed, 37 skipped.
### Phase 1b — Consensus paper (landed 2026-05-10)