garrytan a1b21407eb refactor(pty): one runPtySession loop drives observation, counting and floor ...

test/helpers/pty/session.ts owns launch -> start -> (poll -> tick)* ->
timeout and the failure contract the three runners each hand-rolled: the
run's own error wins over capture and close errors, close always runs, owned
fixture cleanup runs last (also when launch fails). Each runner now supplies a
PtySessionPlan: its boot/command step, poll cadence (2s observation/floor
sleep; counting's output wake + 250ms coalesce), tick policy (permission
handling, native identity, terminal rules stay per runner because they differ)
and capture hooks. The runner bodies are decomposed into top-level steps so no
function exceeds 150 lines; behavior is unchanged and the fake-driver cases
from the first W4 commit pass unmodified.

The counting capture step and the native completion-summary predicate are now
named functions (countingCapture, isNativeCompletionSummary), so
plan-create-prepublication and plan-count-completion call them directly
instead of executing sliced source. The two harnesses that still execute a
sliced runner body with injected boundaries (eng-seeded-completion-ai,
plan-floor-permission) pass the PtyDriver seam instead of overriding
Date/Bun.sleep.

2026-09-30 06:15:24 +00:00

..

counting.ts

refactor(pty): one runPtySession loop drives observation, counting and floor

2026-09-30 06:15:24 +00:00

floor.ts

refactor(pty): one runPtySession loop drives observation, counting and floor

2026-09-30 06:15:24 +00:00

observation.ts

refactor(pty): one runPtySession loop drives observation, counting and floor

2026-09-30 06:15:24 +00:00