Close live inventory migration and prepare workplan identity repair
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 10:17:42 +02:00
parent da42f764c0
commit 3dc005df1c
5 changed files with 157 additions and 4 deletions

View file

@ -67,3 +67,28 @@ no generated repository changes were observed. This confirms a latency issue,
but does not establish that timeout tuning alone is sufficient. State Hub sync
remains pending. A focused State Hub endpoint/query latency investigation is
needed before another full consistency run. No registrar authority was changed.
## Operational migration and precise sync blocker
RPF-WP-0028 is now finished: durable directory and versioned capture hook
installed on railiance01; actcore-worker rolled out; definition synchronized
and read back from the API. All 51 restored entries survive in the 86-entry
union. The worker mount is read-only, and missing input is rejected before
subprocess invocation. No prune was executed. See the dedicated JSON receipt.
Platform code `da42f76`; activity-core integration `4083f31`.
The current State Hub AGENTS.md documents `rmgr sync --path . --push` for fast
projection sync, reserving fix-consistency for deep audits. That command
assigned missing identifiers and pushed `05f315b`, verified primary/railiance01
and the exact Forge commit, then returned a refusal in 5.8 seconds. The blocker
is six duplicated identities shared by the archived May apps-pg plan and the
August Core Hub onboarding plan, both RPF-WP-0021. No projection mutations were
performed. RPF-WP-0031 tracks the exact repair proposal and the required exception
to this repository's managed-UUID editing prohibition. This supersedes the
previous undifferentiated "sync latency" blocker; deep audit latency is separate.
Read-only State Hub source inspection also found eager relationship loading
on RepositorySlug, ManagedRepo, Workplan and Task. Avoiding unrelated relationship
loads is a candidate optimization for the snapshot/identity endpoints, not a
measured root-cause finding. No State Hub service code or deployment was changed.