Add governance docs and v1 prep updates (README + release review)#7
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 31687b63c1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ## v1 blockers (must fix before tagging `v1.0.0`) | ||
|
|
||
| 1. **Public stability message conflicts with v1 expectations** | ||
| - README still labels the project as `alpha` and explicitly says APIs may change. |
There was a problem hiding this comment.
Remove stale alpha blocker from v1 review
This blocker is now factually incorrect: the same commit updates README.md to status-v1--prep and replaces the early-development warning, so saying the README "still labels the project as alpha" is stale. Leaving this in the v1 blocker list can mislead release decisions and keep a completed task marked as unresolved.
Useful? React with 👍 / 👎.
Motivation
Description
CONTRIBUTING.mdwith the development workflow, PR expectations, and a public API policy note.CODE_OF_CONDUCT.mdto define expected behavior and enforcement contacts.SECURITY.mdto document vulnerability reporting and supported-version guidance.README.mdstatus badge and stability blurb to reflect "v1-prep" and new messaging.RELEASE_READINESS_REVIEW.mdinto a v1-focused review that lists improvements, v1 blockers, should-fix items, and a go/no-go checklist.Testing
go test ./...across the repository and the test suite completed successfully.Codex Task