docs(P00): grill PASS (0.82) — 3 binding conditions, 3 phase challenges

---ci---
project: orca
phase: 0
milestone: v0.10
status: grill
---/ci---

.ciagent/CHECKPOINT.json

@@ -1 +1,20 @@
-{ "phase": 99, "stage": "verify", "milestone": "v0.9", "phase_role": "final", "updated_at": "2026-08-05T05:20:00Z", "milestone_complete": false, "verify": { "build": "pass", "go_test": "26/26", "bats": "20/20", "gofmt": "clean", "go_vet": "clean", "verify_reqs": "90 consistent", "p0_fixed": "heredoc command injection" } }
+{
+  "phase": 0,
+  "stage": "plan",
+  "milestone": "v0.10",
+  "milestone_slug": "docs-cli-examples",
+  "phase_role": "pre_execution",
+  "attempts": 0,
+  "updated_at": "2026-08-05T20:00:00Z",
+  "milestone_complete": false,
+  "ship": {
+    "tag": null,
+    "merged_to_main": false,
+    "milestone_branch_deleted": false,
+    "all_phase_branches_deleted": false
+  },
+  "requirements": {
+    "covered": [],
+    "partial": []
+  }
+}

.ciagent/GRILL_v0.10.md

@@ -0,0 +1,58 @@
+# Grill: v0.10 Docs & Install Milestone
+
+## Verdict: PASS (confidence 0.82)
+
+The plan is sound for a documentation + install-hardening milestone.
+No replan required. Three binding conditions adopted below.
+
+## Axis review
+
+### Scope justification — PASS
+The milestone closes a real gap (no CLI/jobspec/ingress docs, stale
+README, broken release pipeline) with a bounded scope (5 phases, no Go
+orchestration code changes). The v0.9 re-architecture shipped
+functionality without operator-facing docs; this milestone ships the
+docs. The install fix (P1) addresses a measured production bug
+(v0.4.5 install), not a speculative enhancement.
+
+### Feasibility — PASS
+All tasks are markdown authoring (P2-P4) or bash script hardening (P1).
+No new dependencies, no schema changes, no Go code changes. The
+jobspecs in P3 must parse against the current parser — risk R1 is
+real but mitigated by validation before commit.
+
+### Vertical slice integrity — PASS
+Each phase ships an independently valuable deliverable:
+- P1: install.sh works (resolves to a release with an asset)
+- P2: an operator can read the CLI/jobspec/ingress docs
+- P3: an operator can copy the examples and deploy a stack
+- P4: README + namespace.md are accurate
+- P5: milestone complete, merged, released
+
+### Wave ordering — PASS
+P1 (Wave 1) unblocks all subsequent ship operations (each phase ship
+needs a correctly-asseted release). P2 + P3 (Wave 2) are parallel with
+no dependencies. P4 (Wave 3) depends on P2/P3 for cross-links. P5
+(Wave 4) depends on all.
+
+### Risk register — PASS
+Three risks identified, all mitigated. R1 (jobspec parse drift) is the
+highest; mitigation is validation before commit. R2 (tea CLI asset bug)
+has a curl fallback. R3 (v0.8.15 still asset-less) is handled by
+install.sh's fallback walk.
+
+## Binding conditions
+
+| ID | Condition | Phase | Status |
+|----|-----------|-------|--------|
+| C-20 | Every jobspec in `examples/full-stack/` MUST parse with `internal/jobspec.ParseFile` and pass `internal/spec/schema.ValidatorFor(kind)` before P3 commits | P3 | pending |
+| C-21 | `scripts/release.sh` post-create asset verification MUST query the Gitea API and assert the tarball in attachments (not rely on `tea` exit code alone) | P1 | pending |
+| C-22 | Every factual claim in `docs/cli.md`, `docs/jobspec.md`, `docs/ingress.md` MUST be grounded in the live codebase (struct fields, flag definitions, paths) — verified by the docs-engineer persona before P2 commits | P2 | pending |
+
+## Phase challenges
+
+| ID | Challenge | Phase |
+|----|-----------|-------|
+| PC-11 | The jobspecs in P3 must not use fields that don't exist yet (e.g., `resources:` which lands in v0.11-P0c). Validate against the current `WorkloadSpec` struct. | P3 |
+| PC-12 | The rendered artifacts in P3 must match what the emitters actually produce, not an idealized version. Cross-check against `internal/emitter/` test fixtures. | P3 |
+| PC-13 | The README subcommand table must match `internal/cli/` exactly — no stale commands, no missing commands. | P4 |

.ciagent/IDEATION_v0.10.md

@@ -0,0 +1,39 @@
+# Ideation: v0.10 Docs & Install Milestone
+
+## Tier 1 — Mechanical (codebase-grounded, no new deps)
+
+| ID | Idea | Source | Accepted | REQ |
+|----|------|--------|----------|-----|
+| I-M-091 | `docs/cli.md` comprehensive CLI reference | README subcommand table is stale (missing cert/daemon/doctor/audit/ns/node-capacity/node-key-reset); no `docs/` CLI reference exists | ✅ | REQ-091 |
+| I-M-092 | `docs/jobspec.md` markdown frontmatter schema reference | Operators must read `internal/jobspec/markdown.go` source to author jobspecs; no reference doc exists | ✅ | REQ-092 |
+| I-M-093 | `docs/ingress.md` Traefik ingress reference | The service→Traefik mapping (R-007, atomic reload, drain, TLS) is undocumented; the user explicitly asked for "ingress configured" | ✅ | REQ-093 |
+| I-M-094 | `examples/full-stack/` with 5 valid jobspecs + rendered artifacts + walkthrough | No examples directory exists; `testdata/` holds legacy HCL test fixtures, not operator examples | ✅ | REQ-094 |
+| I-M-095 | README.md refresh (status, subcommand table, install example, dev targets, docs/examples sections) | README says "v0.1: Foundation"; subcommand table missing 5 commands; install example pins v0.4.2 | ✅ | REQ-095 |
+| I-M-096 | `docs/namespace.md` v0.9 multi-namespace layout update | Documents the v0.8 flat layout, not the v0.9 `cluster/`+`_defaults/`+per-ns layout | ✅ | REQ-096 |
+
+## Tier 2 — Backend-enriched (API/behavior-grounded)
+
+| ID | Idea | Source | Accepted | REQ |
+|----|------|--------|----------|-----|
+| I-B-097 | `scripts/release.sh` cross-build amd64 + post-create asset verification | v0.8.x releases shipped with zero binary assets; install.sh resolves to v0.8.15 then errors on missing tarball; root cause of v0.4.5 install | ✅ | REQ-097 |
+| I-B-098 | `scripts/install.sh` asset fallback walk + `--check` dry-run | install.sh has no fallback when the latest release lacks the expected tarball; a broken release blocks all installs | ✅ | REQ-098 |
+
+## Tier 3 — Cross-project (deferred — single-project mode)
+
+No cross-project ideas. Orca is single-project mode.
+
+## Rejected ideas
+
+- **Backfill the existing v0.8.15 release with a binary asset** —
+  rejected per D-192. Backfilling a past release is an ops task, not a
+  docs milestone deliverable. The next tagged phase (P1 ship at v0.9.1)
+  will be the first correctly-asseted release; install.sh's fallback
+  walk handles the gap.
+- **Document both v0.8 and v0.9 paths equally** — rejected per D-191.
+  The v0.8 path is deprecated and scheduled for removal; documenting it
+  as primary misleads new operators.
+- **arm64 tarball in release.sh** — rejected for this milestone per
+  D-193. The install user base is amd64 today; arm64 is a separate
+  enhancement.
+- **Per-command `docs/cli/*.md` subdirectory** — rejected per D-188.
+  Single-file `docs/cli.md` matches the existing flat `docs/` layout.

