fix: isolate rein results and normalize manager startup failures
Some checks failed
ci / validate (push) Has been cancelled

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb
This commit is contained in:
tegwick 2026-09-06 01:13:23 +02:00
parent 73cee37ad8
commit 53f2abf7e0
8 changed files with 152 additions and 32 deletions

View file

@ -0,0 +1,51 @@
---
id: GLAS-WP-ADHOC-2026-09-06
type: workplan
title: "Repository review: session isolation and startup failure reporting"
domain: infotech
repo: glas-harness
status: finished
owner: codex
topic_slug: repository-review
created: "2026-09-06"
updated: "2026-09-06"
---
# Repository review
The working tree was clean at review start. GLAS-WP-0012 is the only unfinished
workplan. Its real-key proof still waits on owner activation and runtime
acceptance; the latest owner update is recorded there. These bounded local
fixes do not change profile readiness. No residuals from these fixes.
## Isolate reusable rein session results
```task
id: ADHOC-2026-09-06-T01
status: done
priority: medium
```
Both adapters stored the parsed CLI response on the adapter instance. When two
sessions interleaved, ending the first used the second session's outcome,
model and usage. Store the response in its session and read it from there.
The regression test reproduces the mixed outcome in both adapters before the
fix and validates distinct outcomes/model/usage afterwards.
## Normalize sandbox manager initialization failure
```task
id: ADHOC-2026-09-06-T02
status: done
priority: medium
```
Move default manager construction inside the sandbox-create error boundary.
Initialization failure now returns a failed GatewayResult with sandbox_create
stage and no sandbox id. Direct callers retain the error; Hub evidence omits
its raw contents. The regression test failed with an escaping exception before
the fix and passes afterwards.
Validation: full suite 104 passed; profile catalog validation passed with
existing readiness unchanged. Reviewed credential owner update and refreshed
the proposed policy reference in docs/anthropic-workload-key.md.

View file

@ -8,7 +8,7 @@ status: blocked
owner: codex
topic_slug: first-local-profile-production-proof
created: "2026-09-05"
updated: "2026-09-05"
updated: "2026-09-06"
state_hub_workstream_id: "170bf1ae-337f-5553-8d1e-03b07100e08f"
---
@ -223,3 +223,14 @@ policy/AppRole proposal and activation now live in SECRETS-WP-0009. Its
production exec refuses before OpenBao because durable access-engine decision
records and scoped service authority remain unavailable. T02 remains waiting
on that activation, pinned Claude startup and real provider/task acceptance.
## 2026-09-06 credential owner update
Reviewed secrets-engine message `3bd23bc9-e863-4f1f-8c76-415812ec0656`.
Owner reports the local authorization join implemented at `627810b`. Remaining
native activation depends on approval-engine serving the durable
ActionAuthorization claim endpoint and access-engine serving Check, followed
by configuration, per-lane approval and positive/negative verification.
State Hub decisions are not a substitute for the durable authorization object.
SECRETS-WP-0009-T03 and this plan's T02 remain waiting; runtime pinning and
combined real proof remain required. No readiness change or real-key read.