Upgrade crypto live pool artifact namespace

[Pigbibi]

Summary:

• Upgrade artifact namespace from crypto-leader-rotation to crypto-live-pool-pipelines.
• Rename strategy artifact contract to crypto_live_pool_rotation.live_pool.v1 and Firestore document to CRYPTO_LIVE_POOL_ROTATION_LIVE_POOL.
• Update config defaults, publish workflow, release contract validation, docs, fixtures, and tests.

Tests:

• timeout 120 env PYTHONPATH=/home/ubuntu/Projects/CryptoLivePoolPipelines /usr/bin/python3 -m unittest tests.test_monthly_publish_workflow_config tests.test_monthly_report_bundle -v
• timeout 120 env PYTHONPATH=/home/ubuntu/Projects/CryptoLivePoolPipelines /tmp/crypto-live-pool-test-venv/bin/python -m unittest tests.test_release_contract tests.test_release_status_summary -v
• Result: OK.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1876345f93

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

Preserve the existing Firestore pointer during migration

When the scheduled monthly workflow runs in an environment that has not explicitly set FIRESTORE_DOCUMENT, it will now publish only to strategy/CRYPTO_LIVE_POOL_ROTATION_LIVE_POOL; the previous v1 contract documented strategy/CRYPTO_LEADER_ROTATION_LIVE_POOL as the compatibility pointer for downstream readers. Without a dual-write, alias, or staged migration, those existing readers will keep seeing the old document and stop receiving monthly pool updates after this workflow publishes.

Useful? React with 👍 / 👎.