.ciagent/PERSONAS.md

@@ -137,91 +137,72 @@ enforcement remains in `warn` mode per config.json.
 
 ---
 
-## v0.7 baseline (preserved for traceability)
+## v0.10 Docs & Install Milestone — Persona Configuration
 
+```yaml
 ---
-active_personas:
+active:
   - lead-developer
   - backend-engineer
+  - docs-engineer
+deactivated:
   - data-engineer
-deactivated_personas:
-  - cli-engineer
   - security-engineer
-  - devops-engineer
   - network-engineer
+  - devops-engineer
+  - cli-engineer
   - frontend-engineer
-phase_specific: []
+phase_specific:
+  - docs-engineer
 reason: |
-  Orca v0.7 is an NFR hardening & completion milestone. The work is CLI
-  registration (cert command), a new internal/config package, test
-  coverage uplift across engine/transport/proxmox/audit, and an opt-in
-  pprof endpoint on the daemon. No schema changes, no new security
-  surface, no packaging/distribution, no UI.
-
-  Roster changes vs v0.6:
-  - data-engineer: RETAINED — owns cert_repo tests + store coverage.
-  - security-engineer: DEACTIVATED — v0.7 adds no new security surface
-    (pprof is operator-only, addr-gated; cert registration exposes
-    existing security code, does not add new).
-  - cli-engineer: DEACTIVATED — merged into lead-developer for v0.7
-    (the cert registration is a 1-line AddCommand; config --config flag
-    is root-command wiring, not a new CLI subsystem).
-  - devops-engineer: DEACTIVATED — no packaging/distribution in v0.7.
+  v0.10 is a documentation + install-hardening milestone. It touches two
+  territories: scripts/ (release.sh, install.sh — bash, backend-engineer)
+  and docs/ + examples/ + README.md (markdown, lead-developer +
+  docs-engineer). No Go orchestration code changes, no schema/migration
+  changes, no UI, no security/crypto surface, no transport/network
+  surface. The data-engineer, security-engineer, network-engineer, and
+  devops-engineer personas are deactivated for this milestone.
 ---
+```
 
-### lead-developer (v0.7)
-- **Domain**: coordination
-- **Frameworks**: `cobra`
-- **Constraints**: `boundary-enforcement`, `offline-first`, `no-redundant-implementations`
-- **Territory**: `**/*.go`, `cmd/**`, `internal/**`
+### lead-developer (v0.10)
 - **Active**: true
-- **Reason**: Coordination across P01/P02/P03. SSH/bootstrap touches security + cli + store + doctor — territory overlaps need adjudication (proxmox package boundary, doctor Proxmox check scaffolding).
+- **Territory**: `docs/**/*.md`, `examples/**`, `README.md`,
+  `.ciagent/**/*.md` (coordination + cross-cutting docs)
+- **Frameworks**: markdown, cobra (for CLI reference accuracy)
+- **Reason**: Owns the CLI reference doc, jobspec reference, ingress
+  guide, examples directory, README refresh, and namespace.md update.
+  Coordinates factual accuracy against the live codebase.
 
-### backend-engineer (v0.7)
-- **Domain**: backend
-- **Frameworks**: `cobra`, `net/http`, `golang.org/x/crypto/ssh`
-- **Constraints**: `API-first`, `error-handling`, `minimal-dependencies`, `security-first`, `idempotent-bootstrap`
-- **Territory**: `**/api/**`, `**/*_handler*`, `**/*_handler.go`, `internal/daemon/**`, `internal/proxmox/**`, `internal/cli/init.go`
+### backend-engineer (v0.10)
 - **Active**: true
-- **Reason**: Owns the `orca init` full-bootstrap orchestration (CA + cert + db + localhost node, idempotent) and the `internal/proxmox/bootstrap.go` SSH session sequence (dial, deploy pubkey, useradd, pveum, sudoers, visudo validate). Added `idempotent-bootstrap` constraint (D-036 — re-run must be skip-and-refresh) and `golang.org/x/crypto/ssh` to frameworks.
+- **Territory**: `scripts/release.sh`, `scripts/install.sh`,
+  `scripts/tests/*.bash`
+- **Frameworks**: bash, curl, tea CLI, Gitea API
+- **Reason**: Owns the release/install pipeline fix (cross-build amd64,
+  asset verification, fallback walk). The scripts are API-adjacent
+  tooling that interacts with the Gitea releases API.
 
-### data-engineer (v0.7)
-- **Domain**: data
-- **Frameworks**: `modernc/sqlite`, `iter`
-- **Constraints**: `schema-first`, `migration-safe`, `local-storage-only`, `no-goroutine-leak`, `nullable-column-handling`
-- **Territory**: `**/store/**`, `**/model.go`, `**/migration*`, `migrations/**`, `internal/store/migrations/**`, `internal/model/node.go`
-- **Active**: true
-- **Reason**: Reactivated for v0.6. Owns migration `0006_node_kind_os.sql` (REQ-049 — nullable `kind`/`os` columns, backward-compatible) and `NodeRepo` schema extension (Insert/Get/List/Watch/scanNode column additions + new `GetByName`/`UpdateLastSeenAndOS` helpers). Added `nullable-column-handling` constraint (NULL → `""` in Go struct, not nil-deref).
+### docs-engineer (v0.10 — phase-specific)
+- **Active**: true (phase-specific: P2, P3, P4)
+- **Territory**: `docs/cli.md`, `docs/jobspec.md`, `docs/ingress.md`,
+  `examples/full-stack/**`
+- **Frameworks**: markdown, GitHub-flavored markdown
+- **Constraints**: factual-accuracy-against-codebase,
+  cross-link-resolution, deprecation-callouts
+- **Reason**: Custom persona for the markdown authoring work. Ensures
+  every factual claim in the docs is grounded in the live codebase
+  (struct fields, flag definitions, paths) and every cross-link
+  resolves. Removed after P4.
 
