Prevent generic OpenSpec task reuse#451
Merged
NagyVikt merged 1 commit intoApr 29, 2026
Merged
Conversation
The dirty-worktree continuation matcher treated the shared word OpenSpec as a meaningful task token. That made an openspec-disabled setup test reuse the dirty openspec-default sandbox and lose the expected plan/change slug output path. The matcher now ignores OpenSpec as a generic workflow word, while template parity keeps installed starters aligned. The full test run also exposed stale assertions for the current managed AGENTS wording and a missing README package-summary anchor, so those test surfaces now match the shipped contract. Constraint: Primary main had unrelated dirty files, so the fix was developed in a clean isolated agent worktree. Rejected: Print slugs for reused worktrees only | would hide the false-positive reuse and still route distinct OpenSpec tasks into the wrong sandbox Confidence: high Scope-risk: narrow Directive: Keep scripts/agent-branch-start.sh and templates/scripts/agent-branch-start.sh in parity when changing bootstrap matching logic. Tested: bash -n scripts/agent-branch-start.sh Tested: bash -n templates/scripts/agent-branch-start.sh Tested: node --test --test-name-pattern "setup agent-branch-start supports optional OpenSpec auto-bootstrap toggles" test/setup.test.js Tested: node --test test/setup.test.js test/branch.test.js Tested: node --test --test-name-pattern "doctor refreshes existing managed AGENTS block by default|README keeps canonical About copy and problem-solution visuals aligned|setup agent-branch-start supports optional OpenSpec auto-bootstrap toggles" test/doctor.test.js test/metadata.test.js test/setup.test.js Tested: npm test Not-tested: GitHub Actions rerun
NagyVikt
deleted the
agent/codex/fix-setup-openspec-reuse-output-2026-04-29-11-34
branch
Merged
NagyVikt
added a commit
that referenced
this pull request
Apr 29, 2026
The npm registry is still at 7.0.41 while main contains the agent-session and cockpit work from PRs #451 through #473, so this assigns the next patch version and records release notes for that payload. Constraint: Release work must keep package metadata and README release notes in sync. Rejected: Retag or republish 7.0.41 | npm versions are immutable and the registry already reports 7.0.41. Confidence: high Scope-risk: narrow Directive: Do not publish without confirming npm still lacks 7.0.42. Tested: node --test test/metadata.test.js Tested: node --check bin/multiagent-safety.js Tested: npm pack --dry-run Tested: openspec validate --specs Tested: git diff --check Not-tested: Full npm test; current baseline is known red outside this release metadata lane. Co-authored-by: NagyVikt <nagy.viktordp@gmail.com>
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
1 participant
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.
Automated by gx branch finish (PR flow).