Changes: Preserve incomplete work and blocker metadata for S00-012. This checkpoint does not mark implementation accepted. Validation: Session ended with status blocked. Blocker: Submit-transition descendant regression fails: repeated stop_process_tree after parent reap raises EPERM at os.killpg; launch OSError handling then attempts invalid escalation from review state. Task: S00-012 Agent: auto-ci-cd-28868645424b Role: ci-cd Action: claim Status: blocked Task title: Fix runner prompt delivery after partial stdin timeout
3.6 KiB
S00-012 executor blocker evidence
Agent: auto-ci-cd-28868645424b; role: ci-cd; date: 2026-10-15. No submission or acceptance is claimed.
Input: assigned card/packet, startup instructions, prior partial handoff and diagnostic evidence, exact NFR-007, accepted scope ADR, S00-001/S00-011/S00-013 dependency evidence/reviews/handoffs. Output attempted: complete stdin delivery with verified lifecycle cleanup.
Preserved implementation and current changes
The checkpoint c28412a already contains the stdin correction and delayed-reader regression. It supplies the persisted binary UTF-8 prompt file as stdin, polls wait at .2-second intervals, and retains deadlines/terminal-transition/process-group cleanup. S00-013 subsequently corrected prompt budgeting independently. No runner source changes were made in this session.
Added two real subprocess regressions in tests/tooling/test_automation.py. A descendant installs SIGTERM ignore, records readiness, then attempts a delayed source write. The parent either times out or submits and remains alive. Tests require cleanup to prevent the write. These tests are preserved as partial work; the submit-transition test does not pass.
Actual commands/results
- tasks.py resume/show/packet: exit 0 each; S00-012 already owned, no repeated claim.
- git status --short at entry: exit 0; only coordinator state/tasks.json claim metadata modified.
- git log for S00-012 and git show
c28412ascoped source: exit 0; prior checkpoint inspected. - Synthetic legacy transport reproduction: exit 0; Python 3.9.6, 140000 UTF-8 bytes, .5-second delayed reader, communicate(payload, timeout=.2) then communicate(None, timeout=1) both time out. Child killed/reaped in finally.
- python3 -m unittest discover -s tests/tooling -p test_automation.py -v: exit 1; 26 tests in 9.489s, 25 passed, submit descendant test errored. Complete 140024-byte delayed UTF-8 prompt/EOF, timeout descendant, fresh-session chain, scope, escalation transition and both prompt-budget regressions passed.
- Isolated RunnerTests._check_descendant_cleanup(True) invocation: exit 1; same error reproduced.
- Same isolated invocation with an in-memory tracing wrapper around stop_process_tree: exit 1; first stop_process_tree succeeded and parent returncode was -15; second invocation with parent already reaped raised PermissionError [Errno 1] Operation not permitted at runner.py:340, os.killpg(process.pid, SIGTERM). No persistent tracing/source change.
- git diff --check and git diff --stat: exit 0; only tests/tooling/test_automation.py plus coordinator state metadata changed.
Blocker and limits
After submit, stop_process_tree runs during transition handling and again in finally. With a SIGTERM-ignoring descendant and reaped parent, the second process-group signal is denied in this managed execution environment. The broad launch OSError handler then treats this as executable startup failure; escalation from an already submitted executor raises ValueError: Only current executor or assigned-role reviewer may escalate its current task. Timeout descendant test passes; transition descendant cleanup cannot be declared passed. The precise sandbox/OS policy causing EPERM is not proven beyond the observed syscall result.
Stop source edits and remediate this one lifecycle failure in a new session. Preserve real descendant termination, deadline/transition monitoring and fail-closed behavior for inaccessible live processes; do not simply suppress permission errors. make check was not run after establishing the blocker, and the automation suite is not passed. No actual model, product/provider integration, Git mutation, immutable spec or shared-contract change occurred.