docs: reconcile installed runtime and offline rehearsal evidence
Some checks failed
Governed runtime contract / contract (push) Failing after 12s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
tegwick 2026-10-19 11:28:42 +02:00
parent 0b7a9cfdc8
commit eca0a5891c
2 changed files with 38 additions and 2 deletions

View file

@ -133,3 +133,16 @@ retains a legacy set of local task executors for unattended repository work.
- Production claim loop: `docs/ops-run-claim-loop.md`
- Deployment: `deploy/README.md`
- Completed work records: `workplans/`
## Owner runtime reuse update — 2026-10-19
The repository includes the credential-free `owner_rehearsal.rehearse` API and
owner renewal support tracked in HARNESS-WP-0008. Reuse these existing paths for
installation verification and bounded attempts; do not introduce a parallel
launcher. Custodian's October 17 native-runtime-install-r3 execution receipt
proves installed artifact `f59959b6…` passes offline rein/Glas/Claude startup,
unchanged full digest and process cleanup. Revision 2's earlier failed rehearsal
is preserved. This has zero model calls and no credential/configuration reads.
Remaining spend-memo lifecycle, owner renewal/pin updates, fresh native approvals
and bounded successful model/tool acceptance remain in HARNESS-WP-0008-T07.
Actual Custodian interactive isolation remains a separate consumer obligation.

View file

@ -9,7 +9,7 @@ owner: claude-code
topic_slug: rein-aharness
priority: high
created: "2026-10-13"
updated: "2026-10-17"
updated: "2026-10-19"
related:
- REINAH-WP-0003
state_hub_workstream_id: "187c2599-84a6-5764-a14f-7e9121975bf2"
@ -263,7 +263,7 @@ lives outside this repo. If accepted, hand it off as a residual intake.
id: HARNESS-WP-0008-T07
status: wait
needs_human: true
blocking_reason: "Owner: accept spend memo infd-20261014-b01, then attended install, rehearsal, renew and approvals on railiance01"
blocking_reason: "Owner: finish spend memo lifecycle, renew and update Secrets Engine pins, then fresh native approvals and bounded model/tool proof; f599 installation and offline rehearsal verified 2026-10-17"
priority: high
state_hub_task_id: "80318842-ccaa-5484-a54a-3d9981eaec8b"
```
@ -363,3 +363,26 @@ owner artifact installation/rehearsal, renewal and Secrets Engine file-pin
updates, required native approvals and bounded real-model/tool proof. Actual
interactive assignment migration and external tool-path denial remain Custodian
acceptance obligations; no profile readiness or supervision authority changed.
### Installed artifact and offline rehearsal reconciled — 2026-10-19
The older candidate/install/rehearsal instructions above are historical. The
Custodian retained exact execution receipts under
`docs/changes/netkingdom-target-2026-10-17/native-runtime-install-r2/execution-receipt.json`
and `native-runtime-install-r3/execution-receipt.json` in its repository.
Revision 2 installed complete artifact
`f59959b605a51abd2901becde14e7abd852c2bd3f848004b51d250d1cb81af6d`
on Railiance and verified its digest; the rehearsal failed and remains recorded.
Revision 3 reused that installed artifact without installation calls. Its status
is `installed_runtime_offline_rehearsal_verified`: rein, Glas and Claude
launchers all exit zero, the post-rehearsal full digest matches, durable receipt
precedes cleanup, and no live or waitable descendants remain.
Do not rebuild an older candidate, reinstall f599 or repeat the completed
offline rehearsal to satisfy those old instructions. This evidence has zero
model calls and no credential/owner-configuration reads; it establishes neither
current native credentials nor spend authority. T07 remains wait for the spend
memo lifecycle, owner renewal/Secrets Engine pin updates, fresh required native
approvals and one bounded real-model/tool acceptance. Actual interactive
assignment migration remains CUST-WP-0073's separate acceptance requirement.
Canonical HARNESS task identity and all existing Hub UUIDs remain unchanged.