feat: finish register receiving and authority routing
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
parent
6d134425df
commit
d103955217
28 changed files with 970 additions and 48 deletions
|
|
@ -35,8 +35,18 @@ confirmed live hub-first workplans in this snapshot.
|
|||
|
||||
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. Repairing the seven live bindings is
|
||||
the remaining prerequisite for T07.
|
||||
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
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue