tegwick
d103955217
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
2.5 KiB
| id | type | workplan_task | created | source |
|---|---|---|---|---|
| RMGR-EVIDENCE-0005-ORPHANS-20260821 | evidence | RMGR-WP-0005-T09 | 2026-08-21 | local State Hub at http://127.0.0.1:8000 |
Local-cache orphan disposition rebaseline
The 2026-08-17 baseline of 28 workplans without backing_filename is stale.
On 2026-08-21 the local State Hub returned 224 unbound rows:
| Status | Count | Disposition class |
|---|---|---|
active |
1 | live, broken link |
blocked |
1 | live, broken link |
proposed |
3 | live, broken link |
ready |
2 | live, broken link |
finished |
201 | closed provenance |
archived |
16 | closed provenance |
Every one of the seven live rows has a matching repository file. There are no confirmed live hub-first workplans in this snapshot.
| Hub slug | Repository file |
|---|---|
nk-wp-0027 |
net-kingdom/workplans/NK-WP-0027-reef-placement-reconciliation.md |
state-wp-0081 |
state-hub/workplans/STATE-WP-0081-cluster-self-sufficiency-and-registrar.md |
railiance-wp-0022 |
railiance-platform/workplans/RAILIANCE-WP-0022-agent-high-risk-boundary-coverage.md |
railiance-wp-0023 |
railiance-platform/workplans/RAILIANCE-WP-0023-hub-core-candidate-credential-lanes.md |
rail-en-wp-0001 |
railiance-enablement/workplans/RAIL-EN-WP-0001-private-by-default-templates.md |
rail-ho-wp-0010 |
railiance-infra/workplans/RAIL-HO-WP-0010-new-reef-ports-need-a-grant.md |
ops-wp-0003 |
ops-hub/workplans/OPS-WP-0003-extension-contract-alignment.md |
The 217 closed rows remain cheap historical provenance. They need not be reconstructed as files, but the cache-rebuild procedure must export or retain them before replacing the local database.
Repair result
All seven bindings were submitted together to the preferred
PUT /workplans/index/bindings route and the hub acknowledged
{"updated":7,"received":7}. A fresh query now finds exactly 217 unbound rows:
201 finished, 16 archived, and zero live. No repository file or
lifecycle status was changed. The broad fix-consistency --all path was not
used for the repair because it aborts while refreshing the brief for stale
registered path /home/worsch/inter-hub; the targeted binding route avoided
coupling this data repair to that unrelated registry defect.
Reproduction
The counts came from GET /workplans/, selecting rows whose
backing_filename is null and grouping by status. Repository UUIDs were joined
to GET /repos/; canonical ids and exact titles were then searched in each
reported checkout. This evidence records no secret or credential value.