Codex overall-timeout (3600s) not enforced: implement codex hung 11h on quiet scripts/run.sh test, freezing the devloop pipeline (open_pr 0 success); suspect #135 flush blocks the timeout wait loop

[loning]

github-devloop implementation PR for issue #139

[loning]

github-devloop implementation PR for issue #139

[loning]

github-devloop PR is ready for review

[loning]

github-devloop PR review decision: reject
Three-angle verdicts: minimal=reject structural=reject delete=reject
Blocking gap: Unfixed stdout-drain durable-publish deadlock path

minimal:
Established process-supervision practice requires a parent-owned monotonic watchdog outside child stdout/stderr drain and durable publish paths; this diff only bounds local spawn_codex_sync/adoption waits in sdk_codex.rs, while the producer context refined the accepted root to stdout_observer → publish_raised_events → router.publish blocking pipe drain, so the minimal accepted path still lacks proof or code that the DEFAULT_CODEX_TIMEOUT_SECONDS watchdog dominates the actual #135 drain/publish deadlock path.

structural:
Established process-supervision practice requires a parent-owned monotonic watchdog and nonblocking stdout/stderr drainage, with durable publication kept off the pipe-drain path; this diff mostly changes sdk_codex.rs timeout handling (run_codex_sync_request, try_lock_until_deadline, wait_codex_with_timeout_and_tail) but leaves the stated #135 deadlock boundary stdout_observer → publish_raised_events → router.publish untouched, so the core data-flow and module-boundary violation can still freeze the child stdout drain before DEFAULT_CODEX_TIMEOUT_SECONDS is enforced.

delete:
Established process-supervision practice requires a parent-owned monotonic watchdog outside child I/O, buffering, durable publish, and adoption bookkeeping; the delete-angle bar is to remove or make nonblocking the unnecessary blocking surface, not add another wrapper around it. The diff adds run_codex_sync_request, bounded lock waiting, and timeout tests, but it does not delete, make no-op, or decouple the diagnosed stdout_observer → publish_raised_events → router.publish durable-publish path that can block pipe draining and prevent the existing DEFAULT_CODEX_TIMEOUT_SECONDS/spawn_codex_sync watchdog from running, so the proposed surface does not prove necessity and leaves the class defect alive.

⟦AI:FKST⟧

[loning]

github-devloop reaped this managed PR because its parent issue is terminal.

Parent: #139
Reason: Parent issue #139 is closed.
Successors: 0 successor issue(s)
Branch cleanup is intentionally left to a separate manual or managed path.