Part of #120 (Phase 5 — Release).
Scope
Finalize the consumer-facing release documentation, once the full break surface is known and soaking.
docs/migration-v0.8-to-v1.0.md — review end to end. Per-PR entries have been accumulating throughout the cycle by design, so this is a coherence and completeness pass, not a writeup from scratch. Confirm the scope decision holds: breaking changes plus behavioral changes that can require action on upgrade.- Test the AI migration prompt. The guide's top-of-file prompt is a v1.0.0 deliverable and has never been exercised. Run it against a real sample consumer
build.ps1 with an agent and fix what it gets wrong. An untested prompt that produces a broken build.ps1 is worse than no prompt.
CHANGELOG.md — write the 1.0.0 entry, summarizing the breaks and linking to the migration guide.
Gate
Blocked on 1.0.0-preview2 — the break surface must be complete before the guide can be called finished.
Done when
The migration guide is complete, the AI prompt has been verified against a sample consumer build, and the changelog entry is written.
Part of #120 (Phase 5 — Release).
Scope
Finalize the consumer-facing release documentation, once the full break surface is known and soaking.
docs/migration-v0.8-to-v1.0.md— review end to end. Per-PR entries have been accumulating throughout the cycle by design, so this is a coherence and completeness pass, not a writeup from scratch. Confirm the scope decision holds: breaking changes plus behavioral changes that can require action on upgrade.build.ps1with an agent and fix what it gets wrong. An untested prompt that produces a brokenbuild.ps1is worse than no prompt.CHANGELOG.md— write the 1.0.0 entry, summarizing the breaks and linking to the migration guide.Gate
Blocked on
1.0.0-preview2— the break surface must be complete before the guide can be called finished.Done when
The migration guide is complete, the AI prompt has been verified against a sample consumer build, and the changelog entry is written.