Session 0.10.0-S03 · type contract · milestone 0.10.0 — Platform Hardening, Extension Ecosystem & 1.0 Readiness
GA preparation. All graduated-automation stages hardened.
Delivers
Plugin SDK: capability contract docs plus example plugin.
Scope and ownership boundary
- This session owns: One schema/identity/state-machine contract plus fixtures.
- This session may not: Persistence, UI, surfaces.
- 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
Dependencies
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
Example plugin builds against the documented contract only.
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 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.
Session
0.10.0-S03· typecontract· milestone 0.10.0 — Platform Hardening, Extension Ecosystem & 1.0 ReadinessGA preparation. All graduated-automation stages hardened.
Delivers
Plugin SDK: capability contract docs plus example plugin.
Scope and ownership boundary
Tasks
Dependencies
0.10.0-S01— 0.10.0-S01: 1.0 contract-surface declaration and deprecation policy #468Parallel 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
Example plugin builds against the documented contract only.
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 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
S00reconcile. 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.mdsection 4.6 anddocs/github-milestones/0.10.0.md.