Dashboard › publish › Distillation
7a0360b4-cbc0-4a22-8a5b-9f7895e0b9c5["lore_tm_v1_4hkUm2oxSB2Q4TrjFJVvq5ktvwjGIU7RS2F9cXAF5u4","lore_tm_v1_HUlgwG_GnehZl1SjZ2JUOQIRdy20zI_JFpepBDuL1j4","lore_tm_v1_RRzW3FR9OwxfMTda5mssD1waI1LBZviVviH69yklwXs","lore_tm_v1_ZV-ksTxzSiMHcSR1D1JQIX-lP9abugzyTpnxhX5RLgg","lore_tm_v1_Mg9N3rPW5Da7ik7JXtziTOGuQHZPLPZW7hTL6H3mq_8","lore_tm_v1_fuY2zCFgA0jafEhPnnDWkGwve87U_NFkUChXu9vfqrk","lore_tm_v1_-VMoqOFwCUYESuFE_XnGTqHh01urdnh1K4YNHtNxYPw"]
Date: Aug 28, 2026
src/modules/__tests__/approval-attestation.js (90 lines). Existing Vitest tests import createApprovalAttestation, currentAcceptedEvent, hasApprovalAttestation, and parseApprovalAttestation from ../approval-attestation.js; verify latest accepted event selection (id: "200" over "100"), numeric GitHub event ID normalization (29503999078 → "29503999078"), trusted-comment author matching, rejection of stale/mismatched attestations, and malformed <!-- publish-approval not-base64 --> parsing to null.src/modules/approval-attestation.js; exact code changes were not shown in this segment.ci-ready labels and approval changes during CI handoff.src/modules/__tests__/approval-attestation.js; exact test changes were not shown in this segment.src/publish/record-ci-ready-attestation.js.src/publish/validate-approval-attestation.js; exact code changes were not shown in this segment.workflow_dispatch must always be allowed for manual recovery..github/workflows/ci-poller.yml lines 1–70. CI Status Poller runs every 5 minutes (cron: "*/5 * * * *") and supports workflow_dispatch with optional attempt input defaulting to "0"; check-ci runs on ubuntu-latest in production when vars.CI_POLLER_HAS_PENDING == 'true' || github.event_name == 'workflow_dispatch', with concurrency group ci-status-poller and cancel-in-progress: false. It checks out with actions/checkout@v6 and persist-credentials: false; creates sentry-internal-app and release-bot credentials using actions/create-github-app-token@v3; uses GH_TOKEN for publish-repo label changes and RELEASE_TOKEN for cross-repository API calls. The release-bot token is created with owner: getsentry because sentry-internal-app is not installed on some private repositories including sentry-xbox, sentry-playstation, sentry-switch, and service-registry.ci-ready; the publisher will require this proof in addition to the approval attestation.