test(followups): F6 - the wrapper vanishes inside the second wait; the <= 60 s is the herdr wait's

delegate-job SKILL.md said a watcher outlives a killed wrapper by "one
wait, <= 60 s". That bound is the herdr wait's; a wrapper that goes while a
notice is being published is noticed when that publish ends. The text now
says both (PR #41 codex round 3).

"a wrapper gone during the wait" switched alive() by call count, so the
watcher saw the wrapper gone at the next loop head and never entered the
second wait (ticks == [1] with that band). The wrapper now vanishes inside
the second herdr wait (_during_notice's in_wait hook), and the test checks
that the second wait happened and that alive() was true until then. The
same test fails when the post-wait _wrapper_gone() check is removed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HCGpJXhSZasJLU38ksDghe

.agents/skills/multi-agent-mux-delegate-job/SKILL.md

@@ -50,8 +50,9 @@ multi-agent-mux-delegate-job submit \
   #   MAM_STALL_IDLE_S (600) / MAM_STALL_HERDR_FAIL_S (120) / MAM_STALL_WATCH=0: the stall watcher (Issue #30).
   #   The watcher lives as long as the job's wrapper: the wrapper stops it (KILL, at once)
   #   when its subscriber ends, and the watcher exits on its own once the wrapper pid is gone
-  #   (checked after every herdr wait, so it can outlive a killed wrapper by one wait, <= 60 s,
-  #   and never sends a notice or a nudge after it saw the wrapper gone).
+  #   (checked after every herdr wait, so it can outlive a killed wrapper by one herdr wait,
+  #   <= 60 s - or, when the wrapper goes while a notice is being published, until that
+  #   publish ends - and never sends a notice or a nudge after it saw the wrapper gone).
   #   --parent-job <id> (Issue #34): this job is delegated from job <id>, which
   #   must exist in the registry (else exit 1). A loop waiting on <id> waits for
   #   it too and shows it to reviewers. Default: $MAM_JOB_ID (the remote runner