Monthly Report Review: 2026-05-01

[github-actions]

Monthly Report Review Input

Use this file as the primary review input for the monthly upstream release package.

Bundle metadata

• Artifact name: monthly-report-2026-05-01
• Report month: 2026-05
• As-of date: 2026-05-01
• Version / mode: 2026-05-01-core_major / core_major
• Pool size: 5
• Symbols: TRXUSDT, TAOUSDT, DOGEUSDT, LINKUSDT, AVAXUSDT

Review intent

• This is an upstream selector review for CryptoSnapshotPipelines, not a downstream execution report.
• The main question is whether the current monthly 5-symbol pool still looks like a sound production selector output, and what additional research evidence is still missing.
• Shadow / challenger coverage should be used for strategy-optimization judgment when available. If missing, treat optimization evidence as incomplete rather than forcing a strong conclusion.
• Downstream BinancePlatform consumes this pool monthly and then applies its own execution logic on top.

Strategy review questions

1. Does the official pool look internally consistent with the ranking preview and release metadata?
2. Are score spread and selected symbols reasonable for a Binance Spot mainstream leader selector?
3. Is shadow / challenger evidence present, and if not, what is the highest-value missing comparison?
4. What are the most useful next low-risk research directions before changing production selector logic?

Release Status Summary

Release Status Summary

Generated: 2026-05-01T07:27:57.505423+00:00

Official release

• Status: ok
• As-of date: 2026-05-01
• Version / mode: 2026-05-01-core_major / core_major
• Pool size: 5
• Symbols: TRXUSDT, TAOUSDT, DOGEUSDT, LINKUSDT, AVAXUSDT
• Source project: crypto-leader-rotation

Artifact summary

• latest_universe symbol count: 7
• latest_ranking row count: 7
• latest_ranking selected count: 5
• artifact contract version: crypto_leader_rotation.live_pool.v1

Ranking preview

• Repo hygiene: add validation CI and governance files #1 TRXUSDT score=1.000000 selected=True
• chore(deps): bump actions/upload-artifact from 4 to 7 #2 TAOUSDT score=0.678571 selected=True
• chore(deps): bump actions/checkout from 5 to 6 #3 DOGEUSDT score=0.571429 selected=True
• chore(deps): bump scikit-learn from 1.6.1 to 1.8.0 #4 LINKUSDT score=0.500000 selected=True
• chore(deps): bump google-github-actions/auth from 2 to 3 #5 AVAXUSDT score=0.500000 selected=True

Publish summary

• dry_run: False
• publish_enabled: True
• release_prefix: crypto-leader-rotation/releases/2026-05-01-core_major
• current_prefix: crypto-leader-rotation/current
• firestore target: strategy / CRYPTO_LEADER_ROTATION_LIVE_POOL

Validation

• ok: True
• manifest_present: True
• artifact_manifest_present: True
• age_days: 0

Errors

• none

Warnings

• none

Monthly Review

Monthly Review

Generated: 2026-05-01T07:27:57.988982+00:00

Current release status

• Status: ok
• As-of date: 2026-05-01
• Official profile: baseline_blended_rank
• Official version / mode: 2026-05-01-core_major / core_major
• Official pool size: 5
• Official symbols: TRXUSDT, TAOUSDT, DOGEUSDT, LINKUSDT, AVAXUSDT
• Source project: crypto-leader-rotation

Publish summary

• dry_run: False
• publish_enabled: True
• release_prefix: crypto-leader-rotation/releases/2026-05-01-core_major
• current_prefix: crypto-leader-rotation/current
• firestore target: strategy / CRYPTO_LEADER_ROTATION_LIVE_POOL

Track coverage

• official_baseline: releases=51 first=2021-05-31 last=2026-05-01 status=official_reference
• challenger_topk_60: releases=51 first=2021-05-31 last=2026-05-01 status=shadow_candidate

Warnings

• none

Operator checklist

1. Run make monthly-shadow-build before generating the extended shadow review package.
2. Confirm live_pool.json and release_manifest.json point to the same month; if generated, confirm track_summary.csv matches too.
3. Review warning lines before any manual publish or communication follow-up.
4. Keep the official baseline as the only production reference unless a separate governance process approves a change.

