feat(pipeline_status): register the Saturday-SF ReportCard state (v0.52.1)#97
Merged
Merged
Conversation
…52.1) The Director arc added a substantive ReportCard Task state to the Saturday SF (alpha-engine-data #367, invoking alpha-engine-evaluator:live to build the Report Card v2). The cross-repo invariant test_pipeline_status_registry_drift (run in alpha-engine-data + alpha-engine-dashboard) asserts every substantive SF Task state has a STATE_TO_ARCHIVE_PAGE entry — so data CI went red on the merged SF until ReportCard is registered here. Add ReportCard → ArchivePageRef(page="Report_Card", artifact_label="System Report Card") — deep-links page-25 to the new dashboard Report Card page. Bump 0.52.0 → 0.52.1 (auto-tag + publish on main push). Consumers (data, dashboard) re-pin to v0.52.1 to clear the drift. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
cipher813
added a commit
that referenced
this pull request
Jun 5, 2026
… page (v0.52.2) (#98) The Director Task state (added to the Saturday SF by data #370) had no STATE_TO_ARCHIVE_PAGE entry, so the dashboard pipeline-status registry-drift test fails on a full local checkout (page 25 renders a "⚠️ Registry drift" cell for it). lib #97 added ReportCard but not Director. Add the Director entry as an ArchivePageRef deep-linking the new Director_Plan console page (companion alpha-engine-dashboard Director-console-page PR). Mirrors the ReportCard entry. Bump 0.52.1 → 0.52.2 (auto-publishes on main push). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The Director arc added a substantive
ReportCardTask state to the Saturday SF (alpha-engine-data#367 — invokesalpha-engine-evaluator:liveto build the Report Card v2). The cross-repo invarianttest_pipeline_status_registry_drift(run in alpha-engine-data + alpha-engine-dashboard) asserts every substantive SF Task state has aSTATE_TO_ARCHIVE_PAGEentry — so data CI went red on its merged SF untilReportCardis registered here."ReportCard": ArchivePageRef(page="Report_Card", artifact_label="System Report Card")(deep-links page-25 to the new dashboard Report Card page).auto-tag.ymlcreatesv0.52.1+publish.ymlpublishes on merge.After merge
Consumers re-pin to
v0.52.1to clear the drift: alpha-engine-data (turns its registry-drift test green — the urgent one) and alpha-engine-dashboard (page-25 + its skip-in-CI test).Lib pipeline_status tests: 68 passed.
🤖 Generated with Claude Code