[jonahgabriel]

Summary

Follow-up to OMN-11348 wave 2 OCC bundle (PR #1250, merged at 262b14c). After the initial OCC PR merged, the 4 still-open release PRs (compat, core, oii, omem) needed empty-commit pushes to refresh their PR_EVENT_BODY webhook payload caches — those caches still showed the PR bodies without the OMN-11348 ticket reference (added via REST API PATCH after PR creation), causing receipt-gate to fail with "PR title/body does not cite an OMN ticket".

The empty-commit pushes changed each PR's head SHA, which made the SHA pins in the merged OCC contract stale. This PR updates the 4 receipts + contract check_value entries to match the new head SHAs.

SHA refreshes

Repo	PR	Old SHA	New SHA
omnibase_compat	#95	9554d993	c8c41c8c
omnibase_core	#1120	1834272d	3159cb9d
omniintelligence	#657	63ca7019	dffac2f3
omnimemory	#324	5da2e419	cbcdd75d

Not refreshed (already merged before OCC #1250 landed)

• omnibase_spi chore(contracts): backfill ModelTicketContract for 50 done tickets [OMN-8637 wave 50] #212 (v0.21.0) — MERGED, tag published
• omninode_infra fix(OMN-9893): set pr_number=948 in OMN-9892 receipts (int, not "TBD") #442 (v0.2.0) — MERGED, tag published
• omnidash test(cross-repo): verify topic constants match kafka_boundaries manifest [OMN-6284] #102 (v1.0.0) — MERGED, tag published

These three repos' receipts in the OCC main contract have the correct SHAs as recorded at merge time.

Files

• contracts/OMN-11348.yaml — 4 check_value entries refreshed
• drift/dod_receipts/OMN-11348/dod-release-compat-v0.4.1/command.yaml
• drift/dod_receipts/OMN-11348/dod-release-core-v0.42.0/command.yaml
• drift/dod_receipts/OMN-11348/dod-release-oii-v0.24.0/command.yaml
• drift/dod_receipts/OMN-11348/dod-release-omem-v0.16.0/command.yaml

Evidence-Ticket: OMN-11348

Summary by CodeRabbit

• Chores
  • Updated release binding configurations and validation metadata for four package versions: dod-release-compat-v0.4.1, dod-release-core-v0.42.0, dod-release-oii-v0.24.0, and dod-release-omem-v0.16.0.

[coderabbitai]

Warning

Rate limit exceeded

@jonahgabriel has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 9 minutes and 2 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 48328288-09e1-40c9-8341-212f407e9cff

📥 Commits

Reviewing files that changed from the base of the PR and between d85cfc6 and 60ff859.

📒 Files selected for processing (1)

• drift/dod_receipts/OMN-11348/dod-occ-pr-self/command.yaml

📝 Walkthrough

Walkthrough

This PR updates evidence bindings and receipt records for OCC ticket OMN-11348. The contract file specifies expected commit SHAs for four release checks, and corresponding receipt files record the actual observed state with synchronized timestamps and probe outputs for each release.

Changes

OMN-11348 Evidence Bindings Re-bind

Layer / File(s)	Summary
Evidence contract expectations contracts/OMN-11348.yaml	Expected commit_sha values are updated for four release evidence checks: dod-release-compat-v0.4.1, dod-release-core-v0.42.0, dod-release-oii-v0.24.0, and dod-release-omem-v0.16.0. All other check parameters remain unchanged.
Receipt for dod-release-compat-v0.4.1 drift/dod_receipts/OMN-11348/dod-release-compat-v0.4.1/command.yaml	Receipt record is synchronized to the new commit SHA: check_value assertion, metadata fields (commit_sha, run_timestamp), probe_stdout headRefOid, and actual_output text all reflect the new commit state and worktree path.
Receipt for dod-release-core-v0.42.0 drift/dod_receipts/OMN-11348/dod-release-core-v0.42.0/command.yaml	Receipt record is updated with new commit SHA, corresponding run_timestamp, probe_stdout output, actual_output text including parenthetical note, and working_dir path change.
Receipt for dod-release-oii-v0.24.0 drift/dod_receipts/OMN-11348/dod-release-oii-v0.24.0/command.yaml	Receipt validation now greps for the exact new commit_sha, with synchronized run_timestamp, commit_sha, probe_stdout result, and actual_output text reflecting the new release head state.
Receipt for dod-release-omem-v0.16.0 drift/dod_receipts/OMN-11348/dod-release-omem-v0.16.0/command.yaml	Receipt record is updated with new commit_sha assertion and synchronized execution metadata (commit_sha, run_timestamp, probe_stdout headRefOid, actual_output details), plus working_dir path change.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• OmniNode-ai/onex_change_control#1250: Earlier PR that introduced the OMN-11348 evidence bindings; this PR continues by re-binding to updated commit SHAs.

Poem

A rabbit hops through commits with glee,
Re-binding proof for OMN-11348's spree,
Four releases dance with SHAs so new,
Contracts and receipts both synced and true! 🐰✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: refreshing SHA pins for four release PRs (compat/core/oii/omem) in response to ticket OMN-11348.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/release-batch-occ-11348-sha-refresh

---

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