Driver
The dev branch has accumulated 123 commits since the v1.3.0 tag (2026-05-18). This includes 6 new slash commands, a per-agent model routing layer, class-aware role activation, a security-reviewer agent rename (breaking), and the marketing-site rewrite for the founder audience. Time to tag a release so adopters running /update get the new capabilities.
Scope
- Add
## [2.0.0] — 2026-05-24 entry to CHANGELOG.md (concise, adopter-focused per the brief — capability changes, not internal commit chains)
- Backfill the missing
## [1.3.0] entry as a short summary (the v1.3.0 tag shipped but never landed a CHANGELOG entry — gap to close)
- Update
site/index.html JSON-LD softwareVersion, version pill, release-tag link, hero metric (releases: 7→8, AgDRs: 29→51, PRs: 175→176)
- Update
site/llms.txt, site/llms-full.txt, site/index.md.gen proof numbers
- Open release PR
release/v2.0.0 → main with the <!-- multi-close: approved --> marker (release PR closes 77 issues in one go)
- After CEO
/approve-merge + Rex + merge: git tag v2.0.0 origin/main && git push origin v2.0.0
- Optional:
gh release create v2.0.0 with the CHANGELOG section as the body
Acceptance Criteria
Risks / Dependencies
Glossary
| Term |
Definition |
| Release-cut branch model |
Framework convention (AgDR-0007) — daily PRs to dev, release PRs to main only, tag per release. Adopted in v1.1.0. |
| Multi-close marker |
<!-- multi-close: approved --> HTML comment in PR body that bypasses the single-Closes #N-per-PR hook for legitimate umbrella PRs like release cuts. |
| Breaking change marker |
The ! in feat(#347)!: per Conventional Commits — drives the MAJOR semver bump per /release skill auto-detection. |
| Agent runtime overhaul |
Wave 1-3 PRs from #347/#351 that introduced per-agent model routing (agent-routing.yaml), class-aware role activation (spawn vs in-thread), and the Hatim→Hakim consolidation. |
Driver
The
devbranch has accumulated 123 commits since the v1.3.0 tag (2026-05-18). This includes 6 new slash commands, a per-agent model routing layer, class-aware role activation, a security-reviewer agent rename (breaking), and the marketing-site rewrite for the founder audience. Time to tag a release so adopters running/updateget the new capabilities.Scope
## [2.0.0] — 2026-05-24entry toCHANGELOG.md(concise, adopter-focused per the brief — capability changes, not internal commit chains)## [1.3.0]entry as a short summary (the v1.3.0 tag shipped but never landed a CHANGELOG entry — gap to close)site/index.htmlJSON-LDsoftwareVersion, version pill, release-tag link, hero metric (releases: 7→8, AgDRs: 29→51, PRs: 175→176)site/llms.txt,site/llms-full.txt,site/index.md.genproof numbersrelease/v2.0.0→mainwith the<!-- multi-close: approved -->marker (release PR closes 77 issues in one go)/approve-merge+ Rex + merge:git tag v2.0.0 origin/main && git push origin v2.0.0gh release create v2.0.0with the CHANGELOG section as the bodyAcceptance Criteria
CHANGELOG.mdv2.0.0 section written, structurally consistent with v1.2.0 shapeCHANGELOG.mdv1.3.0 backfill entry added (gap fix)softwareVersion: 2.0.0, 8 releases, 51 AgDRs, 176 PRsmainwith all 77Closes #Nreferences<!-- multi-close: approved -->) present in PR bodyrelease(#<this-ticket>): v2.0.0/approve-mergefor the release PRv2.0.0tag pushed toorigin/mainafter mergeRisks / Dependencies
Hatim → Hakim([Feature] Promote all 19 role definitions to Claude Code sub-agents (per-role model + tool restriction + isolated context) #347 PR feat(#347)!: Hatim→Hakim consolidation + security + data sub-agents (Wave 2 PR 3) #360). Adopters with custom prompts referencingHatimmust update. Call out in CHANGELOG § Breaking and in tag annotation./updatewill walk the v1.3.0 → v2.0.0 migration chain — thefeat(#282)chain-walker shipped in v1.3.0 handles this transparently, but observe behavior on first adopter to sync.Glossary
dev, release PRs tomainonly, tag per release. Adopted in v1.1.0.<!-- multi-close: approved -->HTML comment in PR body that bypasses the single-Closes #N-per-PR hook for legitimate umbrella PRs like release cuts.!infeat(#347)!:per Conventional Commits — drives the MAJOR semver bump per/releaseskill auto-detection.agent-routing.yaml), class-aware role activation (spawn vs in-thread), and the Hatim→Hakim consolidation.