Fail closed not-evidenced strategy catalog profiles

[Pigbibi]

Summary

• fail closed the catalog declarations for the eight profiles that remain runtime-enabled on the fresh base but lack verifiable current promotion-grade evidence-v2 bound to an accepted human identity in the canonical repository mains and local receipt registry
• keep those profiles research/backtest-only and dry-run-only in the source catalog, generated console assets, fallback catalog, and Binance crypto example target
• align the internal dependency matrix and its existing pin contract with merged BinancePlatform PR Fix account mapping collisions across platform-prefixed keys #149 and UsEquitySnapshotPipelines PR #265 identities

Semantics and safety

This is a conservative NOT_EVIDENCED catalog proposal. It does not mean any strategy is invalid, bad, or inactive. Evidence or acceptance outside the checked canonical repositories and registered receipts remains unknown.

This PR does not remove or mutate runtime targets, services, schedulers, providers, brokers, orders, positions, or capital.

Keep this PR open and unmerged for human approval. Merging platform-config.json or strategy-switch console paths to main triggers the Cloudflare Worker deployment workflow, strategy catalog KV/config sync, and live API count verification.

Validation

• config build check and runtime target validation
• focused Python: 109 tests
• full Python: 172 tests
• Node worker validation: 151 tests, cash financing tests, and asset syntax checks
• fresh strict dependency matrix: 30 files, 0 issues, 0 missing files across 14 consumer repositories
• Python compile and package build
• actionlint 1.7.12
• generated asset consistency, JSON validation, diff/scope11/secret checks
• Ruff non-regression: changed Python files have the same 4 existing findings as the old base

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:a21793df3c

ℹ️ 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".