-### cli-engineer (v0.7)
-- **Domain**: CLI/UX
-- **Frameworks**: `cobra`, `pflag`
-- **Constraints**: `discoverable-help`, `consistent-flag-naming`, `human-readable-output`, `machine-readable-json-flag`, `signal-handling`, `password-flag-redaction`
-- **Territory**: `cmd/**`, `internal/cli/**`, `internal/commands/**`
-- **Active**: true
-- **Reason**: Owns `orca init` multi-step bootstrap output UX (progress lines per step), `orca node join --type/--host/--user/--password/--proxmox-user/--proxmox-role` flag wiring, and `doctor os`/`doctor proxmox` subcommand wiring. Added `password-flag-redaction` constraint (D-031 — `--password` never echoed, prefer `$ORCA_PROXMOX_PASSWORD`, zero after use).
-
-### security-engineer (v0.7)
-- **Domain**: security
-- **Frameworks**: `crypto/tls`, `crypto/x509`, `crypto/ed25519`, `golang.org/x/crypto/ssh`, `slog`
-- **Constraints**: `no-panic-in-production`, `structured-audit-logging`, `no-secret-in-logs`, `input-validation`, `least-privilege`, `tofu-host-key-pinning`, `noexec-sudoers`
-- **Territory**: `**/auth/**`, `**/audit/**`, `internal/security/**`, `internal/transport/**` (TLS config only), `internal/proxmox/**` (SSH + sudoers + PVE role)
-- **Active**: true
-- **Reason**: Reactivated for v0.6. Owns `internal/security/sshkey.go` (Ed25519 keygen, 0600/0644 mode enforcement per REQ-033 spirit), TOFU host-key pinning via `knownhosts.New`, sudoers least-privilege design (NOEXEC on pct/qm, exclude pvesh, no NOEXEC on apt-get/dpkg), password redaction (D-031), and audit logging of all bootstrap/join actions (REQ-052). Added `tofu-host-key-pinning` and `noexec-sudoers` constraints. Co-owns `internal/proxmox/**` with backend-engineer (security owns SSH auth + sudoers content; backend owns the session orchestration).
-
-### devops-engineer (v0.7)
-- **Active**: false (v0.6)
-- **Reason**: Deactivated — v0.6 has no install.sh, Dockerfile, .coreci.yml, or release-pipeline surface. The Proxmox SSH bootstrap is backend + security work, not devops. Was active in v0.5 (distribution milestone).
-
-### network-engineer (v0.7)
-- **Active**: false (v0.6)
-- **Reason**: v0.6 has no transport/mTLS surface. SSH is point-to-point bootstrap, not the mTLS mesh network-engineer owns.
-
-### frontend-engineer (v0.7)
-- **Active**: false (v0.6)
-- **Reason**: No web UI in Orca (unchanged from v0.1 onward).
-
-### v0.6 vs v0.5 Persona Diff (v0.7 baseline reference)
+### Deactivated personas (v0.10)
+- **data-engineer**: no schema/migration work this milestone.
+- **security-engineer**: no crypto/threat-model work this milestone.
+- **network-engineer**: no transport/socket work this milestone.
+- **devops-engineer**: no packaging/distribution work beyond the
+  release.sh fix (owned by backend-engineer).
+- **cli-engineer**: no new CLI commands this milestone.
+- **frontend-engineer**: no web UI (unchanged from v0.1).
 
 | Change | Rationale |
 |--------|-----------|

.ciagent/PLAN_v0.10.md

@@ -0,0 +1,96 @@
+# Plan: v0.10 Docs & Install Milestone
+
+## Milestone: v0.10 — Docs & Install Hardening
+- **Type**: feature (P1 `fix`, P2-P4 `docs`; at least one non-docs phase)
+- **Tags**: `v0.9.0` (P0) → `v0.9.1` (P1) → `v0.9.2` (P2) → `v0.9.3` (P3) → `v0.9.4` (P4) → `v0.9.5` (P5 = milestone release)
+- **Branch**: `milestone/v0.10-docs-cli-examples`
+
+## Phase breakdown
+
+### Phase P1 — release.sh + install.sh fix (Wave 1)
+**REQs**: REQ-097, REQ-098
+**Persona**: backend-engineer
+**Territory**: `scripts/release.sh`, `scripts/install.sh`, `scripts/tests/*.bash`
+**Vertical slice**: a broken release → a correctly-asseted release that install.sh resolves.
+
+| Task | Description | REQ |
+|------|-------------|-----|
+| P1-T1 | `scripts/release.sh`: replace host-arch build (lines 84, 89-98) with explicit `GOOS=linux GOARCH=amd64 go build` cross-build; produce `orca-${VERSION}-linux-amd64.tar.gz` regardless of host arch | REQ-097 |
+| P1-T2 | `scripts/release.sh`: after `tea releases create` (line 132), add post-create asset verification — query `/api/v1/repos/$OWNER/$REPO/releases/tags/$VERSION`, assert the tarball appears in `attachments`, retry once if missing, fail loudly with clear error if still missing | REQ-097 |
+| P1-T3 | `scripts/install.sh`: add asset fallback walk — if the resolved release (latest or `--version`) lacks the matching `orca-<ver>-<os>-<arch>.tar.gz`, query `/releases?limit=20`, walk backward, use the most recent release that carries the asset, print a warning | REQ-098 |
+| P1-T4 | `scripts/install.sh`: add `--check` dry-run mode that prints version + asset URL + install path without writing | REQ-098 |
+| P1-T5 | `scripts/tests/release.bats` + `scripts/tests/install.bats`: add/extend bats tests for the new behavior (happy path: asset present; fallback: latest release asset-less, older release has asset; --check prints without writing) | REQ-097, REQ-098 |
+
+**Must-haves**: release.sh produces an amd64 tarball on any host arch; install.sh resolves to a release with an asset (walking back if needed); `--check` works; bats tests pass.
+
+### Phase P2 — CLI + jobspec + ingress docs (Wave 2)
+**REQs**: REQ-091, REQ-092, REQ-093
+**Persona**: docs-engineer (phase-specific), lead-developer
+**Territory**: `docs/cli.md`, `docs/jobspec.md`, `docs/ingress.md`
+**Vertical slice**: an operator with no orca background → can author a jobspec, run it, and understand the ingress model from docs alone.
+
+| Task | Description | REQ |
+|------|-------------|-----|
+| P2-T1 | `docs/cli.md`: full CLI reference — global flags, every command/subcommand with synopsis + flag tables + one-line example, output modes (text/json/watch), exit codes, deprecated surface callout boxes (daemon/cert/node-join-mTLS/HCL-jobspec) | REQ-091 |
+| P2-T2 | `docs/jobspec.md`: markdown frontmatter schema reference — top-level keys, block reference (runtime/ports/env-secrets/volumes/restart/update/service/health/lifecycle/constraints/affinity/tasks), kinds matrix, CEL subset grammar, body semantics, deprecated HCL callout | REQ-092 |
+| P2-T3 | `docs/ingress.md`: Traefik ingress reference — service→Traefik mapping, R-007 socket-vs-TCP-bind, generated YAML shape, atomic reload (C-10), drain, TLS, worked-example pointer to `examples/full-stack/`, v0.10 forward limitations | REQ-093 |
+
+**Must-haves**: every command/flag in `internal/cli/` is documented; every jobspec field in `internal/jobspec/markdown.go` is documented; every factual claim is grounded in the live codebase; cross-links resolve; deprecated surface is clearly marked.
+
+### Phase P3 — full-stack examples (Wave 2, parallel with P2)
+**REQs**: REQ-094
+**Persona**: docs-engineer (phase-specific), lead-developer
+**Territory**: `examples/full-stack/**`
+**Vertical slice**: an operator → can deploy a multi-service stack with ingress by copying the examples.
+
+| Task | Description | REQ |
+|------|-------------|-----|
+| P3-T1 | `examples/full-stack/web-app.md`: kind Service, process runtime, port http, service block (socket default), health, restart (service), update (rolling), constraints (CEL), task group (app + sidecar) | REQ-094 |
+| P3-T2 | `examples/full-stack/api.md`: kind Service, process runtime, port api, service bind 127.0.0.1 (TCP opt-in), health, restart, update (canary) | REQ-094 |
+| P3-T3 | `examples/full-stack/worker.md`: kind Job, process runtime, one-shot, timeout, env, lifecycle hooks | REQ-094 |
+| P3-T4 | `examples/full-stack/log-shipper.md`: kind DaemonSet, schedule (every-node), restart, constraints | REQ-094 |
+| P3-T5 | `examples/full-stack/postgres.md`: kind Service, process runtime, port pg, volumes + replication (syncthing), health, restart, update (blue-green) | REQ-094 |
+| P3-T6 | `examples/full-stack/rendered/`: the Traefik dynamic YAML + systemd units orca generates for the stack (traefik-dynamic-web-app.yaml, traefik-dynamic-api.yaml, systemd-web-app.service, systemd-api.service, systemd-log-shipper.service) | REQ-094 |
+| P3-T7 | `examples/full-stack/README.md`: walkthrough (init → node join → capacity set → ns create → job run → list --watch → inspect rendered → drain/rollback notes → cross-link to docs/ingress.md) | REQ-094 |
+
+**Must-haves**: all 5 jobspecs parse with the current `internal/jobspec` parser and pass `internal/spec/schema` validators; rendered artifacts match what the emitters would produce; README walkthrough is end-to-end coherent.
+
+### Phase P4 — README + namespace.md refresh (Wave 3, after P2/P3)
+**REQs**: REQ-095, REQ-096
+**Persona**: lead-developer
+**Territory**: `README.md`, `docs/namespace.md`
+**Vertical slice**: a new visitor to the repo → sees accurate status, all commands, install instructions that work, and a link to the docs + examples.
+
+| Task | Description | REQ |
+|------|-------------|-----|
+| P4-T1 | `README.md`: status line (v0.9 complete, v0.10 in progress); install `--version` example updated to current tag; subcommand table expanded to all commands with deprecation markers; update-in-place example updated; development targets complete; new Documentation + Examples sections | REQ-095 |
+| P4-T2 | `docs/namespace.md`: replace v0.8 flat path table with v0.9 multi-namespace layout (`cluster/`, `_defaults/`, per-ns `db/jobs/alloc/ns.md`); `ORCA_HOME`/`--system` resolution; `orca ns` subcommand cross-link; v0.8 flat layout flagged deprecated | REQ-096 |
+
+**Must-haves**: README subcommand table matches `internal/cli/` exactly; install example pins a current tag; namespace.md path table matches `internal/paths/paths.go`; both files cross-link to the new docs.
+
+### Phase P5 — final review + ship + audit (Wave 4)
+**REQs**: all (REQ-091..REQ-098)
+**Persona**: lead-developer
+**Vertical slice**: milestone complete → merged to main, tagged, released.
+
+| Task | Description | REQ |
+|------|-------------|-----|
+| P5-T1 | Code review across all phases (P1-P4); auto-apply P0 fixes, flag P1+ for post-hoc | all |
+| P5-T2 | Audit: reconstruction test (git log matches `.ciagent/`), file discipline, branch hygiene, commit discipline | all |
+| P5-T3 | Milestone ship: merge phase/05 → milestone → main; tag `v0.9.5` (= v0.10.0 milestone release); create release with full milestone summary + Linux binary asset (verified by the P1 fix); delete all milestone branches | all |
+| P5-T4 | Complete milestone: mark REQ-091..098 complete in REQUIREMENTS.md; mark v0.10 docs milestone complete in ROADMAP.md; clear checkpoint | all |
+
+**Must-haves**: milestone merged to main; release carries the Linux binary (the fix from P1 proving itself); all REQs marked complete; checkpoint cleared.
+
+## Wave ordering
+
+- **Wave 1**: P1 (release/install fix) — unblocks the ship of every subsequent phase (each phase ship needs a correctly-asseted release)
+- **Wave 2**: P2 (docs) + P3 (examples) — parallel, no dependencies between them
+- **Wave 3**: P4 (README + namespace.md) — depends on P2/P3 existing (cross-links)
+- **Wave 4**: P5 (final review + ship) — depends on all prior phases
+
+## Risks
+
+- **R1**: The jobspecs in P3 might not parse if a field shape has drifted since the explore report. Mitigation: validate each jobspec against the current parser before committing (write a throwaway test or run `orca job run` with `--dry-run` if available).
+- **R2**: `tea releases create` asset verification in P1 might reveal a tea CLI bug that can't be worked around in bash. Mitigation: fall back to a direct `curl` upload to the Gitea attachments API if `tea` is unreliable.
+- **R3**: The v0.8.15 release still has no asset after P1 ships (P1 only fixes forward). Mitigation: install.sh's fallback walk (P1-T3) handles the gap; users installing between P1 ship and the first correctly-asseted release (P1's own ship tag v0.9.1) will get a clear warning + fallback.

.ciagent/PROJECT.md

@@ -446,3 +446,61 @@ are recorded in `REQUIREMENTS.md`. The reordered phase plan is in
 | D-179 | Jobspec format: HCL canonical (AD-007) or Markdown? | **Markdown with YAML frontmatter canonical (R-013); HCL legacy** | PRD §8 — Markdown + body preservation is the operator-facing format. HCL adapter (REQ-064) preserves `orca job run old-spec.hcl` during migration. | 0.85 |
 | D-185 | Re-architecture justification: incremental additive or full re-architecture? | **Full re-architecture (overridden by user)** | Six-part evidence basis above; the grill's REPLAN mechanics (PC-01..PC-10, C-01..C-19) adopted as gates. The incremental-additive path was evaluated and rejected on grounds 1 + 5 (daemon failing; SSH-push only viable). | 0.88 |
 | D-187 | wasmtime Go binding (bytecodealliance/wasmtime-go) is CGO-based — does adopting it revoke D-002 (modernc/sqlite CGO-free cross-compile story)? | **Use the wasmtime CLI (apt-installed on peer) via SSH exec; do NOT import wasmtime-go.** | The Go binding links libwasmtime via cgo and would revoke D-002's CGO-free cross-compile story. The CLI-via-SSH approach (same pattern as podman/qm/pct) avoids CGO entirely. `internal/runtime/wasm.go` imports only stdlib + sshpush. `CGO_ENABLED=0 go build ./...` succeeds. C-01 grill gate SATISFIED; D-002 NOT revoked. Full evaluation in `internal/runtime/C01_WASMTIME_CGO_EVAL.md`. | 0.90 |
+
+---
+
+# v0.10 Docs & Install Milestone — Scope Summary
+
+v0.10 is a focused milestone that closes the documentation gap left by
+the v0.9 re-architecture and fixes the release/install pipeline bug that
+caused `install.sh` to resolve to v0.4.5 instead of the latest release.
+The v0.9 re-architecture shipped a complete CLI surface (markdown
+jobspec, `orca ns`, `orca node capacity`, CLI-side scheduler, emitters,
+Traefik ingress) but no operator-facing reference documentation. This
+milestone ships that documentation plus a worked full-stack example
+with ingress configured, and hardens the release pipeline so every
+Gitea release carries a Linux binary asset.
+
+## Root cause of the v0.4.5 install
+
+The v0.8.x releases (v0.8.0 through v0.8.15) shipped with **zero binary
+assets attached** to their Gitea releases. `scripts/install.sh` resolves
+"latest" by hitting `/releases/latest` (returns v0.8.15), then looks for
+`orca-v0.8.15-linux-amd64.tar.gz` in that release's assets. Since the
+asset is missing, install.sh errors out — there is no fallback walk to
+older releases that DO carry a binary. The user's v0.4.5 install came
+from an earlier run or a pinned `--version`. The fix is forward: harden
+`scripts/release.sh` to cross-build the amd64 tarball and verify the
+asset attached post-create; harden `scripts/install.sh` to walk
+backward through releases if the latest lacks the asset.
+
+## v0.10 Phases
+
+- **Phase 0 (pre-execution)**: specify → clarify → research → ideate → plan → grill. Tag `v0.9.0`.
+- **Phase P1 — release/install fix** (REQ-097, REQ-098): cross-build amd64 tarball in release.sh, post-create asset verification, install.sh fallback walk. Tag `v0.9.1`.
+- **Phase P2 — CLI + jobspec + ingress docs** (REQ-091, REQ-092, REQ-093): `docs/cli.md`, `docs/jobspec.md`, `docs/ingress.md`. Tag `v0.9.2`.
+- **Phase P3 — full-stack examples** (REQ-094): `examples/full-stack/` with 5 valid jobspecs + rendered artifacts + walkthrough README. Tag `v0.9.3`.
+- **Phase P4 — README + namespace.md refresh** (REQ-095, REQ-096): README subcommand table + install example + docs/examples sections; `docs/namespace.md` v0.9 layout. Tag `v0.9.4`.
+- **Phase P5 — final review + ship + audit** (milestone release). Tag `v0.9.5` = v0.10.0 milestone release.
+
+**Milestone type**: feature (P1 ships `fix` phases; P2/P3/P4 ship `docs`
+phases; at least one non-docs phase makes this a feature milestone per
+the versioning logic). Tags run on the v0.9.x patch line. The milestone
+branch label is `milestone/v0.10-docs-cli-examples`.
+
+The vision ("minimalist, offline-first, CLI-first orchestration
+engine") is unchanged. v0.10 is a documentation + install-hardening
+milestone, not a direction change. It builds on the v0.9
+re-architecture foundation without modifying any Go orchestration code.
+
+## v0.10 Clarified Decisions (D-series, full autonomy — Phase 0 pre-execution)
+
+| ID | Question | Decision | Rationale | Confidence |
+|----|----------|----------|-----------|------------|
+| D-188 | Should the CLI docs be a single `docs/cli.md` reference or a per-command `docs/cli/` subdirectory? | **Single `docs/cli.md` reference** | Mirrors the existing flat `docs/` pattern (install.md, docker.md, namespace.md, security-scanning.md). One file is more discoverable for a CLI tool and avoids navigation overhead. A per-command subdirectory diverges from the established layout. | 0.92 |
+| D-189 | Should the examples live in `examples/full-stack/` or in `testdata/`? | **`examples/full-stack/` as a new top-level directory** | `testdata/` holds legacy HCL fixtures (`hello.hcl`, `fail.hcl`) used by Go tests; mixing operator-facing examples with test fixtures conflates audiences. A new `examples/` directory is the conventional location for worked examples and is what an operator expects to find. | 0.93 |
+| D-190 | How deep should the ingress/Traefik documentation go? | **Dedicated `docs/ingress.md` plus a worked example in `examples/full-stack/`** | Ingress is the user's explicit ask ("full stack with ingress configured") and the Traefik/service-block model (R-007 socket vs TCP, atomic reload, drain, TLS) is non-trivial. A dedicated doc is the clearest answer; a section buried in `docs/cli.md` would be less discoverable. | 0.90 |
+| D-191 | Should the docs frame the v0.9 canonical path or document both v0.8 and v0.9 equally? | **Document the v0.9 canonical path; flag deprecated surface with callout boxes** | The v0.8 daemon/mTLS/HCL path is deprecated and scheduled for removal in v0.10-P14. Documenting it as primary misleads new operators; documenting both equally doubles the surface and risks documenting soon-removed code. Callout boxes with "deprecated in v0.9, removed in v0.10" point operators to the canonical path. | 0.91 |
+| D-192 | Should the existing v0.8.15 release be backfilled with a binary asset, or only fix the pipeline forward? | **Fix forward only; no backfill** | Backfilling a past release is an ops task, not a docs milestone deliverable. The next tagged phase (this milestone's P1 ship at v0.9.1) will be the first correctly-asseted release; install.sh's new fallback walk handles the gap until then. | 0.88 |
+| D-193 | Should `release.sh` build only `linux-amd64` or also `linux-arm64`? | **Cross-build `linux-amd64` explicitly (host-arch-independent); arm64 deferred to a follow-up** | The install.sh user base is amd64 today (the `.coreci.yml` release step hardcodes `--asset orca-${VERSION}-linux-amd64.tar.gz`). Building amd64 regardless of host arch (via `GOOS=linux GOARCH=amd64 go build`) guarantees the asset the install script expects. arm64 support is a separate enhancement. | 0.85 |
+| D-194 | Should `install.sh` add a `--check` dry-run mode? | **Yes, lightweight** | A dry-run mode (`--check`) that prints the version + asset URL + install path without writing is cheap to add and useful for debugging the "which release will I get?" question that the v0.4.5 incident surfaced. | 0.80 |

.ciagent/REQUIREMENTS.md

@@ -182,3 +182,22 @@ and `GRILL_v0.9.md`.
 | REQ-088 | Security-engineer + network-engineer persona reactivation: reactivate security-engineer (step-ca provisioner model, SSH-push blast radius, Traefik edge, .env.secrets crypto) and network-engineer (socket exposure R-007, Syncthing P2P ports, Traefik routing); cross-cutting review not single phase (I-C-004). Implements grill C-05 | High | **v0.9 P00** → v0.10 P16 | Complete |
 | REQ-089 | Documentation rewrite: ARCHITECTURE.md/PROJECT.md/README + AD-010 supersession: v0.9-P00 adds "v0.9 Architecture (Supersedes v0.8)" section + banners + Superseded Decisions table; v0.10-P15 rewrites README quickstart for new curl|sh + orca init + orca ns create flow (I-C-005) | Medium | **v0.9 P00** + v0.10 P15/P16 | Complete |
 | REQ-090 | Dual-write window: v0.9 `orca job run` dispatches on extension (`.md`→SSH-push new path, `.hcl`→old daemon path) via parser dispatcher (REQ-064); daemon not removed until v0.10-P05; SSH-push path writes to separate systemd unit namespace (`orca-v1-<alloc>.service`) while daemon uses `orca-<job>.service` — no unit name overlap = no conflict (I-C-006) | High | **v0.9 P00** | Complete |
+
+## v0.10 Docs & Install Milestone Requirements
+
+The following requirements are scoped to the v0.10 docs/cli-examples
+milestone. They cover the CLI reference documentation, jobspec
+reference, ingress guide, full-stack example jobspecs, README refresh,
+namespace.md v0.9 layout update, and the release/install pipeline fix
+that guarantees every Gitea release carries a Linux binary asset.
+
+| ID | Requirement | Priority | Phase | Status |
+|----|-------------|----------|-------|--------|
+| REQ-091 | `docs/cli.md` comprehensive CLI reference: every command/subcommand with synopsis, flags (name/type/default/description), and one-line example; global flags (`--json`, `--system`, `--config`, `--no-deprecation-warnings`); output modes (text vs `--json`, `--watch` table vs NDJSON); exit codes; deprecated surface (`orca daemon`, `orca cert`, `orca node join` mTLS path, legacy `.hcl` jobspec) flagged with callout boxes pointing to v0.10 removal | High | **v0.10 P2** | Pending |
+| REQ-092 | `docs/jobspec.md` markdown frontmatter schema reference: all top-level keys, block reference (runtime, ports, env/secrets, volumes, restart, update, service, health, lifecycle, constraints, affinity, tasks), kinds matrix (Job/Service/DaemonSet required vs allowed), CEL subset grammar, body byte-exact preservation (R-015), deprecated HCL form callout | High | **v0.10 P2** | Pending |
+| REQ-093 | `docs/ingress.md` Traefik ingress reference: `kind: Service` implies Traefik route (D-175), R-007 socket-vs-TCP-bind semantics, generated Traefik YAML shape (routers/services/healthCheck), atomic reload (C-10), drain (`weight: 0`), TLS (certResolver, trust domain, step-ca), worked-example pointer to `examples/full-stack/`, v0.10 forward limitations (socket activation, transactional update) | High | **v0.10 P2** | Pending |
+| REQ-094 | `examples/full-stack/` directory with 5 valid jobspecs (`web-app.md`, `api.md`, `worker.md`, `log-shipper.md`, `postgres.md`) exercising ports/service/health/restart/update/constraints/affinity/lifecycle/task-groups/volumes/replication/DaemonSet; `rendered/` subdir showing the Traefik dynamic YAML + systemd units orca generates; `README.md` walkthrough (init → node join → capacity set → ns create → job run → list --watch → inspect rendered) | High | **v0.10 P3** | Pending |
+| REQ-095 | README.md refresh: status line (v0.9 complete, v0.10 in progress), install `--version` example updated to current tag, subcommand table expanded to all commands with deprecation markers, update-in-place example updated, development targets complete (`verify-reqs`, `security-scan`, `test-race`, `changelog`), new Documentation + Examples sections linking all `docs/*.md` and `examples/` | High | **v0.10 P4** | Pending |
+| REQ-096 | `docs/namespace.md` v0.9 multi-namespace layout update: replace v0.8 flat path table with v0.9 layout (`cluster/`, `_defaults/`, per-ns `db/jobs/alloc/ns.md`), `ORCA_HOME`/`--system` resolution, `orca ns` subcommand cross-link, v0.8 flat layout flagged deprecated | Medium | **v0.10 P4** | Pending |
+| REQ-097 | `scripts/release.sh` release pipeline fix: cross-build `linux-amd64` tarball regardless of host arch (`GOOS=linux GOARCH=amd64 go build`); post-create asset verification (query `/releases/tags/$VERSION`, assert the tarball in attachments, retry/fail loudly if missing). Guarantees every Gitea release carries the Linux binary asset (root cause of v0.4.5 install) | High | **v0.10 P1** | Pending |
+| REQ-098 | `scripts/install.sh` asset fallback walk: if the latest/pinned release lacks the matching `orca-<ver>-<os>-<arch>.tar.gz`, walk backward through `/releases?limit=20` to the most recent release that has it, with a clear warning. Keeps pulling from releases (not main). Optional `--check` dry-run mode | High | **v0.10 P1** | Pending |

.ciagent/RESEARCH_v0.10.md

@@ -0,0 +1,140 @@
+# Research: v0.10 Docs & Install Milestone
+
+## Documentation landscape in the orca tree
+
+### What exists today
+
+The `docs/` directory contains four files:
+
+- `docs/install.md` — install guide (user-level, system-level, version
+  pinning, in-place update, troubleshooting). Accurate for v0.5-v0.8
+  but does not mention the v0.9 multi-namespace layout, `--config`, or
+  `--no-deprecation-warnings`.
+- `docs/docker.md` — Docker image guide. Still documents `orca daemon`
+  (deprecated in v0.9).
+- `docs/namespace.md` — namespace and paths. Documents the **v0.8 flat
+  layout** (`~/.orca/orca.db`, `ca.crt`, `ca.key`, `server.crt`,
+  `server.key`). Does NOT document the v0.9 multi-namespace layout
+  (`cluster/`, `_defaults/`, per-ns `db/jobs/alloc/ns.md`), `orca ns`
+  subcommands, or the `_defaults` implicit root (D-159/D-185/D-187).
+- `docs/security-scanning.md` — gosec + govulncheck + gitleaks guide.
+  Accurate; no v0.9 drift.
+
+### What's missing (the gap this milestone closes)
+
+1. **No CLI reference doc.** The entire CLI command surface (init, job,
+   node, ns, cert, daemon, doctor, status, audit, version) is
+   undocumented in `docs/`. The README subcommand table is stale (lists
+   only version/init/status/node/job with fake "Phase N" statuses,
+   missing cert/daemon/doctor/audit/ns/node-capacity/node-key-reset).
+2. **No jobspec reference doc.** The markdown frontmatter schema (kinds,
+   blocks, CEL subset, validation rules, body semantics) is
+   undocumented. Operators must read `internal/jobspec/markdown.go` and
+   `internal/spec/schema/schema.go` source.
+3. **No ingress/Traefik doc.** The service→Traefik mapping, R-007
+   socket-vs-TCP-bind, atomic reload, drain, TLS — all undocumented.
+4. **No examples directory.** `testdata/` holds legacy HCL fixtures
+   (`hello.hcl`, `fail.hcl`) for Go tests, not operator-facing
+   examples. No worked full-stack demo exists.
+5. **README is stale.** Status line says "v0.1: Foundation".
+   Subcommand table missing 5 commands. Install `--version` example
+   pins v0.4.2. Update-in-place example references v0.4.1→v0.4.2.
+   Development section omits 4 make targets.
+
+### Prior art for CLI reference docs
+
+- **Nomad**: `nomad job` / `nomad node` / `nomad agent` reference pages,
+  one per subcommand, with flag tables and JSON examples. Orca's
+  single-file `docs/cli.md` is simpler (one file vs a subdirectory) but
+  follows the same flag-table + example convention.
+- **kubectl**: `kubectl reference` + per-command pages. Too heavy for
+  orca; the single-file model fits the minimalist ethos.
+- **Docker CLI**: `docker run` reference with flag tables. Matches the
+  shape orca's `docs/cli.md` will take.
+
+### Prior art for example jobspecs
+
+- **Nomad example jobs**: `nomad-job-spec.example` files in the Nomad
+  repo showing service + job + sysbatch patterns. Orca's
+  `examples/full-stack/` mirrors this with 5 markdown jobspecs covering
+  Service/Job/DaemonSet + task groups + volumes + replication.
+- **Kubernetes examples**: `examples/` directory with yaml
+  deployments/services/ingress. Orca's equivalent is the 5 jobspecs +
+  rendered Traefik/systemd artifacts.
+
+## Release/install pipeline research
+
+### Root cause of the v0.4.5 install
+
+Verified via the Gitea API:
+
+```
+GET /api/v1/repos/coreci/orca/releases/latest
+→ tag_name: "v0.8.15"
+
+GET /api/v1/repos/coreci/orca/releases/tags/v0.8.15
+→ attachments: []   (zero binary assets)
+```
+
+The v0.8.x releases (v0.8.0 through v0.8.15) all shipped with **zero
+binary assets attached**. Only `v0.4.5` carries a tarball
+(`orca-v0.4.5-linux-amd64.tar.gz`).
+
+`scripts/install.sh:70-78` resolves "latest" → v0.8.15, then
+`install.sh:96-104` looks for `orca-v0.8.15-linux-amd64.tar.gz` in
+v0.8.15's assets. Since the asset is missing, install.sh errors out
+(`could not find asset ... in release v0.8.15`). The v0.4.5 install
+came from an earlier run or a pinned `--version`.
+
+### Why v0.8.x releases have no assets
+
+`scripts/release.sh:132-136` calls `tea releases create "$VERSION" ...
+--asset "$TARBALL"`. The script builds the tarball (line 98) and passes
+it to `tea`. Two likely failure modes:
+
+1. **Host arch mismatch**: `release.sh:89-95` builds for the host arch
+   (`uname -m`). If the CI runner or dev machine is arm64, it produces
+   `orca-v0.8.15-linux-arm64.tar.gz`, but `install.sh` looks for
+   `linux-amd64`. The `.coreci.yml:121` release step hardcodes
+   `--asset orca-${VERSION}-linux-amd64.tar.gz`, so the CI runner must
+   be amd64 — but `release.sh` run locally on an arm64 dev machine
+   produces the wrong arch.
+2. **Silent asset drop**: `tea releases create` has been observed to
+   succeed (exit 0) without attaching the asset in some tea versions.
+   The script treats `tea`'s exit code as success without verifying the
+   asset actually appears in the release.
+
+### Fix approach (REQ-097, REQ-098)
+
+**release.sh**:
+- Cross-build `linux-amd64` explicitly via
+  `GOOS=linux GOARCH=amd64 go build`, regardless of host arch.
+- After `tea releases create`, query
+  `/api/v1/repos/$OWNER/$REPO/releases/tags/$VERSION` and assert the
+  tarball appears in `attachments`. If not, retry once, then fail
+  loudly with a clear error.
+
+**install.sh**:
+- Add an asset fallback walk: if the resolved release (latest or
+  pinned) lacks the matching tarball, query
+  `/releases?limit=20`, walk backward, and use the most recent release
+  that carries the `orca-<ver>-<os>-<arch>.tar.gz` asset. Print a
+  clear warning.
+- Add `--check` dry-run mode (D-194) that prints the version + asset URL
+  + install path without writing.
+
+## Persona assessment (PERSONAS.md)
+
+This milestone touches two territories:
+
+1. **`scripts/` (release.sh, install.sh)** — bash scripts, not Go.
+   Backend-engineer territory (API-adjacent tooling). The fix is
+   cross-build + API verification + fallback walk.
+2. **`docs/` + `examples/` + `README.md`** — markdown documentation.
+   Lead-developer territory (coordination + cross-cutting docs).
+
+No data-engineer work (no schema/migration changes). No
+frontend-engineer work (no UI). The data-engineer persona is
+deactivated for this milestone. A docs-engineer custom persona is
+created for P2/P3/P4 (markdown authoring with codebase-grounded
+factual claims).

.ciagent/ROADMAP.md

@@ -249,7 +249,53 @@ HCL-canonical, single-namespace, no-container-runtime, no-SPIFFE). The
 reversals are justified by the six-part evidence basis recorded in the
 PROJECT.md Supersession Table.
 
-## Milestone v0.10: Production Hardening
+## Milestone v0.10: Docs & Install Hardening — **IN PROGRESS**
+
+**Scope**: close the documentation gap left by the v0.9 re-architecture
+and fix the release/install pipeline bug that caused `install.sh` to
+resolve to v0.4.5 instead of the latest release. The v0.9
+re-architecture shipped a complete CLI surface (markdown jobspec,
+`orca ns`, `orca node capacity`, CLI-side scheduler, emitters, Traefik
+ingress) but no operator-facing reference documentation. This milestone
+ships that documentation plus a worked full-stack example with ingress
+configured, and hardens the release pipeline so every Gitea release
+carries a Linux binary asset.
+
+**Milestone type**: feature (P1 ships `fix` phases; P2/P3/P4 ship `docs`
+phases; at least one non-docs phase makes this a feature milestone per
+the versioning logic).
+
+- [ ] Phase 0: Pre-execution (specify → clarify → research → ideate → plan → grill) — tag `v0.9.0`
+- [ ] Phase P1: release.sh + install.sh fix (REQ-097, REQ-098) — tag `v0.9.1`
+- [ ] Phase P2: docs/cli.md + docs/jobspec.md + docs/ingress.md (REQ-091, REQ-092, REQ-093) — tag `v0.9.2`
+- [ ] Phase P3: examples/full-stack/ (REQ-094) — tag `v0.9.3`
+- [ ] Phase P4: README.md + docs/namespace.md refresh (REQ-095, REQ-096) — tag `v0.9.4`
+- [ ] Phase P5: Final review + ship + audit (milestone release) — tag `v0.9.5` = v0.10.0 milestone release
+
+**Milestone tag**: `v0.9.5` (final phase patch = milestone release per
+feature-milestone progressive-patch rule). Per-phase tags: `v0.9.0`…`v0.9.5`.
+Tags run on the previous minor's patch line (v0.9.x) per
+branch-strategy.md. The milestone branch label uses the milestone
+number (`milestone/v0.10-docs-cli-examples`); no separate minor tag.
+
+### Per-phase REQ coverage (v0.10 docs milestone)
+
+- **P1** — release.sh cross-build + asset verification (REQ-097); install.sh fallback walk (REQ-098)
+- **P2** — CLI reference (REQ-091); jobspec reference (REQ-092); ingress guide (REQ-093)
+- **P3** — full-stack examples (REQ-094)
+- **P4** — README refresh (REQ-095); namespace.md v0.9 layout (REQ-096)
+
+### Root cause of the v0.4.5 install (documented in RESEARCH_v0.10.md)
+
+The v0.8.x releases (v0.8.0–v0.8.15) shipped with zero binary assets
+attached to their Gitea releases. `install.sh` resolves "latest" →
+v0.8.15, looks for `orca-v0.8.15-linux-amd64.tar.gz`, finds nothing, and
+errors out. The v0.4.5 install came from an earlier run or a pinned
+`--version`. The fix is forward: release.sh cross-builds amd64 and
+verifies the asset post-create; install.sh walks backward through
+releases if the latest lacks the asset.
+
+## Milestone v0.11: Production Hardening
 
 **Scope**: ship a cluster that operators can run. Builds on the v0.9
 re-architecture foundation with the production-grade subsystems:
@@ -258,36 +304,36 @@ the v0.8→v1.0 migration.
 
 **Milestone type**: feature (multiple `feat` phases).
 
-- [ ] Phase 0: Pre-execution (specify → clarify → research → plan → grill) — tag `v0.9.0`
-- [ ] Phase P00: CLI cache layer (REQ-062 cache floor; R-008) — tag `v0.9.1`
-- [ ] Phase P01: Metrics endpoint (hand-rolled text exposition) — tag `v0.9.2`
-- [ ] Phase P01.5: SPIFFE SVID minting spike (REQ-076; **gate C-08** — if spike fails, fall back to mTLS identity) — tag `v0.9.3`
-- [ ] Phase P02: ACL (SPIFFE + token identities) — tag `v0.9.4`
-- [ ] Phase P03: Secrets subsystem (REQ-080; **gate C-19** threat model) — tag `v0.9.5`
-- [ ] Phase P04: Backup/restore (tar + signed) — tag `v0.9.6`
-- [ ] Phase P05: Drain + daemon drain-and-stop (REQ-061) — tag `v0.9.7`
-- [ ] Phase P06: Alloc history (CLI-side SQLite retention; REQ-071 cache DB) — tag `v0.9.8`
-- [ ] Phase P07: Recovery (`orca restore`) — tag `v0.9.9`
-- [ ] Phase P08: Integration tests — expand hermetic harness (REQ-087) — tag `v0.9.10`
-- [ ] Phase P09: Collector + aggregator (opt-in; **gates C-11, C-12, C-14**) — tag `v0.9.11`
-- [ ] Phase P10: Transactional plane (REQ-075, REQ-079; **gate C-09** orca-pull.sh failure contract) — tag `v0.9.12`
-- [ ] Phase P11: `orca job lint` (REQ-084) — tag `v0.9.13`
-- [ ] Phase P12: `orca job verify` (dry-run txn through lead) — tag `v0.9.14`
-- [ ] Phase P13: `orca ns` subcommands (full surface) + deprecation warnings (REQ-068) — tag `v0.9.15`
-- [ ] Phase P14a: v0.8→v1.0 data migration (REQ-066; **gate C-07** CA migration spec) — tag `v0.9.16`
-- [ ] Phase P14b: Daemon cutover + running-allocation adoption — tag `v0.9.17`
-- [ ] Phase P14c: Mixed-version tolerance + no-orca-on-server enforcement (REQ-065, REQ-086; implements C-13) — tag `v0.9.18`
-- [ ] Phase P15: README quickstart (REQ-089) — tag `v0.9.19`
-- [ ] Phase P15.5: Threat model + security review (**gate C-19**) — tag `v0.9.20`
-- [ ] Phase P16: Final review + ship + audit — **v0.10.0 milestone release** — tag `v0.9.21` (v1.0.0 cut separately after UAT sign-off)
+- [ ] Phase 0: Pre-execution (specify → clarify → research → plan → grill) — tag `v0.10.0`
+- [ ] Phase P00: CLI cache layer (REQ-062 cache floor; R-008) — tag `v0.10.1`
+- [ ] Phase P01: Metrics endpoint (hand-rolled text exposition) — tag `v0.10.2`
+- [ ] Phase P01.5: SPIFFE SVID minting spike (REQ-076; **gate C-08** — if spike fails, fall back to mTLS identity) — tag `v0.10.3`
+- [ ] Phase P02: ACL (SPIFFE + token identities) — tag `v0.10.4`
+- [ ] Phase P03: Secrets subsystem (REQ-080; **gate C-19** threat model) — tag `v0.10.5`
+- [ ] Phase P04: Backup/restore (tar + signed) — tag `v0.10.6`
+- [ ] Phase P05: Drain + daemon drain-and-stop (REQ-061) — tag `v0.10.7`
+- [ ] Phase P06: Alloc history (CLI-side SQLite retention; REQ-071 cache DB) — tag `v0.10.8`
+- [ ] Phase P07: Recovery (`orca restore`) — tag `v0.10.9`
+- [ ] Phase P08: Integration tests — expand hermetic harness (REQ-087) — tag `v0.10.10`
+- [ ] Phase P09: Collector + aggregator (opt-in; **gates C-11, C-12, C-14**) — tag `v0.10.11`
+- [ ] Phase P10: Transactional plane (REQ-075, REQ-079; **gate C-09** orca-pull.sh failure contract) — tag `v0.10.12`
+- [ ] Phase P11: `orca job lint` (REQ-084) — tag `v0.10.13`
+- [ ] Phase P12: `orca job verify` (dry-run txn through lead) — tag `v0.10.14`
+- [ ] Phase P13: `orca ns` subcommands (full surface) + deprecation warnings (REQ-068) — tag `v0.10.15`
+- [ ] Phase P14a: v0.8→v1.0 data migration (REQ-066; **gate C-07** CA migration spec) — tag `v0.10.16`
+- [ ] Phase P14b: Daemon cutover + running-allocation adoption — tag `v0.10.17`
+- [ ] Phase P14c: Mixed-version tolerance + no-orca-on-server enforcement (REQ-065, REQ-086; implements C-13) — tag `v0.10.18`
+- [ ] Phase P15: README quickstart (REQ-089) — tag `v0.10.19`
+- [ ] Phase P15.5: Threat model + security review (**gate C-19**) — tag `v0.10.20`
+- [ ] Phase P16: Final review + ship + audit — **v0.11.0 milestone release** — tag `v0.10.21` (v1.0.0 cut separately after UAT sign-off)
 
-**Milestone tag**: `v0.10.0` (the v0.10 milestone release tag; v1.0.0 is
-UAT-gated and cut separately after v0.10 completion per operator decision —
+**Milestone tag**: `v0.11.0` (the v0.11 milestone release tag; v1.0.0 is
+UAT-gated and cut separately after v0.11 completion per operator decision —
 the v1.0.0 tag marks production-ready sign-off, not a separate milestone).
-Per-phase patches run on the v0.9.x line per branch-strategy.md. Per-phase
-tags: `v0.9.0`…`v0.9.21`.
+Per-phase patches run on the v0.10.x line per branch-strategy.md. Per-phase
+tags: `v0.10.0`…`v0.10.21`.
 
-### Per-phase REQ coverage (v0.10)
+### Per-phase REQ coverage (v0.11)
 
 - **P00** — CLI cache (R-008)
 - **P01.5** — SPIFFE spike (REQ-076; C-08)
@@ -309,9 +355,9 @@ tags: `v0.9.0`…`v0.9.21`.
 - **wasmtime CGO breaks cross-compile** (mitigation: C-01 spike; fallback to podman/process primary)
 - **bash control plane drift** (mitigation: C-15..C-18 render-format contract + bats gate)
 - **daemon cutover orphans running allocs** (mitigation: P14b split; test adoption)
-- **27→35+ phase scope** (mitigation: C-04 resolved — operator decision: keep 2 milestones v0.9 + v0.10, keep all phases, v1.0 is UAT-gated after v0.10; current count v0.9=18 + v0.10=22 = 40 phases, exceeds 35 soft limit but operator accepted)
+- **27→35+ phase scope** (mitigation: C-04 resolved — operator decision: keep 2 milestones v0.9 + v0.11, keep all phases, v1.0 is UAT-gated after v0.11; current count v0.9=18 + v0.11=22 = 40 phases, exceeds 35 soft limit but operator accepted)
 
-## Deferred to v1.x (out of scope for v0.10)
+## Deferred to v1.x (out of scope for v0.11)
 
 - `sqlite-wal-shared` state backend (R-009 abstractions ship in v1.0; backend in v1.x)
 - `git` state backend

.ciagent/config.json

@@ -5,7 +5,7 @@
       "slug": "orca",
       "name": "Orca",
       "description": "Offline/CLI-first orchestration engine (Orca) — Nomad-inspired, far simpler than Kubernetes",
-      "milestone": "v0.9",
+      "milestone": "v0.10",
       "phase": 0,
       "milestone_type": "feature",
       "default_branch": "main",