Prepare 0.1.0 - #45
Merged
Merged
Conversation
The preview label came off because the things it was hedging against are now either fixed or measured. Results come back whole rather than as a first chunk. The documentation's own commands are parsed against the real command tree on every build. The one terminal image that was reconstructed from string literals is a captured session. Three defects an adversarial review found are fixed, each with a test that fails without its fix. 0.x still means a minor version may break the API, and the README says so in the same breath as the version. What is verified and what is not stays in docs/compatibility.md: chat and the chunk mechanism were checked against a live workspace, while Genie emitting a multi-chunk result, the service-principal exchange with real credentials, AWS, GCP and macOS were not. A release is not a claim that everything works; it is a claim that the record is accurate. No tag is pushed here. That is what triggers publishing, and it is a human decision gated behind the nuget environment.
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
1 participant
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.
Version bookkeeping only — no code changes. Merging this publishes nothing; pushing the tag
does, and that stays with you.
What changes
CHANGELOG.md—Unreleasedbecomes0.1.0 — 2026-08-06README.md— status line offv0.1.0-preview.1, and the install command drops--prereleaseWhy the preview label comes off
The things it was hedging against are now either fixed or measured:
live workspace — including the permission question ADR 0004 recorded as unanswerable.
its fix.
0.xstill means a minor version may break the API, and the README says so in the same breath asthe version.
What this release does not claim
docs/compatibility.mdis the record. Verified live:chat, the chunk mechanism,agents list,ask, every output format,pack run,export last,feedback last. Not verified: Genieemitting a multi-chunk result, the service-principal exchange with real credentials, the full-result
download endpoints, visualizations,
QUERY_RESULT_EXPIREDrecovery, AWS, GCP, macOS.A release is not a claim that everything works. It is a claim that the record is accurate.
After this merges
0.1.0— the rehearsal.lakespeak --version.git tag v0.1.0 && git push origin v0.1.0.nugetenvironment gate.Steps 3 and 4 are yours.
.claude/auto-dev.mdforbids me pushing av*tag, and the environmentgate exists so a human decides.
Verification
229 tests green. Build clean under warnings-as-errors, format clean. The only remaining
0.1.0-preview.1reference is the historical changelog entry, which is correct.