coulomb/the-custodian
4
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

feat(workplan): record the RAILIANCE-WP orphan debt as CUST-WP-0068-T09
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Migrating active workplans off the retired family prefix left 26 hub rows with
no backing file. Accepted deliberately: the alternative was one repository
carrying two prefixes indefinitely.

Blocked on ADR-012 decision 7's per-repository reset — C-07 is not fixable and
hand-deleting hub rows is the direct central edit ADR-010 decision 6 forbids.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
codex 2026-08-25 23:00:47 +02:00
parent 46c5d1682e
commit 6629212985
1 changed files with 35 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

35
workplans/CUST-WP-0068-cache-only-work-record-recovery.md
View file

@ -298,6 +298,41 @@ verified only by the person who caused the damage.
By status the remainder is overwhelmingly closed history — 96 `finished`, 10
`archived` — with only 2 `active`, 2 `blocked` and 1 `proposed` still live.
## Clear the orphaned RAILIANCE-WP rows
```task
id: CUST-WP-0068-T09
status: wait
priority: medium
```
Migrating the active workplans off the retired `RAILIANCE-WP` prefix
(2026-08-25, owner decision) changed their canonical identifiers, so the records
registered under the old ones no longer have a backing file. **26 orphaned rows
remain on central**, mostly `finished` and `archived`.
This debt was accepted deliberately rather than discovered: the alternative was
leaving one repository carrying two prefixes indefinitely, which is more
confusing than a visible, bounded set of stale rows.
C-07 detects them and is explicitly `fixable=False`, and there is no sanctioned
delete path — reaching past the tooling to remove hub rows by hand is the direct
central edit `ADR-010` decision 6 forbids. The correct instrument is `ADR-012`
decision 7's per-repository reset from the forge, which rebuilds
`railiance-platform` and `railiance-apps` from what Forgejo holds and drops
whatever no longer derives.
Status is `wait`, not `todo`: this is blocked on that reset existing, and doing
it any other way would violate the ADR accepted the same day.
Note the prefix collision this resolved was worse than a naming inconsistency.
Three repositories used one number space for unrelated work — `RAILIANCE-WP-0012`
was an openbao extraction, a cnpg backup, and a deploy-verify simultaneously —
and `railiance-platform` carried two files both numbered `0016`.
Acceptance: no `railiance-wp-*` record remains on central; the 26 are gone
through re-derivation rather than deletion.
## Converge and retire the cache database
```task