Repository navigation
chore: adopt SpecGit 2.5 project integration and remove v1 leftovers - #723
Merged
Merged
Conversation
SpecGit 2.5.0 rejected the repository's integration: Prettier had reformatted the generated guidance block in AGENTS.md, so init/migrate/remove reported a damaged marker. - Regenerate the SpecGit-owned AGENTS.md blocks with 2.5.0 init and setup --agent opencode, and exclude AGENTS.md from Prettier so the tool-managed blocks stay byte-exact. - Untrack .specgit.yaml: 2.5 treats the declaration as per-checkout local configuration (already Git-excluded); document the init/setup commands. - Remove the uncalled v1-to-v2 bootstrap wrapper and its test. - Record the merge-commit-only rule in AGENTS.md and the release train.
LeXwDeX
marked this pull request as ready for review
October 8, 2026 15:11
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2e2af1bd68
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
2 tasks done
specgit init excludes .specgit.yaml through .git/info/exclude, but a tracked ignore rule also protects checkouts that receive the file another way from committing per-checkout delivery configuration.
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.
Closes #722
Why
SpecGit 2.5.0 rejected this repository's integration:
init,migrateandremovereported a damaged generatedmarker in
AGENTS.mdbecause Prettier had reformatted the managed block. The 2.5 model treats.specgit.yamlasper-checkout local configuration, but the repository still tracked it; the project
setupblock and thespecgit-nativeskill were missing; and the uncalled v1-to-v2 bootstrap wrapper remained.What changed
AGENTS.mdblocks with 2.5.0init(existing settings: github / origin / main / en /native auto-merge false) and
setup --agent opencode; removed the damaged 2.0.x block.AGENTS.mdfrom Prettier: it carries tool-managed blocks (SpecGit, Turborepo) verified byte-for-byte.Reformatting is what broke the old marker.
.specgit.yaml(kept locally; already excluded through.git/info/exclude) and documented theper-checkout
specgit init/specgit setupcommands.script/specgit-bootstrap.shand its test (no callers) and the stale reference in the installer boundarytest comment.
AGENTS.mdand the release train.Unchanged on purpose: CI fingerprint logic (its
.specgit.yamlexclusion is inert once the file is untracked) and theopt-in opencode Claude-compatible SpecGit hooks.
Evidence
specgit init --checkpasses;specgit statusinitialized;specgit setup --agent opencode --dry-runreports everyasset
unchanged;specgit remove --dry-runreports no damaged marker.prettier --checkpasses for the touched Markdown; commit hooks ran lint and the workspace typecheck.script/oc-install-boundary.test.sh9 passed;script/ci-fingerprint.test.mjs11 passed.specgit-bootstrapremains outside historical docs.Checklist
🤖 Generated with Claude Code