Commit graph

2 commits

Author SHA1 Message Date
codex
b5205d66b9 docs(recovery): drop agent-harness by owner decision
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 1s
Superseded by glas-harness and the rein concept, so there is nothing to
restore. Not onboarded to central; its cache-only record is left to disappear
when the cache database is discarded, rather than preserved as a hub-only
record with no backing file.

Successors verified present and classified on central before dropping.
Ten records remain outstanding.

Refs CUST-WP-0067-T05

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-25 13:51:05 +02:00
codex
7f19ad465b feat(workplan): close CUST-WP-0067 T04 and T05, open T09
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
rmgr repo-onboard is the missing managed_repos write path. 33 of 44 cache-only
repositories onboarded to central (78 -> 111); the other 11 carry written
dispositions rather than guessed classifications.

T04 uncovered why onboarding only worked from a workstation: the hub resolved
its classification allowed-values file from hardcoded developer checkouts, so
every classification write 500'd in the container. T09 delivers that file.

The local cache database must not be discarded yet — 11 records live only there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-24 23:35:58 +02:00