docs(release): add 0.4.0-rc.1 readiness proof by EffortlessSteven · Pull Request #255 · EffortlessMetrics/shipper

EffortlessSteven · 2026-05-13T16:16:08Z

Summary:

add docs/release/0.4.0-readiness.md for the 0.4.0-rc.1 evidence packet
promote only the release-readiness support-tier entry now that the proof artifact exists
update the active goal manifest to point at the PR 15: 0.4.0-rc.1 release dry-run proof #195 release-readiness work item

Evidence:

cargo run -p shipper -- plan
copied-binary shipper preflight --preflight-only --format json --state-dir target/release-proof-state-copied => finishability proven
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features => 4266 passed, 36 ignored
cargo test --workspace --doc => 19 passed, 36 ignored
cargo check --workspace
cargo audit
cargo doc --workspace --no-deps --document-private-items
cargo test -p shipper-cli --test bdd_publish => 26 passed
cargo publish --dry-run --workspace => all 13 crates packaged, verified, and dry-run uploaded
cargo xtask check-doc-contracts --mode advisory
cargo xtask policy-report
cargo xtask check-file-policy --mode blocking-allowlist
cargo xtask no-panic check
cargo xtask check-lint-policy
cargo xtask ripr-pr

Notes:

No tag was created and no crate was published.
Isolated cargo publish --dry-run -p passed for tier-1 leaf crates. The first downstream isolated dry-run, shipper-types, is blocked before verification because unpublished rc.1 dependencies are absent from the crates.io index; cargo publish --dry-run --workspace is the successful Cargo-supported proof for this unpublished multi-crate workspace state.

Closes #195

gemini-code-assist · 2026-05-13T16:16:13Z

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

chatgpt-codex-connector · 2026-05-13T16:16:13Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

coderabbitai · 2026-05-13T16:16:17Z

Warning

Rate limit exceeded

@EffortlessSteven has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 27 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: e46b2a2e-e661-4d4f-a74c-675970f25f85

📥 Commits

Reviewing files that changed from the base of the PR and between d72f58b and 28800bb.

📒 Files selected for processing (3)

.shipper-meta/goals/active.toml
docs/release/0.4.0-readiness.md
docs/status/SUPPORT_TIERS.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch docs/0.4.0-readiness-proof

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

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

factory-droid · 2026-05-13T16:16:33Z

Droid finished @EffortlessSteven's task —— View job

Droid review complete for PR #255.

Validation result: 3 findings posted — 1 P1, 2 P2.

P1: Evidence base commit in docs/release/0.4.0-readiness.md line 3 does not match PR head SHA; spec SHIPPER-SPEC-0002 requires identifying the commit under review.
P2: Preflight gate sidecar target/release-proof-state-copied/preflight_workspace_verify.txt not committed; unverifiable by reviewers.
P2: ripr-pr advisory summary target/ripr/pilot/pilot-summary.md not committed; top recommendation about crates/shipper-cli/src/lib.rs::run boundary discriminator coverage unverifiable.

No security issues found.

factory-droid · 2026-05-13T16:29:27Z

@@ -0,0 +1,111 @@
+# Shipper 0.4.0-rc.1 Readiness
+
+Version: 0.4.0-rc.1


[P1] Evidence base commit does not match PR head

