R1: prepare v0.2.0 public release readiness#150
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release Boundary
Verification
Upgrade Overview
Protected Areas
Compatibility Impact
This is a release-readiness packaging sprint. It does not widen the shipped product surface; it documents the actual shipped baseline and prepares the repo, checklists, and runbooks for a pre-1.0 public release.
Migration / Rollout
Merge this sprint to main first, then execute docs/release/v0.2.0-tag-plan.md from main to create the v0.2.0 tag in the documented order. No feature migration is introduced beyond release doc and evidence alignment.
Operator Action
Use the new release checklist and runbook as the public release gate, follow the documented provider_plus_mcp recommended path and mcp_only fallback where referenced, and use the documented smoke/demo commands as the final release verification set.
Validation
Branch-local verification passed:
Rollback
Revert the squash merge commit to restore the pre-R1 release docs and smoke harness state, then rerun the release verification set before attempting the tag procedure again.