chore(OMN-15604): bump omnibase-infra to 0.38.9 (cascade leg recovery)

[jonahgabriel]

OMN-15604: recover the missed omnibase-infra 0.38.9 Dependency Cascade leg

The post-release Dependency Cascade for omnibase-infra 0.38.9 never opened a PR against this repo. Root cause: [tool.uv.sources] pinned omnibase-infra to git rev ead076af5762be7777a42d52e3ed8668f2d0fa0d (# raw-override-ok: OMN-15145), which forces uv resolution to that exact commit regardless of the declared >=0.38.4,<0.39.0 range in [project.dependencies]. Any automated uv lock --upgrade-package omnibase-infra against this override is a structural no-op — this is the concrete instance of the failure mode OMN-15604 AC4 flags ("cascade no-op is surfaced, not silent") for git-pinned first-party deps, and mirrors the same mechanism omniintelligence#828 (OMN-16287) already fixed for omnibase-core in this same file.

Verified before removing the override

Per the "content is the correct oracle, ancestry alone is not dispositive under squash-promotion" finding in OMN-15604 itself:

• git merge-base --is-ancestor ead076af5762be7777a42d52e3ed8668f2d0fa0d v0.38.9 → true — the pinned rev IS a real ancestor of the released tag here (unlike the omnibase-core case in omniintelligence#828, where ancestry across the dev/main squash boundary was false and content-diff was the only valid oracle).
• git diff --stat ead076af v0.38.9 -- src/ → 346 files changed — the pin is materially behind, not an equivalent tree under a different label.
• No other [tool.uv.sources] entry in this file (omnimarket, onex-change-control) declares an exact-pin on omnibase-infra that would force resolution elsewhere; omnimarket's own internal omnibase-infra override is not inherited here — omnimarket is pulled as a git dependency, not a uv workspace member, so its [tool.uv.sources] is local to its own project resolution only.
• No nested omnibase-core== exact-pin from any pinned transitive dep constrains omnibase-infra itself.

What changed

• Removed the omnibase-infra [tool.uv.sources] git-rev override.
• Regenerated uv.lock (uv lock) — omnibase-infra now resolves from PyPI: version = "0.38.9", source = { registry = "https://pypi.org/simple" }.

Verification

• scripts/check_dep_provenance.py --pyproject pyproject.toml: OK: no forbidden first-party git-source override and no stale cross-repo git pin.
• ruff format --check / ruff check: clean.
• mypy src/ --strict: 0 issues, 1076 source files.
• pytest -m unit: 5069 passed, 4 skipped, 6 xfailed (matches omniintelligence#828's baseline exactly), 3 errors — the 3 errors are the same pre-existing tests/unit/nodes/node_ast_extraction_compute/test_multi_repo_crawl_counts.py failure documented in omniintelligence#828's body: it crawls live sibling-repo directories on disk and trips on a gitignored local build-staging artifact, unrelated to any tracked source tree or this dependency change.
• pytest -m audit: 25 passed, 3 skipped.
• pre-commit run --all-files: clean, including "Forbid first-party git-source overrides (OMN-13873)".
• pre-commit run --all-files --hook-stage pre-push: clean (mypy pre-push + pytest-tools full).

No integration-marked tests run — Postgres/Kafka are unreachable from this host and this is a dependency-source-only change with no runtime-touching behavior change (same scope precedent as omniintelligence#828).

Precedent

omniintelligence#828 (OMN-16287, merged 2026-08-20) is the identical mechanism applied to omnibase-core in this same file, one PR prior. That PR's own sweep table flagged the omnibase-infra override as the next one to resolve, tracked under OMN-15145; this PR closes that gap under the cascade-recovery umbrella of OMN-15604.

Ticket: OMN-15604
proof_class: deployed (pending merge)

Evidence-Ticket: OMN-15604
Evidence-Source: OCC#6865

Summary by CodeRabbit

• Chores
  • Updated dependency resolution to use the declared compatible release range for infrastructure components.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b4cd582d-4ffb-4f38-9785-1628bc83ec5a

📥 Commits

Reviewing files that changed from the base of the PR and between ac6817a and f8f1b62.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• pyproject.toml

Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

---

📝 Walkthrough

Walkthrough

The dependency configuration removes the omnibase-infra Git revision override. Resolution now follows the declared >=0.38.4,<0.39.0 version range.

Changes

Dependency source resolution

Layer / File(s)	Summary
Use declared dependency range pyproject.toml	The omnibase-infra Git source override is removed. Comments document that the declared version range governs resolution.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to f8f1b

This is a localized dependency-source update that moves omnibase-infra to version 0.38.9 without runtime behavior changes. No actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the dependency bump to omnibase-infra 0.38.9 and matches the pull request objective.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jonah/omn-15604-omniintelligence-infra-0389

---

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

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.