docs(OMN-10278): ticket contract for mandatory DI params resolver fix

[jonahgabriel]

Summary

• Add OCC contract for OMN-10278 (mandatory DI params — resolver multi-param injection)
• Contract covers omnibase_core PR 1057: RESOLVED_VIA_KNOWN_PARAMS enum + resolver Step 4 extension
• Includes deploy verification dod_evidence (dod-005)

Evidence-Ticket: OMN-10278

Test plan

• Contract validates against ModelTicketContract (uv run validate-yaml contracts/OMN-10278.yaml)
• Pre-commit hooks pass

Summary by CodeRabbit

• Chores
  • Updated contract specifications and deployment verification records.

[coderabbitai]

Warning

Rate limit exceeded

@jonahgabriel has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minute and 1 second 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: e395b76c-2bd4-4f22-ba40-7737ca5f0109

📥 Commits

Reviewing files that changed from the base of the PR and between eef92f3 and e6794a5.

📒 Files selected for processing (9)

• contracts/OMN-10278.yaml
• drift/dod_receipts/OMN-10278/dod-005/command.yaml
• drift/dod_receipts/OMN-10278/dod-core-known-params-enum/command.yaml
• drift/dod_receipts/OMN-10278/dod-core-known-providers/command.yaml
• drift/dod_receipts/OMN-10278/dod-core-pr-open/command.yaml
• drift/dod_receipts/OMN-10278/dod-core-tests/command.yaml
• drift/dod_receipts/OMN-10278/dod-occ-pr-912/command.yaml
• drift/dod_receipts/OMN-10278/dod-occ-pr-913/command.yaml
• drift/dod_receipts/OMN-10278/dod-session-id-bridge/command.yaml

📝 Walkthrough

Walkthrough

Updated contract OMN-10278 from batch commit recovery to resolver multi-parameter dependency injection verification. Replaced evidence requirements with omnibase_core PR 1057 test suite checks. Extended verification checks to include enum updates, resolver multi-param injection, unit tests, and PR status. Added deployment evidence record file with health probe and container log inspection command results.

Changes

Resolver DI Contract and Evidence

Layer / File(s)	Summary
Contract Definition Update contracts/OMN-10278.yaml	Contract title/summary rewritten for resolver multi-param DI injection focus. Evidence requirements redirected from local YAML validation to omnibase_core PR 1057 test suite and CI checks. dod-001 updated to reference RESOLVED_VIA_KNOWN_PARAMS.
Verification Checks Registry contracts/OMN-10278.yaml	Checks list extended with four new manual validation entries: enum outcome update, resolver Step 4 multi-param known injection, unit test pass verification, and PR-open status on main. New dod-005 receipt check references command.yaml deployment assertions.
Deployment Evidence Record drift/dod_receipts/OMN-10278/dod-005/command.yaml	New evidence record file added with schema identifiers and command-check metadata. Defines health probe via curl and container log inspection via ssh with grep for "TypeError" count. Records execution payload, probe results, and verification metadata with PASS status and exit code 0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Hops through contracts with DI care,
Resolvers multi-param everywhere,
Evidence receipts now come to play,
Deployment checks pass the day!

🚥 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 clearly describes the main change: adding a ticket contract for mandatory DI params resolver fix. It directly relates to the primary objective of the pull request.
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/omn-10278-mandatory-di-params-contract

---

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

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@contracts/OMN-10278.yaml`:
- Around line 60-64: The check in the "checks" block uses check_type: command
and check_value that counts any occurrence of "pass" (grep -c 'pass') which
doesn't enforce the stated "69 green" and the description is inconsistent with
the current 42 passes; update the "check_value" to assert an exact count (for
example, count only whole-line "pass" entries and compare to the expected
number) and either change the description field to the actual expected count or
update the expected count to 69 if the PR will reach that; specifically, modify
the check_value string (the command executed by the check) to perform an exact
numeric comparison against the target (referencing the existing check_value) and
align the description field with that target number.

In `@drift/dod_receipts/OMN-10278/dod-005/command.yaml`:
- Line 10: Update the commit_sha entry in the command.yaml to the new head
commit value: replace the current commit_sha
"508757e3191018c72907c86d5ea0ec657d3166ce" with
"29764d6d291d43580882f1dcfda70487e6c694fc" so the recorded commit matches the
OmniNode-ai/omnibase_core PR `#1057` head; edit the commit_sha field in the
existing YAML (the key named commit_sha) to the new string.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 53e61817-959e-4780-ac83-943370976db0

📥 Commits

Reviewing files that changed from the base of the PR and between ff9cce9 and eef92f3.

📒 Files selected for processing (2)

• contracts/OMN-10278.yaml
• drift/dod_receipts/OMN-10278/dod-005/command.yaml