chore: pin review capacity classification bridge

[Pigbibi]

Pins the reusable drift review checkout to AIAuditBridge #68.

This preserves the immutable SHA trust boundary and classifies temporary service-capacity exhaustion as review unavailability instead of a false invalid-review disagreement.

Validation:

• python3 -m pytest -q tests/test_reusable_drift_workflow.py
• actionlint .github/workflows/reusable-drift-check.yml
• git diff --check

[github-actions]

🤖 Codex PR Review

⚠️ Review unavailable: Codex review quota or capacity is unavailable. No direct paid API fallback was used; required CI checks remain the merge gate.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e98d0701ed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Pin only bridge builds that trust this workflow SHA

This bridge revision still deploys the Codex audit service with CODEX_AUDIT_SERVICE_ALLOWED_JOB_WORKFLOW_REFS ending at QuantPlatformKit/.github/workflows/reusable-drift-check.yml@fcddef20eea5deb876e739263042acdcb3e9cd1b; it does not include the new reusable-workflow commit 32d4cc676f068c1bf2431383c1f4fc4419b8d622. When strategy repos update their pinned uses: ref to this commit, GitHub's OIDC job_workflow_ref identifies the called workflow at that SHA, so the audit service rejects the dual-review submission before the new capacity classification can run, causing critical-drift dual reviews to fail closed instead of degrading/dispatching. Please use a bridge revision/deployment that already allowlists this QPK SHA or keep callers on an allowlisted QPK pin.

Useful? React with 👍 / 👎.