fix(release): no-verify crate publish; age failed attempts

[DecisionNerd]

Summary

• Latest recovery 30717946991 published graphforge-api (14/15) then failed on graphforge-cli: failed to verify package tarball / build.rs cannot find workspace project-skills (outside the packaged crate; RC uses --no-verify).
• Attempt orphan v0.5.1-attempt-crates-graphforge-cli.json left recon as write_attempt_outcome_unknown.
• Publish with cargo publish --locked --no-verify (checksum gate unchanged); age out attempt-without-receipt after the 15m visibility bound when live stays 404; overlay release_registry.py on recovery checkouts.
• Tag stays dd1fd8c.

Test plan

• python3 scripts/ci/test-publish-crates.py
• python3 scripts/ci/test-release-action.py
• python3 scripts/ci/test-release-publish-preflight.py
• Required CI / CI Gate green on exact head SHA
• After merge + attempt visibility bound: one publish.yaml recovery for cli

Closes #329

Made with Cursor

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Note

Add --no-verify to cargo publish and age failed release attempts past visibility bound

• Adds --no-verify to all cargo publish invocations in publish_crates.py to skip local verification, which fails for crates with workspace path embeddings.
• Changes observe-all in release_registry.py so that prior write attempts with no receipt are only marked indeterminate within a MAX_VISIBILITY_SECONDS window; after that window they remain absent with evidence.attempt_visibility_bound_exhausted = true.
• Adds a step to the candidate preflight job in publish.yaml to fetch and install release_registry.py from refs/remotes/origin/main so later steps can invoke it.
• Behavioral Change: observe-all results for nodes with aged-out failed attempts will now return absent instead of indeterminate.

^{Macroscope summarized fc8c63b.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 13 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

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

How do review 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 refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 076170a1-2f6a-4fa4-851f-0938d5839d41

📥 Commits

Reviewing files that changed from the base of the PR and between a4ee9f8 and fc8c63b.

⛔ Files ignored due to path filters (1)

• .github/workflows/publish.yaml is excluded by !**/.github/**

📒 Files selected for processing (5)

• scripts/ci/release_registry.py
• scripts/ci/test-publish-crates.py
• scripts/ci/test-release-action.py
• scripts/ci/test-release-publish-preflight.py
• scripts/publish_crates.py

---

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