Tianyi Cui 9c1048f2b5 Honor an already-aborted request signal in the subagent driver (Codex review round 2) ...

A request signal aborted BEFORE the run starts never fires an `abort` event
(`addEventListener` only fires on the transition), so the backend-level bridge
missed it and ran the child to `completed`. The driver now checks
`request.signal?.aborted` at the top of the result path and settles `aborted`
without running the child. Regression test proven red on the pre-fix code.

Also refresh two stale RFC prose blocks the round-1 fix left behind: the
subagent RFC's Problem statement (cited the removed `TODO(sub-agents)` markers
and claimed nothing existed yet) and the unify-id RFC's fork/spawn risk bullet
(described the seam as "explicitly deferred" via `AgentLoop.create`'s old TODO),
now pointing at the realized seam.

2026-06-22 07:32:09 +08:00

..

harness.ts

Add in-process subagent backends: spawn (fresh) and fork (seeded)

2026-06-22 05:58:40 +08:00

spawn.e2e.ts

Add in-process subagent backends: spawn (fresh) and fork (seeded)

2026-06-22 05:58:40 +08:00

subagent-spawn.spec.ts

Honor an already-aborted request signal in the subagent driver (Codex review round 2)

2026-06-22 07:32:09 +08:00