docs(P00): correct v0.7 tag line to v0.6.x per branch-strategy.md

Tags run on the previous minor's patch line. v0.7 milestone → v0.6.x
tags (v0.6.0 P0 … v0.6.5 P05 milestone release). Prior commits
incorrectly referenced v0.5.x (the v0.6 milestone's line).

---ci---
project: orca
phase: 0
milestone: v0.7
status: plan
---/ci---

.ciagent/PLAN_v0.7.md

@@ -11,7 +11,7 @@ Branching: `phase/01-cert-register`..`phase/05-final-review-ship` on the
 milestone per branch-strategy.md).
 
 Milestone type: **NFR** (all phases are fix/test/chore; no `feat` phases).
-Tags run on the v0.5.x patch line: `v0.5.5` (P0) … `v0.5.10` (P05 =
+Tags run on the v0.6.x patch line: `v0.6.0` (P0) … `v0.6.5` (P05 =
 milestone release).
 
 ---
@@ -231,7 +231,7 @@ milestone release).
 - [ ] Fix any P0 issues found by review; record P1+ in `.ciagent/` for post-hoc
 - [ ] Merge `phase/05` → `milestone/v0.7-hardening-completion`
 - [ ] Merge `milestone/v0.7` → `main` (rebase-then-fast-forward per config)
-- [ ] Tag `v0.5.10` (final phase patch = milestone release)
+- [ ] Tag `v0.6.5` (final phase patch = milestone release)
 - [ ] Create Gitea release with full milestone summary (all phases, all REQs)
 - [ ] Update `.ciagent/REQUIREMENTS.md` — mark REQ-053..056 complete
 - [ ] Update `.ciagent/ROADMAP.md` — mark v0.7 complete
@@ -245,6 +245,6 @@ milestone release).
 - `make lint` PASS
 - `go vet ./...` PASS
 - `git log` on main shows all v0.7 phase commits
-- `git tag --list 'v0.5.*'` shows v0.5.5..v0.5.10
+- `git tag --list 'v0.6.*'` shows v0.6.0..v0.6.5
 - REQUIREMENTS.md shows REQ-053..056 as Complete
 - ROADMAP.md shows v0.7 as COMPLETE

.ciagent/PROJECT.md

@@ -329,5 +329,5 @@ The vision ("minimalist, offline-first, CLI-first orchestration
 engine") is unchanged. v0.7 is a hardening milestone, not a direction
 change. Milestone type: NFR (all phases are fix/test/chore); the final
 phase's progressive patch IS the deliverable per `run.md` versioning
-logic. Tags run on the v0.5.x patch line: `v0.5.5` (P0) … `v0.5.9` (P05
+logic. Tags run on the v0.6.x patch line: `v0.6.0` (P0) … `v0.6.5` (P05
 = milestone release).

.ciagent/ROADMAP.md

@@ -119,16 +119,16 @@ Scope: NFR milestone closing gaps surfaced by the v0.7 IDEATE stage —
 an unreachable command tree, a missing config file layer, low test
 coverage in core packages, and the long-deferred pprof endpoint.
 
-- [ ] Phase 0: Pre-execution (specify → clarify → research → ideate → plan) — tag `v0.5.5`
-- [ ] Phase 1: Register `orca cert` command tree + cert_repo tests (REQ-053) — tag `v0.5.6`
-- [ ] Phase 2: HCL config file parsing — `internal/config` package (REQ-054) — tag `v0.5.7`
-- [ ] Phase 3: Test coverage uplift — engine/transport/proxmox/audit ≥ 50% (REQ-055) — tag `v0.5.8`
-- [ ] Phase 4: `--pprof` opt-in on `orca daemon` (REQ-056) — tag `v0.5.9`
-- [ ] Phase 5: Final review + ship + audit (milestone release) — tag `v0.5.10`
+- [ ] Phase 0: Pre-execution (specify → clarify → research → ideate → plan) — tag `v0.6.0`
+- [ ] Phase 1: Register `orca cert` command tree + cert_repo tests (REQ-053) — tag `v0.6.1`
+- [ ] Phase 2: HCL config file parsing — `internal/config` package (REQ-054) — tag `v0.6.2`
+- [ ] Phase 3: Test coverage uplift — engine/transport/proxmox/audit ≥ 50% (REQ-055) — tag `v0.6.3`
+- [ ] Phase 4: `--pprof` opt-in on `orca daemon` (REQ-056) — tag `v0.6.4`
+- [ ] Phase 5: Final review + ship + audit (milestone release) — tag `v0.6.5`
 
 **Milestone type**: NFR (all phases are fix/test/chore; no `feat` phases).
-**Milestone tag**: `v0.5.10` (final phase patch = milestone release per
-NFR-milestone progressive-patch rule). Per-phase tags: `v0.5.5`…`v0.5.10`.
-Tags run on the previous minor's patch line (v0.5.x) per
+**Milestone tag**: `v0.6.5` (final phase patch = milestone release per
+NFR-milestone progressive-patch rule). Per-phase tags: `v0.6.0`…`v0.6.5`.
+Tags run on the previous minor's patch line (v0.6.x) per
 branch-strategy.md. The milestone branch label uses the milestone
 number (`milestone/v0.7-hardening-completion`); no separate minor tag.