Merge branch 'docs/create-story-files' into 'main'

docs(standards): create story files for backlog stories 4.5 and 2.10

See merge request orgdocs/development-standards!26

Author: Matthew

_bmad-output/implementation-artifacts/2-10-cut-dev-toolchain-release.md

@@ -0,0 +1,71 @@
+# Story 2.10: Cut Dev-Toolchain Release for Post-v1.5.0 Features
+
+Status: ready-for-dev
+
+## Story
+
+As a maintainer,
+I want to cut a proper minor release for all features merged since v1.5.0,
+so that the published container image includes Rust, Terragrunt, fix target, pre-push hooks, tool version manifest, and the release script.
+
+## Acceptance Criteria
+
+1. CHANGELOG.md is updated with all [Unreleased] entries under [1.6.0]
+2. The tag v1.6.0 is created and pushed
+3. GitHub Actions builds and publishes the container image to GHCR
+4. The v1 floating tag is updated to point to v1.6.0
+5. The GitHub Release is created with release notes
+6. The tool version manifest is attached to the release
+
+## Tasks / Subtasks
+
+- [ ] Task 1: Verify CHANGELOG.md is complete (AC: 1)
+  - [ ] 1.1 Review [Unreleased] section — ensure all post-v1.5.0 features are documented
+  - [ ] 1.2 Features to verify are listed: Rust ecosystem, Terragrunt support, `make fix` target, pre-push hooks, tool version manifest (`report-tool-versions.sh`), `make release` script, critical rule 8 docs
+  - [ ] 1.3 Add any missing entries before release
+
+- [ ] Task 2: Run `make check` (AC: 1)
+  - [ ] 2.1 Verify all checks pass on current main
+
+- [ ] Task 3: Cut the release (AC: 2, 3, 4, 5, 6)
+  - [ ] 3.1 Run `make release VERSION=1.6.0`
+  - [ ] 3.2 Confirm push when prompted
+  - [ ] 3.3 Verify GitHub Actions build completes successfully
+  - [ ] 3.4 Verify container image is published to GHCR with v1.6.0 tag
+  - [ ] 3.5 Verify v1 floating tag is updated
+  - [ ] 3.6 Verify GitHub Release is created with tool version manifest
+
+## Dev Notes
+
+- `make release VERSION=1.6.0` runs `scripts/release.sh` which handles: semver validation, precondition checks, CHANGELOG update via sed, commit, tag, interactive push confirmation
+- The release script was added in the previous session (PR #8, merged)
+- Current latest tag is v1.5.0 — all Rust, terragrunt, and other features are merged to main but unreleased
+- The weekly cron build bumps patch versions automatically, but feature releases need a deliberate minor bump
+- The CHANGELOG [Unreleased] section in the actual repo may be incomplete — need to cross-reference git log since v1.5.0
+- After release, the `build.yml` workflow handles: multi-arch build, GHCR publish, cosign signing, floating tag update, release notes, tool version manifest attachment
+
+### Project Structure Notes
+
+- `scripts/release.sh` — the release ceremony script
+- `Makefile` — `make release VERSION=x.y.z` target
+- `CHANGELOG.md` — must have [Unreleased] section with content
+- `.github/workflows/build.yml` — triggered by tag push, handles publishing
+
+### References
+
+- [Source: dev-toolchain/scripts/release.sh] — release script
+- [Source: dev-toolchain/Makefile] — release target definition
+- [Source: dev-toolchain/DEVELOPMENT.md#Releasing] — release process documentation
+- [Source: dev-toolchain/.github/workflows/build.yml] — automated build/publish pipeline
+- [Source: epics.md#Story 2.10] — acceptance criteria
+- **Depends on:** Story 4.5 (so the pre-commit hook accepts the `release` scope for the release commit)
+
+## Dev Agent Record
+
+### Agent Model Used
+
+### Debug Log References
+
+### Completion Notes List
+
+### File List

_bmad-output/implementation-artifacts/4-5-update-conventional-commit-scopes.md

@@ -0,0 +1,77 @@
+# Story 4.5: Update Conventional Commit Scopes for All Languages
+
+Status: ready-for-dev
+
+## Story
+
+As a developer,
+I want the pre-commit conventional commits hook to accept all current language scopes,
+so that commits for Ruby, Go, JavaScript, Rust, and new workflow scopes are not rejected.
+
+## Acceptance Criteria
+
+1. The hook accepts all language scopes: python, bash, terraform, ansible, ruby, go, javascript, rust
+2. The hook accepts all workflow scopes: container, ci, makefile, standards, security, changelog, release
+3. The updated hook version is referenced in both template repos' `.pre-commit-config.yaml`
+4. The dev-toolchain repo's `.pre-commit-config.yaml` references the updated hook
+5. `make check` passes on all updated repos
+
+## Tasks / Subtasks
+
+- [ ] Task 1: Update pre-commit-conventional-commits repo (AC: 1, 2)
+  - [ ] 1.1 Update `VALID_SCOPES` in `conventional_commits/config.py` — add: ruby, go, javascript, rust, security, changelog, release
+  - [ ] 1.2 Update test suite in `tests/test_check.py` — add parametrized cases for new scopes
+  - [ ] 1.3 Update `tests/test_config.py` — verify VALID_SCOPES count matches expected
+  - [ ] 1.4 Update README.md — add new scopes to the valid scopes list
+  - [ ] 1.5 Sync DEVELOPMENT.md — add rust, security, changelog, release (ruby/go/javascript already there)
+  - [ ] 1.6 Run `make check` and all tests pass
+  - [ ] 1.7 Tag new version (v1.1.0 — minor bump for new scopes)
+
+- [ ] Task 2: Update dev-toolchain `.pre-commit-config.yaml` (AC: 4)
+  - [ ] 2.1 Bump `rev:` from `v1.0.0` to `v1.1.0` for the conventional-commits hook
+  - [ ] 2.2 Run `make check` passes
+
+- [ ] Task 3: Update github-repo-template `.pre-commit-config.yaml` (AC: 3)
+  - [ ] 3.1 Bump `rev:` from `v1.0.0` to `v1.1.0` for the conventional-commits hook
+  - [ ] 3.2 Run `make check` passes
+
+- [ ] Task 4: Update gitlab-repo-template `.pre-commit-config.yaml` (AC: 3)
+  - [ ] 4.1 Bump `rev:` from `v1.0.0` to `v1.1.0` for the conventional-commits hook
+  - [ ] 4.2 Run `make check` passes
+
+## Dev Notes
+
+- The scope validation is hardcoded in Python: `conventional_commits/config.py` uses a `frozenset` called `VALID_SCOPES`
+- The check module (`check.py`) uses regex `r"^(?P<type>[a-z]+)\((?P<scope>[a-z]+)\): (?P<description>.+)$"` and validates scope membership
+- Current `VALID_SCOPES` in config.py: python, terraform, bash, ansible, container, ci, makefile, standards (8 scopes)
+- DEVELOPMENT.md already documents ruby, go, javascript but config.py doesn't implement them — this is a known doc/code mismatch
+- All three downstream repos (dev-toolchain, github-template, gitlab-template) pin `rev: v1.0.0` with no hook_args overrides
+- No hook_args mechanism exists for per-repo scope customization — scopes are centralized in the hook package
+
+### Project Structure Notes
+
+- `pre-commit-conventional-commits/` — source of truth for scope validation
+  - `conventional_commits/config.py` — VALID_SCOPES frozenset
+  - `conventional_commits/check.py` — regex + validation logic
+  - `tests/test_check.py` — parametrized acceptance tests
+  - `tests/test_config.py` — config validation tests
+- Downstream consumers all use identical hook config block (no per-repo overrides)
+
+### References
+
+- [Source: pre-commit-conventional-commits/conventional_commits/config.py] — VALID_SCOPES definition
+- [Source: pre-commit-conventional-commits/conventional_commits/check.py] — validation logic
+- [Source: dev-toolchain/.pre-commit-config.yaml] — rev: v1.0.0
+- [Source: github-repo-template/.pre-commit-config.yaml] — rev: v1.0.0
+- [Source: gitlab-repo-template/.pre-commit-config.yaml] — rev: v1.0.0
+- [Source: epics.md#Story 4.5] — acceptance criteria
+
+## Dev Agent Record
+
+### Agent Model Used
+
+### Debug Log References
+
+### Completion Notes List
+
+### File List

_bmad-output/implementation-artifacts/sprint-status.yaml

@@ -48,7 +48,7 @@ development_status:
   1-5-write-makefile-contract-and-readme: done
   epic-1-retrospective: optional
 
-  epic-2: done
+  epic-2: in-progress
   2-1-initialize-repository-with-multi-stage-dockerfile-and-shared-libraries: done
   2-2-python-tooling-install-script: done
   2-3-bash-tooling-install-script: done
@@ -58,6 +58,7 @@ development_status:
   2-7-multi-arch-build-and-ghcr-publishing: done
   2-8-automated-weekly-builds: done
   2-9-container-self-validation: done
+  2-10-cut-dev-toolchain-release: ready-for-dev
   epic-2-retrospective: optional
 
   epic-3: done
@@ -68,11 +69,12 @@ development_status:
   3-5-implement-make-check-orchestration: done
   epic-3-retrospective: optional
 
-  epic-4: done
+  epic-4: in-progress
   4-1-verify-and-update-conventional-commits-hook: done
   4-2-configure-language-appropriate-linting-and-formatting-hooks: done
   4-3-add-gitleaks-and-terraform-docs-hooks: done
   4-4-create-make-install-hooks-target: done
+  4-5-update-conventional-commit-scopes: ready-for-dev
   epic-4-retrospective: optional
 
   epic-5: done

_bmad-output/planning-artifacts/epics.md

@@ -941,7 +941,7 @@ So that commits for Ruby, Go, JavaScript, Rust, and new workflow scopes are not
 
 **Repos:** pre-commit-conventional-commits, dev-toolchain, github-repo-template, gitlab-repo-template
 
-### Story 2.6: Cut Dev-Toolchain Release for Post-v1.5.0 Features
+### Story 2.10: Cut Dev-Toolchain Release for Post-v1.5.0 Features
 
 As a maintainer,
 I want to cut a proper minor release for all features merged since v1.5.0,
@@ -960,3 +960,4 @@ So that the published container image includes Rust, Terragrunt, fix target, pre
 
 **Repos:** dev-toolchain
 **Depends on:** Story 4.5 (so the release commit uses the correct scope)
+**Story ID:** 2.10 (numbering continues after original Epic 2 stories 2.1–2.9)