S00-028: Record blocked task and remediation handoff

Changes: Preserve incomplete work and blocker metadata for S00-028. This checkpoint does not mark implementation accepted.
Validation: Session ended with status blocked.
Blocker: S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.
Automatic blocker limit reached; explicit external resolution required.

Task: S00-028
Agent: auto-ci-cd-211cf3a2bd08
Role: ci-cd
Action: claim
Status: blocked

Task title: Repair conflicting Codex harness sandbox arguments

state/blockers/S00-030.md

@@ -0,0 +1,23 @@
+# Blocker S00-030
+
+- Original task: S00-028
+- Root task: S00-005
+- Reporter: auto-ci-cd-211cf3a2bd08
+- Role: ci-cd
+- Original owner: auto-ci-cd-211cf3a2bd08
+- Waits for user/external condition: True
+
+## Cause
+
+S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.
+Automatic blocker limit reached; explicit external resolution required.
+
+## One remediation outcome
+
+Coordinator provides a valid private app-server socket environment and a bounded no-model Codex sandbox probe executes with project write restrictions intact.
+
+## Evidence / reproduction
+
+codex -c 'sandbox_mode="workspace-write"' -c sandbox_workspace_write.network_access=true sandbox -- python3 -c '<synthetic project write/read/remove probe>' exits 1: error building bubblewrap command: app-server socket directory must be a user-owned directory with mode 0700. See state/evidence/S00-028-auto-ci-cd-211cf3a2bd08.md.
+
+The reporting agent must stop now. A new agent implements only S00-030.

state/evidence/S00-028-auto-ci-cd-211cf3a2bd08.md

@@ -0,0 +1,24 @@
+# S00-028 launcher validation — incomplete
+
+Executor: auto-ci-cd-211cf3a2bd08 (ci-cd), 2026-10-15.
+Input: assigned card/packet and required documents; coordinator release-external event revision 77 in state/tasks.json. Output intended: compatible fresh launcher with project write sandbox. No source changes performed.
+
+## Findings
+
+Coordinator already removed the conflicting --sandbox before this session. Active argv: `codex -c sandbox_workspace_write.network_access=true exec --approve-for-me --ephemeral -`; commands_by_role is empty. Coordinator event records a subsequent fresh harness reaching its own escalation; this is historical evidence, not an independent fresh-model smoke check here. Original storage tasks were neither executed nor marked complete.
+
+Official reference opened: https://learn.chatgpt.com/docs/cli/reference . It documents --approve-for-me as automatic approval review with workspace-write, conflicting with --sandbox. Installed help agrees. The active configuration was preserved; no new model/agent was launched.
+
+## Actual commands/results
+
+- `python3 scripts/tasks.py resume --agent auto-ci-cd-211cf3a2bd08` and `show S00-028`: exit 0 each; assigned in_progress.
+- Required document/dependency reads succeeded. Optional previous state/handoffs/S00-028.md does not yet exist (fresh remediation); batched cat exit 1 for that path. An exploratory zsh glob state/history* also exited 1; canonical events were subsequently read from state/tasks.json successfully.
+- `codex --version`: exit 0, codex-cli 0.159.0.
+- `codex exec --help` and `codex sandbox --help`: exit 0 each. CLI warns PATH aliases could not be created on read-only filesystem; help still succeeds.
+- Python subprocess loads runner.local.json, invokes exact active argv plus --help with empty stdin and 15-second timeout; asserts exit 0, workspace-write in help, approve-for-me present, sandbox absent, empty role overrides: wrapper and child exit 0. This checks parsing only; no model or product task runs.
+- `codex -c 'sandbox_mode="workspace-write"' -c sandbox_workspace_write.network_access=true sandbox -- python3 -c '<synthetic project write/read/remove probe plus mount inspection>'`: exit 1 BEFORE the probe executes. Error: `error building bubblewrap command: app-server socket directory must be a user-owned directory with mode 0700`. Intended synthetic path: state/evidence/.S00-028-sandbox-probe. No sandbox write or mount inspection result exists; neither is claimed passed. Explicit sandbox_mode in this diagnostic selects the policy implied by approve-for-me; the active argv is unchanged.
+- Initial `git status --short --untracked-files=all`: exit 0; only coordinator claim state/tasks.json modified. No Git mutations.
+
+## Blocker
+
+Independent filesystem sandbox validation cannot run in the current host socket environment. Correcting host socket ownership/mode is outside this card's launcher arguments/documentation scope. No chmod, socket/config change, sandbox bypass, new model, storage work, or source edit attempted. Separate atomic remediation must provide a correctly owned/private socket environment and repeat the bounded no-model sandbox diagnostic. Original launcher repair remains unaccepted.

