docs(STATE-WP-0079): archive suggestion-backlog history, record E1 status
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Slice E1 was already half-retired: mutations 410 since CUST-WP-0061-T06,
reads held open only to keep the history reachable. That history is now
archived fleet-side, so the reads can go.

Records a dependency the inventory's 17-item count misses: the suggestions
dashboard page is live and referenced from index.md and wsjf-triage.md, so
E1's removal must sequence with the UI slices A4/B5 rather than ahead of them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-20 07:42:00 +02:00
parent ecc10b1f9f
commit 98af485cd5
2 changed files with 32 additions and 4 deletions

View file

@ -178,9 +178,19 @@ repo, since State Hub is being archived and the record must outlive it.
(`GET /workstreams/`, `GET /workstreams/{id}`,
`GET /workstreams/{id}/dependencies/`, `GET /tasks/?workstream_id`) clear as
their quiet counters run; earliest is 18 more silent days. Re-capture before
deciding — the ladder evaluates at review time. Then the remaining `retire`
inventory items outside E2: `suggestion-backlog` (E1, 17) and `dashboard-meta`
(E3, 1); `legacy-meter` itself (E4, 9) retires last, being the instrument.
deciding — the ladder evaluates at review time. **Slice E1 part-executed (2026-08-20):** `suggestion-backlog` history archived
to `the-custodian/docs/archived-suggestion-backlog.md` — 10 suggestions, 10
notes, 5 bumps, all `declined` in the 2026-07-21 intake migration, none
promoted. Mutations already 410 since `CUST-WP-0061-T06`; reads were open only
to keep that history reachable, which the archive now replaces.
E1's remaining removal (8 read routes, 6 MCP tools, 3 tables) is **coupled to
the dashboard** — `dashboard/src/suggestions.md` is live and referenced from
`index.md` and `wsjf-triage.md`. The inventory's 17-item count does not show
this. Sequence with the UI slices A4/B5, not ahead of them.
Then `dashboard-meta` (E3, 1); `legacy-meter` itself (E4, 9) retires last,
being the instrument.
## Stabilization window and archive prep