Route monthly optimization tasks to Codex bridge

[Pigbibi]

Summary

This PR routes the normal CryptoSnapshotPipelines monthly code-remediation path through the self-hosted VPS ccbot/Codex bridge instead of the GitHub-hosted Claude Action path.

• label low-risk non-experiment [auto-pr-safe] Crypto monthly optimization task issues with codex-bridge and auto-merge-ok
• add an explicit Codex bridge contract to generated task issues, including branch, PR marker, draft-first, test, and guarded-file requirements
• keep the existing Claude Action workflow as a manual-dispatch/non-Codex fallback by skipping issues already queued for codex-bridge
• extend the post-CI merge gate to recognize codex/monthly-optimization-issue-* branches and require the PR-level auto-merge-ok label for Codex PRs
• add Codex PR Feedback so failed CI or changes-requested reviews are posted back to the source codex-bridge issue for another ccbot/Codex pass
• document the ccbot/Codex remediation flow in README and the operator runbook

Validation

• python3 -m pytest tests/test_fanout_monthly_optimization_tasks.py tests/test_auto_optimization_pr_workflow_config.py tests/test_prepare_auto_optimization_pr.py -q
• git diff --check
• GitHub Actions CI test: passing on ed88f8d

Refs QuantStrategyLab/AuditOrchestrator#1

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ed88f8da6e

ℹ️ 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]

Remove undocumented task-level gate for Codex PR merges

The Codex branch path is now routed through this gate, but should_merge still requires task_level_allowed from a literal PR-body string ("Task-level auto-merge eligible: yes"). The new Codex contract text generated in scripts/fanout_monthly_optimization_tasks.py does not instruct Codex to include that marker, so a Codex PR can satisfy the documented branch/marker/label rules and still be permanently skipped with task_level_guard. This effectively blocks the new Codex auto-merge flow unless out-of-band behavior adds that exact line.

Useful? React with 👍 / 👎.