create-project-arch 1.2.0 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,43 @@
1
+ # Milestone Gap-Closure Report - Example
2
+
3
+ ## Executive Summary
4
+
5
+ Milestone scope is complete, critical architecture artifacts are synchronized, and remaining low-risk gaps are tracked for the next milestone.
6
+
7
+ ## Gap Categories And Resolutions
8
+
9
+ - Traceability drift
10
+ - Finding: concept-map dependencies were incomplete for one feature cluster.
11
+ - Resolution: updated `arch-model/concept-map.json` and linked missing surfaces.
12
+ - Status: closed
13
+ - Documentation clarity
14
+ - Finding: architecture scope language was ambiguous for one boundary.
15
+ - Resolution: clarified in architecture spec and referenced decision note.
16
+ - Status: closed
17
+
18
+ ## Layer Synchronization Check
19
+
20
+ - [x] Architecture docs updated
21
+ - [x] Roadmap tasks/decisions synchronized
22
+ - [x] Graph/parity checks pass (`pa check`)
23
+ - [x] Report diagnostics reviewed (`pa report`)
24
+
25
+ ## Coverage Audit
26
+
27
+ - Spec section: service boundary constraints
28
+ - Coverage status: covered
29
+ - Notes: validated against acceptance checks and policy explain output.
30
+ - Spec section: advanced optimization strategy
31
+ - Coverage status: deferred
32
+ - Notes: deferred to next milestone to protect launch scope.
33
+
34
+ ## Remaining Gaps And Follow-On Items
35
+
36
+ - Remaining gap: deferred optimization strategy details
37
+ - Follow-on task/decision: roadmap task `phase-2/milestone-2-performance/003`
38
+
39
+ ## Template Improvement Feedback
40
+
41
+ - Improvement idea: add explicit section for policy conflict outcomes
42
+ - Rationale: closure reviews repeatedly reference policy findings
43
+ - Proposed change: add "Policy Findings" subsection to template
@@ -0,0 +1,4 @@
1
+ #!/usr/bin/env sh
2
+ set -eu
3
+
4
+ sh scripts/validate.sh
@@ -0,0 +1,20 @@
1
+ # Validation Hook Scaffold
2
+
3
+ This scaffold adds baseline architecture validation automation.
4
+
5
+ ## Included Files
6
+
7
+ - `scripts/validate.sh` - local validation entrypoint
8
+ - `.githooks/pre-commit` - optional local pre-commit hook example
9
+
10
+ ## Default Workflow
11
+
12
+ 1. Run `sh scripts/validate.sh` locally.
13
+ 2. The script executes:
14
+ - `pnpm arch:check`
15
+ - `pnpm arch:report`
16
+ 3. Optionally run the same script from `.githooks/pre-commit` for local enforcement.
17
+
18
+ ## Task Verification Guidance
19
+
20
+ When writing or reviewing roadmap tasks, include architecture validation in acceptance checks and verification steps.
@@ -0,0 +1,9 @@
1
+ #!/usr/bin/env sh
2
+ set -eu
3
+
4
+ echo "Running architecture validation..."
5
+
6
+ pnpm arch:check
7
+ pnpm arch:report > architecture-report.txt
8
+
9
+ echo "Architecture validation complete."