v0.8.0 feat: add clean launch profiles - #19
Merged
Conversation
Co-Authored-By: OpenAI Codex <noreply@openai.com>
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
Test coverage
Pre-landing review
Four independent product, engineering, founder, and adversarial review lenses returned SHIP with no P0 or P1 findings.
Plan completion
The clean-profile release scope is complete. Broader Attention View and provider-collector work remains intentionally outside v0.8.0.
Verification
Documentation
README usage and profile semantics are updated. No architecture boundary document exists in this repository.
Test plan
Merge only after the Linux and macOS smoke matrix passes. After merge, tag the exact green main commit, verify the deterministic release archive and checksum, then update and canary the Homebrew formula.