Repository navigation
v1.4.4 · Concurrent check runs
Added
setup-snappedly-skillsrecords which checks two worktrees on one machine cannot run at the same time, in a new Concurrent runs section ofdocs/agents/workflow.md. Each entry names the shared resource the check holds or removes, such as a fixed port, a container name, or a cleanup of every container carrying a label.
Changed
code-cleanupchecks for another worktree's run before starting a check listed under Concurrent runs. When a check fails because a port or other resource is taken, or another run removed what the check created, it finds that run, leaves it running, and reruns once after it exits. A repeated collision is recorded as blocked, naming the other run and the resource, rather than as a failure of the change, and is reported as a gap the repository can close by making the check safe to run concurrently.executeworkers run only focused checks. Full suites, builds, and the checks listed under Concurrent runs run once on the combined result, since the workers share one machine.
Updating existing repositories
Rerun setup-snappedly-skills to add the Concurrent runs section to docs/agents/workflow.md. Setup fills it from each check's configuration and moves any port or resource note already recorded for a check into it.