6.2 KiB
Factory runtime and legacy identity continuation
The worker's missing sandbox-to-source join is implemented and locally proved. It captures a bounded Git bundle through sand-boxer's owner execution after rein cleanup, then imports the exact commit only after successful sandbox teardown and baseline, lease, ancestry, path-grant and object-bound checks. The real local bwrap/Glas/worker exercise passed; a lost terminal-close response replayed without rerunning the task. Queue and authoring were fixtures. No paid model request, factory delivery attempt or live G1/G2 acceptance is claimed.
Native profile USD and turn limits now reach Claude CLI controls with version preflight and strict terminal cost/token/turn accounting. Invalid, missing or exhausted accounting refuses success. This removes the configured route's empty usage accounting; unconfigured legacy paths retain their existing behavior. It does not yet establish the proposed EUR 5/run, EUR 25/day, EUR 150 total factory envelope. Durable reservations, unknown-outcome recovery, conservative currency treatment and actual provider enforcement semantics remain required.
Validation: rein-aharness 290 tests, Glas 133 tests; worker release-contract gate 51 checks and recovery gate 13 checks pass. The contract/recovery checks overlap the main suite and are not additional delivery attempts. Matching Glas and sand-boxer revisions are pinned in rein's runtime lock. The protected runtime must be rebuilt/installed and admitted for the actual factory identity and host. Runtime evidence.
The user-authorized low-cost side quest used gpt-5.6-luna for the historical-ID audit. Root review tightened the allowlist, retained global collision detection for canonical task IDs, replaced nonportable tests, and verified the production projection merge. Repo Manager now accepts the exact historical suffix IDs and 38 parent-local task aliases. All 54 affected historical task UUIDs, parent bindings and statuses survived the production merge exercise against a current read-only Hub snapshot. Repo Manager's suite passed 169 tests. Identity evidence.
Only three missing qualified ad-hoc UUID fields were restored with Repo Manager; all three matched the UUID already held by the Hub. Existing IDs/UUIDs were not replaced. The machine canon and Repo Manager registry now agree on grandfather compatibility. Unknown aliases or missing local historical UUIDs still refuse. Binding restoration.
Efficiency gained and remaining work
The artifact change prevents successful sandbox work from being discarded and removes the need for manual commit recovery. Existing repository transactions, metrics, grants and close replay are reused. Native control/accounting provides a concrete input for the remaining spend admission. Historical compatibility removes the ordinary synchronization identity refusal without a renumbering campaign. No delivery-time or cost saving is claimed yet: the factory attempt ledger is empty and its fourteen-day measurement period has not begun.
HFACT-WP-0001 remains the governing plan; reuse-surface remains the first internal capability, Railiance Fabric the later placement capability, and vergabe-teilnahme the primary customer service/UI repository. Continue:
- HFACT T01: durable daily/total spend reservation, unknown-outcome recovery, provider semantics and final operating-owner acceptance of the concrete G0 packet.
- HFACT T03/T04: deployed PDP replay adoption, client-side/audit custody, approval/native credential delivery, exact factory identity and Railiance placement.
- HFACT T05: install the matching protected runtime, then real model G1 and natural Railiance claim/heartbeat/import/metrics/close G2 with recovery negatives.
- HFACT T06–T08: deliver the typed reuse-surface refusal, consume it from vergabe-teilnahme, verify authorized release/recovery and measure fourteen days.
RMGR-WP-0014 closes bounded identifier compatibility. CUST-IN-0017 remains open for duplicate/retired/orphan history and CUST/THE instruction-generation policy; HFACT T02 retains incomplete task-field projection and request-sensitive idempotency keys. Ordinary synchronization does not authorize historical row retirement. Exact push/projection receipts and the final session progress record supply completion evidence for this continuation.
Final synchronization return
All five changed repositories obtained applied receipts from primary/railiance01 for their exact pushed commits. Custodian ordinary synchronization now succeeds: 77 workplans reconciled, with no workplan retirement and no task creation or cancellation. The previous identifier refusal is resolved. The separate deep consistency audit still reports 13 historical findings under CUST-IN-0017; this is not a claim that broader history or prefix-policy reconciliation is finished.
The four owner/project task files were compared with the Hub after projection: 20 tasks checked, six repaired through supported task PATCH calls. The current fields match source; the systemic projection defect remains HFACT T02. Commits, primary receipts and progress IDs.
Live Custodian readback verified all 54 historical task bindings. Source-field parity was checked for 452 bound task blocks; 114 records required field repair after ordinary projection. Another 28 unbound source blocks remain recorded with CUST-IN-0017. This shows why HFACT T02's projection-completeness fix still matters: correcting current cache contents is not a durable fix to the projection code.
The broad reconciliation exposed an existing archived CUST-WP-0054 conflict: T09/T10 source fences say wait, have legacy UUIDs missing from the current Hub, and their current derived rows were already cancelled. Those two rows were restored to their pre-sync cancel state; no new historical work is authorized. CUST-IN-0017 now explicitly records the source/identity conflict and the need to prevent future ordinary projection from reopening it. The remaining 54 audited compatibility bindings stayed unchanged. This is a preserved historical exception, not permission to rewrite archival source or replace its UUIDs.