create-project-arch 1.2.0 → 1.3.1

package/templates/gap-closure/README.md

@@ -0,0 +1,19 @@
+# Milestone Gap-Closure Reports
+
+<!-- Guidance: Use these reports to complete milestone governance and quality review. -->
+
+## When To Use
+
+Create/update a closure report when a milestone reaches completion readiness.
+
+## Workflow
+
+1. Copy `GAP_CLOSURE_TEMPLATE.md` into the milestone or reference location.
+2. Fill each section with concrete findings and evidence.
+3. Run validation commands (`pa check`, `pa report`) and record outcomes.
+4. Track unresolved items as follow-on tasks/decisions.
+
+## Suggested Locations
+
+- `architecture/reference/` for reusable report artifacts and examples
+- `roadmap/phases/<phase>/milestones/<milestone>/closure.md` for milestone-specific closure records

package/templates/gap-closure/example-gap-closure.md

@@ -0,0 +1,43 @@
+# Milestone Gap-Closure Report - Example
+
+## Executive Summary
+
+Milestone scope is complete, critical architecture artifacts are synchronized, and remaining low-risk gaps are tracked for the next milestone.
+
+## Gap Categories And Resolutions
+
+- Traceability drift
+  - Finding: concept-map dependencies were incomplete for one feature cluster.
+  - Resolution: updated `arch-model/concept-map.json` and linked missing surfaces.
+  - Status: closed
+- Documentation clarity
+  - Finding: architecture scope language was ambiguous for one boundary.
+  - Resolution: clarified in architecture spec and referenced decision note.
+  - Status: closed
+
+## Layer Synchronization Check
+
+- [x] Architecture docs updated
+- [x] Roadmap tasks/decisions synchronized
+- [x] Graph/parity checks pass (`pa check`)
+- [x] Report diagnostics reviewed (`pa report`)
+
+## Coverage Audit
+
+- Spec section: service boundary constraints
+  - Coverage status: covered
+  - Notes: validated against acceptance checks and policy explain output.
+- Spec section: advanced optimization strategy
+  - Coverage status: deferred
+  - Notes: deferred to next milestone to protect launch scope.
+
+## Remaining Gaps And Follow-On Items
+
+- Remaining gap: deferred optimization strategy details
+  - Follow-on task/decision: roadmap task `phase-2/milestone-2-performance/003`
+
+## Template Improvement Feedback
+
+- Improvement idea: add explicit section for policy conflict outcomes
+  - Rationale: closure reviews repeatedly reference policy findings
+  - Proposed change: add "Policy Findings" subsection to template

package/templates/validation-hooks/.githooks/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+set -eu
+
+sh scripts/validate.sh

package/templates/validation-hooks/README.md

@@ -0,0 +1,20 @@
+# Validation Hook Scaffold
+
+This scaffold adds baseline architecture validation automation.
+
+## Included Files
+
+- `scripts/validate.sh` - local validation entrypoint
+- `.githooks/pre-commit` - optional local pre-commit hook example
+
+## Default Workflow
+
+1. Run `sh scripts/validate.sh` locally.
+2. The script executes:
+   - `pnpm arch:check`
+   - `pnpm arch:report`
+3. Optionally run the same script from `.githooks/pre-commit` for local enforcement.
+
+## Task Verification Guidance
+
+When writing or reviewing roadmap tasks, include architecture validation in acceptance checks and verification steps.

package/templates/validation-hooks/scripts/validate.sh

@@ -0,0 +1,9 @@
+#!/usr/bin/env sh
+set -eu
+
+echo "Running architecture validation..."
+
+pnpm arch:check
+pnpm arch:report > architecture-report.txt
+
+echo "Architecture validation complete."