Line 3 states Evidence base commit: d72f58b251b12d93ba3e3b8e7bd0d636d7c8264d, but the PR head SHA is 28800bb48e8bd65cfd48bbe403769a291003d1a8. There is exactly one commit between them (the PR's own commit), and the spec (SHIPPER-SPEC-0002) requires the proof to "identify the commit SHA under review." Using the parent commit creates confusion about what is actually being proven — the evidence run was performed before the PR was finalized. The Evidence base commit field should reflect the commit on which the gates were actually run, which in this case should be the PR head commit or the merge-base if running against a different base.

factory-droid · 2026-05-13T16:29:27Z

+|---|---:|---|
+| Version check | pass | Root workspace and publishable workspace dependency pins read `0.4.0-rc.1`; changelog has `## [0.4.0-rc.1] - 2026-05-12`. |
+| `cargo run -p shipper -- plan` | pass | Plan ID `5d63c5b0725a59a01c1fa1406220808f5a7b1a166c0ddf76d3ba97d13e6feeb5`; 13 publishable crates; `xtask@0.0.0` skipped as `publish = false`. |
+| `shipper preflight --preflight-only --format json --state-dir target/release-proof-state-copied` | pass | `finishability = "proven"`; token detected; all 13 packages `dry_run_passed = true`; sidecar under `target/release-proof-state-copied/preflight_workspace_verify.txt`. |


[P2] Sidecar file referenced in preflight gate evidence not committed

Line 29 references target/release-proof-state-copied/preflight_workspace_verify.txt as a sidecar file for the preflight gate. This path is a runtime artifact from the evidence run and was not committed alongside the document. Reviewers cannot verify this evidence independently. Consider either committing the sidecar file as part of the evidence packet or rephrasing the evidence to note it was observed locally but not persisted.

factory-droid · 2026-05-13T16:29:27Z

+| `cargo xtask check-file-policy --mode blocking-allowlist` | pass | 204 tracked files, 41 entries, 0 unreceipted, 0 missing fields, 0 expired. |
+| `cargo xtask no-panic check` | pass | 25 baseline entries, 25 current entries, no new/resolved/count drift. |
+| `cargo xtask check-lint-policy` | pass | MSRV aligned across Rust policy surfaces at 1.95. |
+| `cargo xtask ripr-pr` | advisory | Completed. Top recommendation: add boundary discriminator coverage for `crates/shipper-cli/src/lib.rs::run`; details in `target/ripr/pilot/pilot-summary.md`. |


[P2] ripr-pr advisory summary not committed

Line 43 references target/ripr/pilot/pilot-summary.md for details of the ripr advisory. This is a runtime artifact and was not committed. The summary states a top recommendation about boundary discriminator coverage for crates/shipper-cli/src/lib.rs::run, but reviewers cannot verify this claim independently. Consider including the key recommendation inline in the document or committing the summary as part of the advisory evidence.

docs(release): add 0.4.0-rc.1 readiness proof

28800bb

factory-droid Bot reviewed May 13, 2026

View reviewed changes

EffortlessSteven merged commit 5879dea into main May 13, 2026
27 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

docs(release): add 0.4.0-rc.1 readiness proof#255

docs(release): add 0.4.0-rc.1 readiness proof#255
EffortlessSteven merged 1 commit into
mainfrom
docs/0.4.0-readiness-proof

EffortlessSteven commented May 13, 2026

Uh oh!

gemini-code-assist Bot commented May 13, 2026

Uh oh!

chatgpt-codex-connector Bot commented May 13, 2026

Uh oh!

coderabbitai Bot commented May 13, 2026

Rate limit exceeded

Uh oh!

factory-droid Bot commented May 13, 2026 •

edited

Loading

Uh oh!

factory-droid Bot May 13, 2026

Uh oh!

factory-droid Bot May 13, 2026

Uh oh!

factory-droid Bot May 13, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		@@ -0,0 +1,111 @@
		# Shipper 0.4.0-rc.1 Readiness

		Version: 0.4.0-rc.1

Uh oh!

Conversation

EffortlessSteven commented May 13, 2026

Uh oh!

gemini-code-assist Bot commented May 13, 2026

Uh oh!

chatgpt-codex-connector Bot commented May 13, 2026

Uh oh!

coderabbitai Bot commented May 13, 2026

Rate limit exceeded

Uh oh!

factory-droid Bot commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

factory-droid Bot May 13, 2026

Choose a reason for hiding this comment

Uh oh!

factory-droid Bot May 13, 2026

Choose a reason for hiding this comment

Uh oh!

factory-droid Bot May 13, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

factory-droid Bot commented May 13, 2026 •

edited

Loading