fix: validate sandbox readiness before rein handoff
Some checks failed
ci / validate (push) Has been cancelled
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:
parent
31dd5aaca8
commit
c38ee08720
6 changed files with 92 additions and 29 deletions
|
|
@ -169,3 +169,12 @@ without them load as `unknown`, rather than implying that cleanup or reporting
|
|||
occurred. Consumers using older strict schemas must update to accept these
|
||||
fields before consuming new serialized results. No profile pins or readiness
|
||||
states change with this addition.
|
||||
|
||||
## Sandbox handoff validation (GLAS-WP-0014)
|
||||
|
||||
The synchronous create handoff must return a READY sandbox before any rein
|
||||
method starts. Non-ready returns fail at sandbox_create and trigger destruction
|
||||
of the returned sandbox. Errors preparing its reachability or SandboxHandle
|
||||
fail at session_start, with destruction still attempted. Readiness here is the
|
||||
owner lifecycle state; it does not promote a Glas profile's operational
|
||||
readiness or independently prove runtime/provider health.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue