fix(gateway): settle a lost yielded child after restart so its parent wakes (#202000)

Problem: after a Gateway restart, startup failed a yielded child whose wake source could not survive the restart, but only in the child's session lifecycle. Its registry run stayed held as yielded, so the parent's owed completion never arrived and the parent stayed parked until a human wrote to it.

Fix: after the existing lifecycle failure, the exact yielded run is settled through the existing completion owner (completeSubagentRunWithRecovery with settleYielded, the unchanged terminal error, and normal cleanup and delivery). suppressSessionEffects only prevents a duplicate visible failure on the child; the parent is still notified. The owner selects the exact runId, refuses non-yielded rows, and is a no-op without a registry entry.

Proof: source tier (ocx test). New regression through the real resumeMarkedSessions startup path: red on unchanged main (child session failed, registry outcome undefined); green on the fix (one parent agent request with subagent_settle provenance, delivered-cleanup acknowledgment). 12 restart-resume and registry pause/yield/settle files; tsgo, test types, oxlint, format, lifetime-check, line-cap and session-identity ratchets; clean exact-head local ClawSweeper review; ocx build --dts plus packed install smoke on the head.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>