docs(P07): release flow hardening — consistent milestone type taxonomy

---ci---
phase: 7
milestone: v0.10
status: complete
decisions:
  - id: D-092
    decision: Rename schema-breaking → major across all framework files
    rationale: Major aligns with semver terminology and is more descriptive of the version bump impact
    confidence: 0.95
  - id: D-093
    decision: Add Major milestone type to dev context and branch-strategy merge validation gates
    rationale: Release flow was documented but not enforced. Zero-HITL, PR+QA, and branch hierarchy are now hard gates
    confidence: 0.92
---/ci---

opencode/ci/contexts/dev.md

@@ -4,7 +4,7 @@ Agent output guidance for CIAgent dev mode. Loaded when the orchestrator operate
 
 ---
 
-## Multi-Project and NFR Versioning
+## Multi-Project and Milestone Versioning
 
 When in multi-project mode (`.ciagent/config.json` has `projects[]` with length > 0):
 - All commits include `project: <slug>` in `---ci---` block
@@ -12,9 +12,10 @@ When in multi-project mode (`.ciagent/config.json` has `projects[]` with length
 - `.ciagent/` files are in `.ciagent/<slug>/` subdirectories
 - Project scoping applies to all operations
 
-NFR milestone versioning:
-- NFR milestones (all phases are fix/chore/docs/perf/refactor/test): progressive patch versions only, no minor tag
-- Feature milestones (any feat phase): progressive patch versions + minor milestone tag
+Milestone versioning (determined by `getMilestoneType()` before any development):
+- **NFR** (all phases: fix/chore/docs/perf/refactor/test): progressive patch versions, no milestone tag — final patch IS the deliverable
+- **Feature** (at least one `feat` phase): progressive patch versions + next minor milestone tag
+- **Major** (breaking schema changes or complete refactor): progressive minor versions per phase + major milestone tag
 
 ## Output Style
 

opencode/ci/references/branch-strategy.md

@@ -104,7 +104,7 @@ Phase branches can be deleted after merge if desired.
 
 ## Versioning and Releases
 
-**Every merge to main creates a release. No exceptions.** Versioning follows a 3-tier model based on milestone type:
+**Every merge to main creates a release. No exceptions.** Versioning follows the milestone type model:
 
 ### Milestone Type and Versioning