Skip to content

lane-orders: the report file lives in the lane's worktree under isolation - #4021

Merged
erikdarlingdata merged 1 commit into
devfrom
docs/lane-orders-report-in-worktree
Sep 23, 2026
Merged

erikdarlingdata merged 1 commit into
devfrom
docs/lane-orders-report-in-worktree

Conversation

@erikdarlingdata

Copy link
Copy Markdown
Owner

A small addition to the lane-orders skill. Under worktree isolation the harness blocks an agent's writes to the coordinator's scratchpad, so <REPORT_FILE> must be inside the lane's own worktree. The note also records that isolated worktrees live under .claude/worktrees/ inside the repo, which repo-scanning tests must not exclude. #4020 fixed two that did. Docs only.

🤖 Generated with Claude Code

https://claude.ai/code/session_01GdmA4ND1wLSqA91ax1m4xv

…ne's worktree

An isolated lane (#4020's) was refused a write to the coordinator's
scratchpad, so its report came back only as its final message. Isolated
worktrees also sit under .claude/worktrees/ inside the repo, which two
repo-scanning tests excluded (fixed in #4020).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GdmA4ND1wLSqA91ax1m4xv
@erikdarlingdata
erikdarlingdata enabled auto-merge (squash) September 23, 2026 11:36
@erikdarlingdata
erikdarlingdata merged commit ea551a2 into dev Sep 23, 2026
15 of 16 checks passed
@erikdarlingdata
erikdarlingdata deleted the docs/lane-orders-report-in-worktree branch September 23, 2026 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant