docs(phase6c): pilot readiness standard, pilot curriculum manifest, ROOT 11 scope

Adds the four required Phase 6C documents:

- ROOT_PILOT_READINESS_STANDARD.md — the explicit 8-point sufficiency bar
  used to judge every module this phase, replacing any fixed activity-count
  assumption.
- ROOT11_DEVOPS_PLATFORM_SCOPE.md — evaluates all 7 proposed ROOT 11 modules
  individually (READY TO AUTHOR NOW / PARTIAL-LESSON-ONLY / REQUIRES FUTURE
  LAB ENVIRONMENT), with what current infra supports vs. what GitOps/CI-CD/
  IaC/observability would each require.
- ROOT_PILOT_CURRICULUM.md — the authoritative pilot manifest: instructor-led
  as the first pilot's delivery mode, honest READY/PARTIAL/DEFERRED/NOT IN
  PILOT status per course and module, and what is intentionally excluded
  (ROOT 01-04 never authored, ROOT 08 non-capstone-gating and deferred, ROOT
  11 modules 2-7, three practice-bank modules instructor-led-only this pilot).
- PHASE6C_CURRICULUM_COMPLETION.md — the phase's own record of what was
  upgraded, why, the bug found and fixed, and the pilot readiness conclusion.

Updates ROOT_CURRICULUM_COVERAGE_MATRIX.md with the verified before/after
module counts (21->22 modules, 6->16 READY) and per-module upgrade rationale,
and ROOT_CAPSTONE_READINESS.md with a re-review confirming the unlock gate's
6 stages, and ROOT 08/09's non-gating status, are unchanged by this phase's
curriculum expansion.

Co-Authored-By: Claude Sonnet 5 <[email protected]>

docs/ROOT_CAPSTONE_READINESS.md

@@ -85,3 +85,29 @@ gap was also found and fixed in `e2e-phase5b.js`'s own capstone-completion test,
 included the `real-ops` stage in its completion loop — it was passing only because the very
 bug this phase fixes let an incomplete curriculum still start the capstone. See that test file's
 own comment for detail.
+
+## 5. Phase 6C re-review against the expanded curriculum
+
+Re-checked every item this doc depends on against Phase 6C's changes and found no gap requiring
+a fix:
+
+- **The unlock gate's 6 stages are unchanged**: Foundation, Workloads, Networking,
+  Configuration, Troubleshooting, Real Ops (`rootnode-path.json`). Phase 6C added and upgraded
+  modules within those stages' courses (ROOT 05-07, 10) plus ROOT 09 (Security) and the new
+  ROOT 11 orientation — **ROOT 08 (Storage & Scheduling) and ROOT 09 (Security) do not appear
+  among the 6 gating stages and still do not gate the capstone.** This is documented
+  architecture, not an oversight — confirmed by direct test
+  (`platform/test/e2e-phase6c.js`, "the capstone unlock gate is unaffected by ROOT 09 (security)
+  being incomplete") rather than assumed.
+- **`root-capstone-m01-operate-and-recover`** was promoted from `partial` to `ready` this phase
+  as a documented exception (no activity added — its single `capstone` activity IS the exam;
+  see `docs/PHASE6C_CURRICULUM_COMPLETION.md`). This changes only its content-model status
+  label, not the real unlock gate described in §3-4 above, which remains entirely independent.
+- **Random draw pools, timing, hint policy, and completion rule** for `rootnode-capstone` itself
+  were not touched by Phase 6C — no scenario content this phase added or changed feeds that
+  pool.
+- **The Capstone Readiness module (§1)** required no changes — its 4 activities and their
+  relationship to the (still unchanged) real unlock gate remain accurate as described above.
+
+No redesign was made or needed; Phase 6C's curriculum expansion did not require reopening the
+capstone engine.