dispatch: invert surface-to-isolation mapping main vs worktree+branch #35

New issue

Closed

opened 2026-05-28 10:55:41 +00:00 by coilysiren · 1 comment

coilysiren commented

2026-05-28 10:55:41 +00:00

Owner

Consumer-driven by coilysiren/coily#145.

Isolation should track concurrency, not churn velocity. Today only the interactive surface uses a worktree, while the detached surfaces (headless, cascade) share the canonical checkout - exactly backwards, since the detached surfaces are the ones that fan out into multiple concurrent workers in one repo and race on a shared working tree/index.

Invert the mapping in cli-guard/dispatch:

headless, cascade (detached, parallel) -> per-issue worktree+branch. Each worker gets its own isolated working dir; lands by merging its branch into main when green.
interactive, consult (supervised, serial) -> run directly on the default branch in the canonical checkout. No worktree, no auto-merge dance; commit to main as the operator watches. Drops the --no-worktree escape hatch.

Worktree placement moves off interactive.go into worktree.go and onto runDetached; reaping follows the detached surfaces.

Consumer-driven by coilysiren/coily#145. Isolation should track concurrency, not churn velocity. Today only the `interactive` surface uses a worktree, while the detached surfaces (`headless`, `cascade`) share the canonical checkout - exactly backwards, since the detached surfaces are the ones that fan out into multiple concurrent workers in one repo and race on a shared working tree/index. Invert the mapping in `cli-guard/dispatch`: - `headless`, `cascade` (detached, parallel) -> per-issue worktree+branch. Each worker gets its own isolated working dir; lands by merging its branch into main when green. - `interactive`, `consult` (supervised, serial) -> run directly on the default branch in the canonical checkout. No worktree, no auto-merge dance; commit to main as the operator watches. Drops the `--no-worktree` escape hatch. Worktree placement moves off `interactive.go` into `worktree.go` and onto `runDetached`; reaping follows the detached surfaces.

coilysiren referenced this issue

2026-05-28 10:58:04 +00:00

cli-guard GitHub and Forgejo mirrors have diverged lockdown sync commit Forgejo-only #36

coilysiren commented

2026-05-28 11:04:27 +00:00

Author

Owner

Landed on GitHub main as cli-guard 02f4153. Closing manually: the cli-guard GitHub and Forgejo remotes have diverged (see #36), so the closes #35 trailer pushed to GitHub did not reach this Forgejo issue. Consumer bump landed in coilysiren/coily#145.

Landed on GitHub main as cli-guard `02f4153`. Closing manually: the cli-guard GitHub and Forgejo remotes have diverged (see #36), so the `closes #35` trailer pushed to GitHub did not reach this Forgejo issue. Consumer bump landed in coilysiren/coily#145.

coilysiren closed this issue

2026-05-28 11:04:28 +00:00

coilysiren referenced this issue from a commit

2026-05-28 12:37:36 +00:00

feat(dispatch): invert surface-to-isolation mapping (main vs worktree+branch)