Repository navigation
JWB-964: Supervisor-launched lanes report back and finish without nudges - #97
Merged
Merged
Conversation
- interlock run --orchestrator THREAD tells launched lanes their orchestrator and reports each approved-and-unmerged head and each attention episode there once, through t3 thread send, journaled per lane. - Launched lane threads are titled "🔨 KEY: summary". - lane submit titles the PR from the ticket, takes --body-file, and a resubmit edits the existing PR's title and body. - A submitted or reviewing lane accepts a new head as its next round. - lane grant-round raises the round limit, journals review_round_granted and resumes a lane held at the limit. - gh and git failures carry their stderr (credentials redacted); a lane whose reads fail five ticks in a row moves to attention instead of retrying. - Unknown commands suggest the closest one; --only warns about a key no map lists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Report ready only while the PR tip is the approved head. - A lane held at its round limit cannot be resumed; grant-round is accepted only at the limit and not for other attention reasons. - Attention reports use the lane's recorded reason, skip lanes that did not end in attention, and suggest lane resume only for attention lanes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JarenKempton
enabled auto-merge (squash)
November 13, 2026 19:23
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supervisor-launched lanes now report back to an orchestrator and can finish without nudges.
interlock run --orchestrator THREADtells each launched lane its orchestrator and sends that thread one 🤖 message per approved-but-unmerged head and one per attention episode (with its reason), viat3 thread send, journaled assupervisor_reported. An undelivered report retries next tick.🔨 KEY: summary.lane submittitles the PR from the ticket (or--title), takes--body-file, and a resubmit edits the existing PR's title and body (gh pr edit).submitted/reviewinglane accepts a new head (e.g. a conflict resolution) as its next round, within the round limit.lane grant-roundraises the limit by one, journalsreview_round_granted, and resumes a lane held atreview_round_limit.read_failing: …instead of retrying forever.--onlywarns about a key no map lists.Acceptance evidence
AC1 — live, scratch state DB (
/tmp/agent-jwb964-*/state, never~/.local/state/interlock): fake HTTPS Jira (scratch ticket FAKE-1 in map FAKE-100), local bare git origin, real T3 server, real lane agent, and a scratch receiver thread as the orchestrator.Launched thread title:
🔨 FAKE-1: Live proof lane reports back; its prompt carriesOrchestrator:\nThread <receiver-thread>. Interlock reports this lane there…. The lane agent ranlane attach, thenlane attention --reason live_proof_blocked.Receiver thread got exactly one message:
The ready-to-merge report (approved head, not merged) is covered by
test/execution/supervisor/tick.test.tsand was not exercised live.AC4 + AC7 — live, same scratch DB
(That lane stays in attention because its reason is not
review_round_limit; a lane held at the limit resumes, per the unit test.)AC2, AC3, AC5, AC6 — tests on the real service and adapter paths with fake GitHub/T3 ports
submit titles the PR from the ticket, and a resubmit updates its title and bodyandupdate edits the PR title and body, then reads the PR back(exactgh pr edit … --title … --body …argv).a lane in review takes a new head as the next round, up to its round limit.the orchestrator hears each attention lane once, with its reason,an undelivered report is retried on the next tick, and the CLI-levelrun --orchestrator launches a 🔨 lane told its orchestrator, and reports its attention there once.failing gh and git calls carry their stderr, with credentials in URLs redactedanda read that keeps failing stops retrying at the limit and routes the lane to attention.Not verified live: AC2 against real GitHub (this PR was opened by the pre-change binary, so its title was the branch name; this body was set with one manual
gh pr edit).Checks at b3a50dc
Lane thread: 🔨 JWB-964: Lanes report back (
mcp:daf57c7c-ba9e-4bb8-a061-9b39ef5dc7bf)🤖 Generated with Claude Code