state/handoffs/S00-028.md

@@ -0,0 +1,9 @@
+# S00-028 blocked handoff
+
+Executor: auto-ci-cd-211cf3a2bd08, ci-cd. No source changes. Coordinator event revision 77 supplies the already corrected active argv: codex -c sandbox_workspace_write.network_access=true exec --approve-for-me --ephemeral -. Installed CLI 0.159.0 and exact-argv help parsing succeed (exit 0). No product/storage work or fresh model was launched.
+
+Independent filesystem validation is blocked: `codex -c 'sandbox_mode="workspace-write"' -c sandbox_workspace_write.network_access=true sandbox -- python3 -c '<synthetic project write/read/remove and mount inspection>'` exits 1 before command execution: `error building bubblewrap command: app-server socket directory must be a user-owned directory with mode 0700`.
+
+Next input: host/coordinator must supply a Codex sandbox socket environment whose directory satisfies ownership and 0700 mode, without broadening filesystem permissions or bypassing sandbox. A fresh remediation executor/reviewer must verify the bounded no-model diagnostic. After reviewed resolution, a new S00-028 executor should finish filesystem verification and document the coordinator-selected supported argv, then submit for QA. Do not resume this reporter id or mark storage tasks done.
+
+Evidence: state/evidence/S00-028-auto-ci-cd-211cf3a2bd08.md. Active config preserved. No application readiness, successful sandbox write, or new harness model execution is claimed.

state/issues/S00-028-auto-ci-cd-211cf3a2bd08.json

@@ -0,0 +1,28 @@
+{
+  "title": "Provide a valid Codex sandbox app-server socket directory",
+  "reason": "S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.",
+  "reproduction": "codex -c 'sandbox_mode=\"workspace-write\"' -c sandbox_workspace_write.network_access=true sandbox -- python3 -c '<synthetic project write/read/remove probe>' exits 1: error building bubblewrap command: app-server socket directory must be a user-owned directory with mode 0700. See state/evidence/S00-028-auto-ci-cd-211cf3a2bd08.md.",
+  "role": "ci-cd",
+  "reviewer_role": "qa",
+  "scope": [
+    "docs/AUTOMATION.md"
+  ],
+  "outcome": "Coordinator provides a valid private app-server socket environment and a bounded no-model Codex sandbox probe executes with project write restrictions intact.",
+  "steps": [
+    "Read S00-028 evidence and coordinate host socket environment ownership/mode correction without changing product files",
+    "Document the supplied supported host setup in docs/AUTOMATION.md",
+    "Run a bounded no-model project write/read/remove and filesystem restriction diagnostic",
+    "Record evidence and submit for independent QA"
+  ],
+  "acceptance": [
+    "Codex sandbox no longer fails with the socket directory ownership/mode error",
+    "Project write sandbox remains enforced without bypass or broader writable roots",
+    "No storage task or additional model is executed"
+  ],
+  "checks": [
+    "Bounded codex sandbox diagnostic executes a synthetic project write/read/remove probe",
+    "Verify effective filesystem restrictions and record exact exit codes"
+  ],
+  "depends_on": [],
+  "requires_user_input": true
+}

state/tasks.json

@@ -1,6 +1,6 @@
 {
   "schema_version": 1,
-  "revision": 91,
+  "revision": 93,
   "tasks": {
     "S00-001": {
       "status": "done",
@@ -1399,16 +1399,30 @@
       "completed_at": "2026-10-15T10:14:41+00:00"
     },
     "S00-028": {
-      "status": "todo",
-      "owner": null,
+      "status": "blocked",
+      "owner": "auto-ci-cd-211cf3a2bd08",
       "external_wait": false,
-      "reason": "Coordinator supplies the active compatible argv from runner.local.json: codex -c sandbox_workspace_write.network_access=true exec --approve-for-me --ephemeral -. Explicit --sandbox was removed before the S00-024/S00-022/S00-025 fresh agent launches. --approve-for-me retains workspace-write per installed CLI help; no danger-full-access or bypass option. Actual subsequent run state/runs/auto-storage-ae5930b6fbdf/run.json shows the fresh harness executed tools and reached its own escalate, unlike the original immediate CLI exit 2. Installed CLI bounded help check codex exec --approve-for-me --ephemeral --help exited 0. Outbound network config retains existing proxy and TLS, independently probed via codex -c sandbox_mode='\"workspace-write\"' -c sandbox_workspace_write.network_access=true sandbox -- python3 /tmp/luma-probe-registry.py, exit 0; state/runs/coordinator-network/output.log. Fresh S00-028 executor/QA must verify supported argv and filesystem scope; no storage task completion or launcher repair acceptance claimed."
+      "reason": "S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.\nAutomatic blocker limit reached; explicit external resolution required.",
+      "started_at": "2026-10-15T10:24:24+00:00",
+      "updated_at": "2026-10-15T10:26:44+00:00",
+      "blocked_by": [
+        "S00-030"
+      ],
+      "resume_status": "in_progress",
+      "blocker_report": "state/blockers/S00-030.md",
+      "handoff": "state/handoffs/S00-028.md"
     },
     "S00-029": {
       "status": "blocked",
       "owner": null,
       "external_wait": true,
       "reason": "Pinned libomemo.js@3.0.0 supplies real embedded WASM but is a different unaudited ratchet and excludes consumer SCE; no approved decision reconciles it with S00-022 retained audited engine/persistence requirement."
+    },
+    "S00-030": {
+      "status": "blocked",
+      "owner": null,
+      "external_wait": true,
+      "reason": "S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.\nAutomatic blocker limit reached; explicit external resolution required."
     }
   },
   "events": [
@@ -2568,6 +2582,29 @@
       "from": "in_progress",
       "to": "blocked",
       "reason": "Pinned libomemo.js@3.0.0 supplies real embedded WASM but is a different unaudited ratchet and excludes consumer SCE; no approved decision reconciles it with S00-022 retained audited engine/persistence requirement."
+    },
+    {
+      "revision": 92,
+      "at": "2026-10-15T10:24:24+00:00",
+      "action": "claim",
+      "task": "S00-028",
+      "agent": "auto-ci-cd-211cf3a2bd08",
+      "role": "ci-cd",
+      "from": "todo",
+      "to": "in_progress",
+      "reason": null
+    },
+    {
+      "revision": 93,
+      "at": "2026-10-15T10:26:44+00:00",
+      "action": "escalate",
+      "task": "S00-028",
+      "resolution_task": "S00-030",
+      "agent": "auto-ci-cd-211cf3a2bd08",
+      "role": "ci-cd",
+      "from": "in_progress",
+      "to": "blocked",
+      "reason": "S00-028 cannot independently validate project filesystem sandbox: installed Codex sandbox exits before command execution because the app-server socket directory must be user-owned with mode 0700. Host socket repair is outside launcher arguments scope.\nAutomatic blocker limit reached; explicit external resolution required."
     }
   ],
   "retired_agents": [
@@ -2589,6 +2626,7 @@
     "auto-ci-cd-988167c541cf",
     "auto-crypto-316a193d6c3e",
     "auto-storage-ae5930b6fbdf",
-    "auto-crypto-bcd7f2a71667"
+    "auto-crypto-bcd7f2a71667",
+    "auto-ci-cd-211cf3a2bd08"
   ]
 }