chore(specgit): enable SpecGit delivery harness - #354
Merged
Conversation
- spec_git/policy.yaml: required check 'Typecheck' (dev-layer gate parity) - specgit-accept.yml: PR-to-dev acceptance evaluation - .opencode/command: /specgit-issue, /specgit-finish entry points - .opencode/hooks/specgit-merge-guard.sh: merge guard script (wired by specgit setup) - AGENTS.md/CLAUDE.md: managed specgit block Closes#353
specgit issue regenerated the harness with the repo default branch (main); delivery PRs in this repo target dev (layered gating), so the trigger must be [dev].
Generated harness assumed the SpecGit repo's own pnpm toolchain. This repo is a bun workspace without packageManager/pnpm-lock: setup-node + npm i -g specgit, minimal policy.yaml parsing without a yaml dependency.
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 freeto 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#353
What
Enables the SpecGit delivery harness for this repository (delivery = issue + branch + PR binding + evidence-gated finish):
spec_git/policy.yaml— required checkTypecheck, matching the dev-layer PR gate (feat/** → dev). dev→main promotion stays governed by the protect-main Ruleset's four checks..github/workflows/specgit-accept.yml— acceptance evaluation on PRs to dev (retargeted from main for this repo's layered gating)..opencode/command/specgit-issue.md,specgit-finish.md— opencode command entry points (installed byspecgit setup --tool opencode)..opencode/hooks/specgit-merge-guard.sh— PreToolUse merge guard script;.opencode/hooks.jsonwiring is gitignored by repo policy and installed locally viaspecgit setup.AGENTS.md/CLAUDE.md— specgit managed block (rewritten on re-init; manual guidance stays outside the markers).Verification
specgit doctorsix probes green (git, repo, origin, gh_present, gh_authenticated, policy)