Skip to content

Gnhf/continue release rea 875ed7 1 - #31

Merged
Laaaaksh merged 3 commits into
masterfrom
gnhf/continue-release-rea-875ed7-1
Aug 22, 2026
Merged

Gnhf/continue release rea 875ed7 1#31
Laaaaksh merged 3 commits into
masterfrom
gnhf/continue-release-rea-875ed7-1

Conversation

@Laaaaksh

Copy link
Copy Markdown
Owner

What does this PR change?

How was it verified?

Run all three locally before opening - CI runs exactly these on every PR:

go build ./...
go vet ./...
go test ./...
  • All three commands pass on my machine
  • The fixed lifecycle (propose -> approve -> implement -> attest/unattest -> status/merge, discard) still works if this change touches it
  • No new dependencies beyond spf13/cobra and BurntSushi/toml

…nd a dedicated macOS runner to ci.yml (validated with actionlint), and added a GitHub issue-form feature_request.yml template, with AGENTS.md updated to capture the branch-protection check-name constraint behind those design choices.
…' fence with byte-real output captured from the real binary running the full loop on the README's own example writ, added a pasteable AGENTS.md/CLAUDE.md agent-discipline snippet section, and added an FAQ answering the four AI questions with every factual claim verified against the codebase first.
… all seven tagged releases (v0.1.0–v0.2.4) with an [Unreleased] section covering this run's post-v0.2.4 work, plus encoded the release-notes discipline in AGENTS.md — completing the last remaining stop-condition gap.
@Laaaaksh
Laaaaksh merged commit 8f0d88f into master Aug 22, 2026
4 checks passed
@Laaaaksh
Laaaaksh deleted the gnhf/continue-release-rea-875ed7-1 branch August 22, 2026 14:20
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.

1 participant