Mark v0.9.0-alpha.1 as published

[flyingrobots]

Summary

Updates release-process current truth after the successful v0.9.0-alpha.1 publication.

This marks the v0.9 release metadata as published, records the durable tag/workflow/milestone/no-crates evidence, and updates README/ROADMAP/release-note wording so main no longer describes v0.9 as publish-ready.

Refs #70

Evidence Recorded

• Release URL: https://github.com/flyingrobots/edict/releases/tag/v0.9.0-alpha.1
• Published at: 2026-06-28T07:04:06Z
• Main merge commit: 81bacc5a240bd3ea50af934a3611ce6b3f505043
• Tag object: c6a4ea6b10d438cd407cd7f273fecf1fd012b2d3
• Peeled commit: 81bacc5a240bd3ea50af934a3611ce6b3f505043
• Main CI run: 28314566818
• Auto Release Tag run: 28314582826
• Release workflow run: 28314590143
• Milestone Phase 2: source/surface validation stage split #10 closed at 2026-06-28T07:04:06Z with zero open issues
• Release assets: 0
• Crates.io publication: none; edict-syntax remains publish = false

RED/GREEN

RED:

cargo test -p xtask release_policy_tracks_v0_9_boundary

Observed failure: policy still had status = "publish_ready" and lacked post-publication evidence.

GREEN:

cargo test -p xtask release_policy_tracks_v0_9_boundary
cargo test -p xtask release_
markdownlint-cli2 README.md ROADMAP.md CHANGELOG.md docs/**/*.md
cargo xtask verify

rg -n "publish-ready|publish_ready" README.md ROADMAP.md CHANGELOG.md docs/topics/release-process docs/releases/v0.9.0-alpha.1.md now returns only historical v0.3 changelog wording, not v0.9 current truth.

Scope Control

No feature work, tag mutation, release re-run, or version bump is included. This PR only records post-publication evidence for the immutable release that already exists.

[coderabbitai]

Warning

Review limit reached

@flyingrobots, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 42 minutes. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more credits in the billing tab to continue.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2990392f-61c8-4306-b14e-6734f8d59f8f

📥 Commits

Reviewing files that changed from the base of the PR and between 81bacc5 and 3ae767b.

📒 Files selected for processing (8)

• CHANGELOG.md
• README.md
• ROADMAP.md
• docs/releases/v0.9.0-alpha.1.md
• docs/topics/release-process/README.md
• docs/topics/release-process/policy.toml
• docs/topics/release-process/test-plan.md
• xtask/src/main.rs

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[flyingrobots]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 3ae767be86

ℹ️ 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".

[flyingrobots]

Code Lawyer Activity Summary

Item	Source	Severity	File	Commit	Outcome
CL-001	Gate	P0	PR #72	3ae767b	PASS: worktree clean, origin fetched, PR non-draft.
CL-002	Review threads	P0	PR #72	3ae767b	PASS: GraphQL reviewThreads.totalCount = 0, unresolved = 0.
CL-003	CI	P0	PR #72	3ae767b	PASS: Rust stable and MSRV checks succeeded.
CL-004	Review bot	P1	PR #72	3ae767b	PASS under fallback policy: CodeRabbit rate-limited/out of credits; @codex review completed with no major issues for 3ae767be86.
CL-005	Self-audit	P1	origin/main...HEAD	3ae767b	PASS: diff scoped to post-publication evidence and release-process status; git diff --check clean.
CL-006	Local verification	P0	workspace	3ae767b	PASS: cargo xtask verify green after the 300-second review wait.

No PR or self-discovered issues required code changes during this Code Lawyer pass.

Merge gate: open under the documented CodeRabbit fallback policy.

[chatgpt-codex-connector]

Summary

• No code changes were made. The trigger reports that PR Mark v0.9.0-alpha.1 as published #72 already passed review-thread, CI, review-bot fallback, self-audit, and local verification gates, with no issues requiring changes.
• I did not create a commit or call make_pr because the worktree is clean and there were no changes to commit. This also avoids creating an unnecessary follow-up PR.
• No topic shelf updates were needed because this follow-up made no behavior, contract, workflow, release, schema, validation, or public-surface changes. The repo guidance says not to churn topic shelves when there is no observable contract change and to state that rationale in the final report. AGENTS.mdL63-L71

Testing

• ✅ find .. -name AGENTS.md -print
• ⚠️ codex-think --remember --json (warning: codex-think is not installed in this environment)
• ✅ cat AGENTS.md
• ✅ git status --short --branch
• ✅ git log --oneline -5
• ✅ nl -ba AGENTS.md | sed -n '1,140p'

View task →