Mark v0.7 alpha as published

[flyingrobots]

Summary

• Mark v0.7.0-alpha.1 as published in the structured release-process policy.
• Replace current-truth v0.7 publish-ready wording with published release wording.
• Record durable release evidence for the v0.7 tag, peeled commit, workflow runs, milestone closure, release URL, and no-crates publication boundary.
• Keep the branch scoped to post-release hygiene; no v0.8 implementation is included.

RED/GREEN

RED:

cargo test -p xtask release_policy_tracks_v0_7_boundary

Failed because docs/topics/release-process/policy.toml still reported status = "publish_ready" for v0.7.0-alpha.1.

GREEN:

cargo test -p xtask release_policy_tracks_v0_7_boundary
cargo test -p xtask release_
npx markdownlint-cli2 CHANGELOG.md README.md ROADMAP.md docs/releases/v0.7.0-alpha.1.md docs/topics/release-process/README.md docs/topics/release-process/test-plan.md
cargo xtask verify

Docs Impact

Release-process topic shelf, release notes, README, ROADMAP, and CHANGELOG were updated because the released world changed from publish-ready to published.

[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 10 minutes and 16 seconds. 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: 5f407d62-292a-4f81-9969-756302f5181f

📥 Commits

Reviewing files that changed from the base of the PR and between d3afa8e and 3af9860.

📒 Files selected for processing (3)

• docs/releases/v0.7.0-alpha.1.md
• docs/topics/release-process/policy.toml
• xtask/src/main.rs

Walkthrough

All release artifacts for v0.7.0-alpha.1 are updated from "publish-ready" to "published." policy.toml gains concrete publication traceability fields (timestamps, URLs, tag hashes, CI run IDs, milestone data, crates.io flag). The xtask contract test is extended to assert these new fields. Release notes, roadmap, changelog, README, and test-plan fixtures reflect the status change.

Changes

v0.7.0-alpha.1 Published Status Propagation

Layer / File(s)	Summary
policy.toml contract + xtask test assertions docs/topics/release-process/policy.toml, xtask/src/main.rs	status changed from publish_ready to published; new traceability fields added (timestamp, URL, tag object/commit, CI run IDs, milestone closure, asset count, crates_io_published = false). release_policy_tracks_v0_7_boundary test extended to assert all new required fields.
Release notes and release-process index docs/releases/v0.7.0-alpha.1.md, docs/topics/release-process/README.md	Release notes status header updated; publication metadata block added (timestamp, URL, tag peel). "Required Verification"/"Publication Plan" sections replaced with "Verification" and "Publication Evidence." Release-process index entry updated to published with full CI/milestone/shelf audit evidence.
Surface docs status wording CHANGELOG.md, README.md, ROADMAP.md, docs/topics/release-process/test-plan.md	"publish-ready" → "published" across all surface references. ROADMAP adds milestone #8, closes #59, records release URL and tag commit. Test-plan fixture oracle wording adjusted accordingly.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

Possibly related issues

• Prepare v0.7.0-alpha.1 release #59: This PR directly closes the work tracked by issue #59 — advancing v0.7.0-alpha.1 from publish-ready to published and recording durable publication evidence.

Possibly related PRs

• flyingrobots/edict#26: Shares the same xtask/src/main.rs release-process contract validation and policy.toml boundary area.
• flyingrobots/edict#32: Also extends xtask/src/main.rs policy status parsing/validation for release_notes.* entries.
• flyingrobots/edict#43: Introduced analogous release-policy assertions in the same xtask test file for earlier versions.

Poem

🏷️ Once "publish-ready," now truly published,
The tag is peeled, the milestone's banished,
CI run IDs etched in stone,
No crates.io — this ships alone,
The policy.toml stands complete,
Evidence logged, the diff is neat. ✅

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main release-state change from publish-ready to published.
Description check	✅ Passed	The description is directly related to the release-state update and supporting release evidence changes.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d3afa8e1a0

ℹ️ 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]

@codex review please

[flyingrobots]

Code Lawyer Activity Summary

Item	Severity	Source	File(s)	Commit	Outcome
Mark v0.7.0-alpha.1 as published and record durable release evidence	P3	Self	docs/topics/release-process/policy.toml, docs/topics/release-process/README.md, docs/releases/v0.7.0-alpha.1.md, ROADMAP.md, README.md, CHANGELOG.md, xtask/src/main.rs	d3afa8e	Implemented with RED/GREEN release-policy regression and docs updates.
Clarify that post-publication evidence was not the immutable release body source	P2	PR / Codex	docs/releases/v0.7.0-alpha.1.md, docs/topics/release-process/policy.toml, xtask/src/main.rs	70bbb72	Implemented with structured policy fields for release-note source commit and post-publication evidence commit; resolved thread PRRT_kwDOS96-Us6Mwov3.
Review threads	-	PR	-	70bbb72	GraphQL reviewThreads total: 1; unresolved: 0. The only thread is resolved and outdated.
Review bot	-	PR	-	70bbb72	CodeRabbit approved current head.
CI	-	GitHub	PR #61	70bbb72	Rust stable and Rust MSRV checks passed.
Local verification	-	Self	workspace	70bbb72	cargo test -p xtask release_, markdownlint touched docs, and cargo xtask verify passed.
Self-audit	-	Self	origin/main...HEAD	70bbb72	git diff --check origin/main...HEAD clean; no new self-discovered blockers.

Merge gate: open under current repository policy.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 70bbb72b97

ℹ️ 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]

@codex review please

[chatgpt-codex-connector]

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

Reviewed commit: 3af9860736

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