glas-harness/workplans/GLAS-WP-0014-sandbox-handoff-validation.md
repo-manager 31dd5aaca8
All checks were successful
ci / validate (push) Successful in 1m19s
repo.work.assign_missing_identifiers
source: repo-manager
reason: deterministic projection registration

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0726e-5232-73f2-aaca-2c05ceb62efb
2026-09-06 14:52:31 +02:00

37 lines
1.3 KiB
Markdown

---
id: GLAS-WP-0014
type: workplan
title: "Validate sandbox readiness before rein handoff"
domain: infotech
repo: glas-harness
status: active
owner: codex
topic_slug: sandbox-handoff-validation
created: "2026-09-06"
updated: "2026-09-06"
state_hub_workstream_id: "7fd7f846-8bb9-5409-b818-5fbdb8d884ba"
---
# Sandbox handoff validation
Review found that the gateway accepts any returned sandbox state and prepares
reachability outside its stage-specific exception handling. An owner returning
a non-ready sandbox must not reach rein startup; preparation errors must carry
normalized failure evidence while preserving destruction attempts.
## Validate and report the owner handoff
```task
id: GLAS-WP-0014-T01
status: progress
priority: high
state_hub_task_id: "64b1e1ab-421b-566d-b2ee-64284446db8a"
```
Require READY after create returns an identified sandbox. Classify non-ready
returns as sandbox_create failures and reachability/handle preparation errors
as session_start failures. Refuse before rein methods or owner exec, destroy
the returned sandbox, and keep raw error details out of Hub evidence. Preserve
successful behavior and existing cleanup status semantics. Add regression
coverage for non-ready states and malformed reachability; run the full suite
and catalog validation. No owner implementation or profile readiness changes.