name	squad-worktree-lifecycle
description	Handle ai-agent-board git worktree and merge flows safely.
domain	git
confidence	medium
source	ai-agent-board worktree lifecycle and architecture

Use for changes to worktree creation, path rewriting, merge-local, PR creation, cleanup, or agent session repo paths.

Neo owns runtime/worktree mechanics; Cypher reviews path safety; Switch verifies behavior.
Preserve the per-repo mutex for operations that checkout/merge branches.
Auto-abort merge conflicts and surface explicit errors.
Clean up worktrees only after successful merge or PR flow.

A merge-local change needs conflict behavior evidence and branch-safety review.
A path rewrite hook change needs proof tools cannot escape the intended worktree.

Do not change branches inside an active worktree unexpectedly.
Do not normalize paths with string replacement alone when filesystem resolution is required.

Más de este repositorio

mismo repositorio

Require clear user-facing summaries after completed agent batches.

Keep client API calls, Express routes, and shared types aligned.

Run risk-based ai-agent-board quality gates after code-producing work.

Detect stale Squad heartbeat and require visible progress updates.

Use telemetry evidence for Squad usage and process audits when available.

Clean up orphaned browser/test/dev-server processes safely after test bursts.

name	squad-worktree-lifecycle
description	Handle ai-agent-board git worktree and merge flows safely.
domain	git
confidence	medium
source	ai-agent-board worktree lifecycle and architecture

Use for changes to worktree creation, path rewriting, merge-local, PR creation, cleanup, or agent session repo paths.

Neo owns runtime/worktree mechanics; Cypher reviews path safety; Switch verifies behavior.
Preserve the per-repo mutex for operations that checkout/merge branches.
Auto-abort merge conflicts and surface explicit errors.
Clean up worktrees only after successful merge or PR flow.

A merge-local change needs conflict behavior evidence and branch-safety review.
A path rewrite hook change needs proof tools cannot escape the intended worktree.

Do not change branches inside an active worktree unexpectedly.
Do not normalize paths with string replacement alone when filesystem resolution is required.