Telegram Preview

CryptoSnapshotPipelines monthly release
status: ok
as_of_date: 2026-05-01
official: profile=baseline_blended_rank version=2026-05-01-core_major mode=core_major pool_size=5
shadow: official_baseline last=2026-05-01 releases=51; challenger_topk_60 last=2026-05-01 releases=51
manifest: present dry_run=False
validation: ok=True manifest_present=True age_days=0
warnings: none

[Pigbibi]

Snapshot Audit Follow-up

Reviewed the 2026-05-01 monthly report input and the latest issue comments. There were no prior comments on this issue.

Review Summary

• The official pool is internally consistent with the release metadata: 2026-05-01-core_major, core_major, pool size 5, and symbols TRXUSDT, TAOUSDT, DOGEUSDT, LINKUSDT, AVAXUSDT all align with the published summary.
• Validation is clean: ok=True, manifest present, age_days=0, and no reported warnings or errors.
• The selected score spread is acceptable for a monthly Binance Spot mainstream leader snapshot. TRXUSDT is the clear leader at 1.000000; LINKUSDT and AVAXUSDT tie at the cutoff with 0.500000, which is worth monitoring but is not a release blocker.
• Shadow/challenger evidence is present this cycle: both official_baseline and challenger_topk_60 show 51 releases, first 2021-05-31, last 2026-05-01, with no warnings.
• Recommendation: keep baseline_blended_rank as the production reference. Do not change selector logic based on this single snapshot.

Highest-value Follow-up

The most useful next low-risk research comparison is a side-by-side official-vs-challenger performance/risk/turnover attribution for official_baseline and challenger_topk_60, using the same-cycle shadow outputs now available. Coverage exists; decision-grade optimization evidence still needs comparative metrics.

Code / Docs Follow-up

PR: #48

That PR tightened monthly review audit controls by requiring same-cycle shadow outputs before generating the monthly review briefing, preserving clean AI review rendering, and aligning README/runbook docs with the current monthly review automation.

Validation:

• GitHub CI test passed on PR Improve monthly review audit controls #48.
• Local targeted check: python3 -m pytest tests/test_monthly_review_briefing.py tests/test_render_monthly_ai_review.py tests/test_prepare_auto_optimization_pr.py -> 10 passed.

Merge note: no merge or auto-merge action was taken during this issue pass. PR #48 was already merged when this follow-up was processed.

[Pigbibi]

Closing after follow-up review. The May monthly report is internally consistent, validation is clean, same-cycle shadow/challenger coverage is present, and PR #48 already tightened the monthly review audit controls with passing CI. The review result was posted in this issue; no separate fix remains.

[Pigbibi]

Crypto Codex Audit

Verdict

Release package is not blocked. The monthly metadata, validation status, symbols, and shadow/challenger coverage in issue #47 are internally consistent. I found and fixed one low-risk reporting-format defect.

Findings

Low: Monthly AI review input duplicated embedded document titles, producing ## Release Status Summary followed by # Release Status Summary, and similarly for Monthly Review. The cause was scripts/run_monthly_report_bundle.py embedding full Markdown documents under wrapper headings without stripping their H1 titles.

Changes Made

• Updated scripts/run_monthly_report_bundle.py to strip only matching wrapped H1 headings before embedding the generated Markdown sections.
• Added focused assertions in tests/test_monthly_report_bundle.py to prevent the duplicate-heading regression.

Verification

• python -m pytest tests/test_monthly_report_bundle.py -> 1 passed
• python -m pytest tests/test_monthly_report_bundle.py tests/test_monthly_review_briefing.py tests/test_monthly_build_telegram.py -> 8 passed

Residual Risk

No strategy behavior, selector logic, allocation rules, generated data, secrets, release artifacts, or GitHub state were changed. Broader pandas/data-heavy release tests were not run because this fix is limited to monthly report text rendering and the VPS guidance favors bounded checks.

Created fix PR: #58