0.10.0-S12: 0.10.0 exit audit, promotion, and opening the 1.0.0-rc train

[mberrys]

Session 0.10.0-S12 · type audit · milestone 0.10.0 — Platform Hardening, Extension Ecosystem & 1.0 Readiness

GA preparation. All graduated-automation stages hardened.

Delivers

Exit audit plus promotion; open the 1.0.0-rc train.

Scope and ownership boundary

• This session owns: Exit audit, catalogue/docs regeneration, exact-SHA gate, promotion.
• This session may not: New behaviour.
• The milestone must not create: new product-scope features hiding as "hardening", a web shell, or a second language runtime.
• Out of scope for the milestone: New capability families; anything that widens authority boundaries.

Tasks

• Verify every exit-gate item below against evidence, not against PR titles or headlines.
• Run the release gate on one exact SHA and record the result.
• Confirm no distribution or platform decision has been inherited by drift.
• Hand the dossier to the operator for acceptance.
• Open the 1.0.0-rc train on acceptance.
• Produce the session handoff packet (exact SHA, changed files, tests run, deviations, remaining risks) — the only valid inter-session interface.

Dependencies

• 0.10.0-S11 — 0.10.0-S11: 1.0 readiness dossier: rc criteria, limitations, and upgrade guide #478

Parallel lanes

Sanctioned parallelism for 0.10.0: S02/S03 after S01; S05/S07/S08 as independent lanes; S09 after S03 and S07.

Lanes run concurrently only where the session map marks them; concurrency outside the sanctioned lanes is not permitted.

Exit evidence

Release Gate green; operator acceptance recorded.

PR titles, commit messages, and document headlines are never acceptance evidence. Only this session's exit evidence, on an exact SHA, closes this gate.

Milestone exit gate verified by this session

• The 1.0 public contract surface is declared, fixture-frozen, and deprecation-governed; experimental surfaces are labelled.
• An example third-party plugin builds and runs against only the documented SDK.
• Benchmarks with full identity run as regression gates within budgets, including job-store scale.
• Distribution decisions (signing, updates, macOS) are executed or explicitly decided - none inherited by drift.
• Security/privacy audit findings are fixed or accepted on the record.
• The 1.0 readiness dossier exists and its rc criteria are demonstrated on an exact SHA.

Milestone context

Objective. Declare and freeze the 1.0 public contract surface (CLI envelopes, persisted schema kinds, plugin capability ABI, documented behaviour) with a deprecation policy; ship the versioned plugin SDK with admission policy and threat review; run the performance/scale program on named benchmark identities; harden distribution (signing procurement decision, update channel, SmartScreen exit); decide macOS explicitly; refresh the security/privacy audit; complete operator documentation; and assemble the 1.0 readiness dossier with release-candidate criteria demonstrated on an exact SHA.

Stop rules. A contract that cannot be fixture-frozen is redesigned or labelled experimental - never silently promised. Scale/performance failures block the release candidate; missing platform evidence is unavailable, not PASS.

Authoring note

Per the rolling-wave rule in section 7 of the roadmap, the fully executable specification for this session (exact starting SHA, allowed layers and files, components to reuse, named tests, escalation conditions) is authored when the milestone activates, after its S00 reconcile. This issue carries the fixed frame — objective, boundary, dependencies, and exit evidence — and is refined, not replaced, at activation.

---

Full context: docs/ROADMAP_0.5.0-0.10.0.md section 4.6 and docs/github-milestones/0.10.0.md.