docs: give retirement tasks distinct sections

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a06d83-1cbc-71f2-b0dc-e0f48cedae43
This commit is contained in:
tegwick 2026-09-04 21:42:31 +02:00
parent f7eb5bfd1f
commit 94e31e3d92

View file

@ -91,7 +91,7 @@ Per `SCOPE.md`, this workplan **decides and inventories; it does not implement**
Every implementation task it identifies is routed to the owning repository by
identifier.
## Tasks
## Correct the generation-2 record
```task
id: SHR-WP-0002-T01
@ -108,6 +108,8 @@ The `0/0` rollback deployment is the designed end state.
**Completed 2026-09-04.** `DECISIONS.md` records the correction and its evidence,
so the project's own record shows that the first reading was wrong and why.
## Inventory generation-2 dispositions
```task
id: SHR-WP-0002-T02
status: todo
@ -129,6 +131,8 @@ workplan), or **dropped** (and by whose decision).
The expected output is uncomfortable and worth having: a list of things the
estate intended to have, does not have, and has not decided to do without.
## Relocate the generation-3 runtime
```task
id: SHR-WP-0002-T03
status: done
@ -190,6 +194,8 @@ were scaled to zero after stabilization, and the sequence and disposition are
recorded in `DECISIONS.md`. `CORE-WP-0010` remains historical context, not the
vehicle that ultimately resolved this task.
## Reconcile repository scope against reality
```task
id: SHR-WP-0002-T04
status: todo
@ -207,6 +213,8 @@ Produce a table of every participating repository's stated position versus
observed reality, and route each correction to its owner. Do **not** edit their
files from here — the project's authority is the ledger, not the prose.
## Sweep downstream lanes
```task
id: SHR-WP-0002-T05
status: progress
@ -234,6 +242,8 @@ runner lanes, but closure is incomplete. In particular,
`inter-hub-bootstrap-ssh` remains an active high-risk catalog lane and needs an
owner decision rather than silent deletion.
## Add a generation-transition gate
```task
id: SHR-WP-0002-T06
status: todo
@ -252,6 +262,8 @@ consumers are reconciled, its downstream lanes are swept, and its successor is
deployed somewhere that will still exist. Take it through the project's normal
decision route rather than adding it unilaterally.
## Retire CoulombCore registry dependencies
```task
id: SHR-WP-0002-T07
status: progress