Skip to content

fix: track spec files in git and regenerate ERROR_CODES.md (G-081 + M1-26)#21

Merged
teragrid merged 1 commit into
mainfrom
fix/error-codes-spec-tracking
May 31, 2026
Merged

fix: track spec files in git and regenerate ERROR_CODES.md (G-081 + M1-26)#21
teragrid merged 1 commit into
mainfrom
fix/error-codes-spec-tracking

Conversation

@teragrid
Copy link
Copy Markdown
Owner

Summary

Fixes two CI gate failures that were present on the now-merged PR #19:

  • G-081 — docs/ERROR_CODES.md drift: regenerated after FORGE-6553/FORGE-6554 errcode registrations were added
  • M1-26 — spec-presence gate: .gitignore was excluding all .forge/specs/\ directories; added !.forge/specs/\ negation to un-ignore the top-level project spec directory and committed all 3 project specs

Root causes

Gate Root cause
G-081 \docs/ERROR_CODES.md\ was not regenerated after adding FORGE-6553, FORGE-6554 error code registrations in \internal/cli/cmdbugfix/bugfix.go\
M1-26 .gitignore\ rule **/.forge/specs/\ excluded all spec files from git; CI checkout found 0 spec.md files

Changes

  • \docs/ERROR_CODES.md\ — regenerated (111 codes total; \go run ./cmd/gen-errors --check\ exits 0)
  • .gitignore\ — added !.forge/specs/\ negation + .playwright-mcp/\ ignore entry
  • .forge/specs/\ — 3 project spec directories now tracked in git
  • \ ests/\ — LLM-driven automation testing MCP integration test stubs

Pre-push results

All 13 checks passed. 33/33 QA tests passed.

- .gitignore: un-ignore top-level .forge/specs/ so spec.md files are committed
  (M1-26 spec-presence gate requires at least one spec.md under .forge/specs/)
- docs/ERROR_CODES.md: regenerated (111 codes) — fixes G-081 drift gate
- .forge/specs/: add all three project specs (explain, forge-ship-v2-rfc-005, llm-driven-automation-testing-mcp-integration)
- tests/: add LLM-driven automation testing stubs
- AGENTS.md: add language policy (chat: EN/VI, docs: EN only)
@teragrid teragrid merged commit 65cac00 into main May 31, 2026
17 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants