Skip to content

#386 follow-ups from #622: crash gap for linked children, reminder edge cases, test gaps #625

Closed

Description

@scuttletoby

Follow-ups from the review of #622 (Part of #386): #622 (comment)

Major (why #386 stays open): if the server stops between starting a child on another environment and recording it here, that child is only found when an agent runs task_list with checkLinked; nothing reminds the parent. #412 said part 2 would close this; #622 does not. Close it (a startup or periodic scan that reminds the parent), then close #386.

Minors (details and file:line in the review comment):

  1. A wait-mode task whose acknowledgement fails lands in the "no delivery record" group and is never reminded.
  2. A parent with a long-running background task or an open question counts as busy and is never reminded.
  3. After a restart, the startup scan only finds parents whose upstream completion wake was already reserved.
  4. The reminder can arrive just after upstream's own wake; its wording then says the result never arrived.
  5. Remote children: the slot count can be one too low; an unreachable environment slows task_list.
  6. The orphan search reads only the newest 100 threads per environment (taskList.ts:216); say so or page.
  7. Five surviving mutants (listed in the review, Minor 7): add tests that kill them.
  8. Tool description could be about 60 bytes shorter.
  9. FORK_CHANGES.md table was re-padded; avoid re-padding to keep other PRs conflict-free.

Activity

  1. added 3 commits that reference this issue on Nov 21, 2026
    48a4b1e
    195b508
    a68f966
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions