Repository navigation
Align project docs with shipped v0.1.1 (post-MVP) - #6
Merged
Merged
Conversation
Mark the core inventory as released, point roadmap work at v0.2, publish canonical v0.1.1 notes, and soften leftover MVP wording in operator docs and agent rules. Co-authored-by: Alejandro Azario <aleaz@users.noreply.github.com>
aleaz
added a commit
that referenced
this pull request
Sep 13, 2026
Resolve development-guide, roadmap, and release-notes conflicts favoring the shipped v0.1.1 baseline; keep a text fence on the smoke block.
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.
Post-release hygiene after publishing
v0.1.1.Changes
docs/releases/v0.1.1-notes.md; keepv0.1.0notes as historical/supersededv0.1.1Not in this PR