Skip to content

Record the Crew-stop replay test under FORK.md case 3 #232

Closed

Description

@bryantderosier

FORK.md requires every touch of an upstream file to be recorded in the appended-integration inventory. apps/server/src/orchestration-v2/runtimeLayer.test.ts is listed under case 3, but case 3 names only the delivery-dedup test ("replays an internal thread send without injecting a second message"). The file also carries a J5 Crew test at line 1764, "replaying a Crew stop does not dispatch a second real interrupt", added with the Crew stop work, and the inventory does not mention it.

What should change:

  • Add one sentence to FORK.md case 3 naming the Crew stop replay test and what it proves, so a rebase that drops it is recognized as a regression.

Done when case 3 names both J5 tests in that file.

Activity

  1. added this to the Crews milestone on Sep 21, 2026
  2. added
    size:XS0-9 effective changed lines (test files excluded in mixed PRs).
    on Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

size:XS0-9 effective changed lines (test files excluded in mixed PRs).

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions