Dashboard › publish › Distillation
636a67a1-71b7-45b9-9e9e-d734930b4559["lore_tm_v1_lSYcrR2_XIzC_sXF1ZU-HOHrBhBBw_-RRoNYLql2dJI","lore_tm_v1_VOz7zzlr_29cPQNZnslsLgJD1dCqZ0Ukf1f7s9Da47k","lore_tm_v1_U-tsTizywCoq9ODtuQPelMx_OLeiGgx1iAicRt6cLVc","lore_tm_v1_x8dQaEK2aSIxD3qJFacpIniEEFCRpoYhyeDz3Qfz4i4","lore_tm_v1_fo-_9NtJskSDVdMcQw15zo5fV22MwqDLu_wUnIIkrRw","lore_tm_v1_ASnz0g5AAh1SXOKLd5ufX88WJEpwhQFfPXiIT7wvNik","lore_tm_v1_m9olr8tYP2SnaxJaDDPJqdTr9wSSaO499RCpD08heIc","lore_tm_v1_DjzI_95JpIsjHcm697fZPZqWdWr9HTKgl33H8-yvOmQ","lore_tm_v1_B5_F3mjtl9JbT2i9N8LC7fX7L0pAU4saQ89syrrd5_c","lore_tm_v1_T0Sh62s-3X-_6mIHAPlnbO0ZwrOQnSq07lTWF-SCLAA","lore_tm_v1_KR64zRRlysFmyvrGzH4HWZjCZhrbXSUM2OK6EYf4F9w","lore_tm_v1_gXplzeQ5K0tAdTGUHsAu4vkfBpBiUSBCK5wvMBdMroY","lore_tm_v1_2NcJDNOs-b67j_cmhcQ30lN5lSjhilM-w4wvM3_9gfQ","lore_tm_v1_J8_i7OSwPolxB022ek-ihw3XeZMWMQ39YRczOesFjIk","lore_tm_v1_Cha2u-nR0cKEEpc2-Ij1HwwAqjgBmq7NhNFgSSiKCIM","lore_tm_v1_7j5yTh8yDYhZXzpLW5jn9Jjan-tBRtocJ99PMqsoyEg","lore_tm_v1_ysKQtpD7JTiAQ9kfuLVTDhvr4ETWcKsSHAumLNobCF8","lore_tm_v1_18Cp9IhVOKm2FrhVI_9HfegJJUq7lyi4FsQq4wg8rS0","lore_tm_v1_VpR_Cn98I2ZxjRv7QOXdrLJPCuaucumi9BZSe-kXaLA","lore_tm_v1_OPoINXfbuddNPOs2hVOAMfm7z54S3zwNKY9GQ1oF9JY","lore_tm_v1_KIC4_lxthLspDiXiJo3y4f1oVjHItm3rnZoaXAt8C7E","lore_tm_v1_b8PqOiHvKbm70zzbLVEvzSrU2XV65ZiM7RkUvVJ_CdI","lore_tm_v1_fsuDvasA_BcKLQS82_YJGlz_olDoNVCl6-p6rrXJ3UM","lore_tm_v1_l4LMSOnfG3jawp-qTFLf7oRkPdu6Q5-9IxXZ4fDdcs0","lore_tm_v1_hlwejDCKooA_r6U8PBXI-RUKJZ79CTMWoQBQF_mbc-o","lore_tm_v1_-HkW1gA8fXKV-j0DvwHKH7YjgnDvFsBo5x1zGRxIjD8","lore_tm_v1_x9OS1_L8qNrlm6PgeEiPlLvbs7fDuKBln2hEptR6cO0"]
ci-ready label.continue-on-error: true on the Trigger CI poller dispatch step in .github/workflows/publish.yml..github/workflows/publish.yml has a best-effort Reconcile publish issue step (if: always(), continue-on-error: true) before optional reporting and an authoritative Verify publish issue reconciliation step (if: always(), no continue-on-error) afterward; both remove accepted, ci-pending, and ci-ready, while the success branch also closes the issue.accepted cleanup from the earlier best-effort reconciliation block instead of the authoritative final block because .github/workflows/publish.yml contains repeated reconciliation commands. The mistake was detected before testing, reverted, and replaced with a mutation anchored specifically to Verify publish issue reconciliation.yarn vitest run src/publish/__tests__/publish-workflow.js -t 'reconciles authorization without Node' --printConsoleTrace failed as intended under Vitest v4.1.0: 1 test file failed; 5 tests total; 1 failed and 4 skipped; test duration 37ms, total duration 525ms; exit code 1.src/publish/__tests__/publish-workflow.js:94: the Verify publish issue reconciliation section no longer contained --remove-label "accepted" after that command was removed from both success and failure branches.reconciles authorization without Node before and after terminal reporting regression enforces dependency-free authorization cleanup in the final authoritative reconciler; restored --remove-label "accepted" in .github/workflows/publish.yml.src/publish/post-result.js: main() defaults status to process.argv.slice(2)[0], parses process.env.PUBLISH_ARGS when present, falls back to {} and warns Could not parse publish inputs; reporting without them on malformed JSON, then calls report({ context, octokit, inputs, status }).src/publish/__tests__/publish-workflow.js requiring exactly one always() terminal reporter whose mutually exclusive mapping derives from steps.publish.outcome: success → success, cancelled → cancelled, and every other outcome → failure.yarn vitest run src/publish/__tests__/publish-workflow.js -t 'reports exactly one terminal status' --printConsoleTrace failed as intended under Vitest v4.1.0: 1 test file failed; 6 tests total; 1 failed and 5 skipped; test duration 16ms, total duration 268ms; exit code 1.src/publish/__tests__/publish-workflow.js:109 because .github/workflows/publish.yml had 3 separate Report publish result steps rather than exactly 1; the existing independent predicates could overlap under cancellation..github/workflows/publish.yml with one Report publish result step using if: always() and continue-on-error: true. Its shell case "${{ steps.publish.outcome }}" in maps success) status=success ;;, cancelled) status=cancelled ;;, and *) status=failure ;;, then runs node .__publish__/src/publish/post-result.js "$status".yarn vitest run src/publish/__tests__/publish-workflow.js src/publish/__tests__/post-result.js src/modules/__tests__/process-end-state.js src/modules/__tests__/ci-poller-workflow.js --printConsoleTrace passed under Vitest v4.1.0: 4 test files passed; 27 tests passed; test duration 2.13s, total duration 2.54s; Yarn completed in 3.17s..github/workflows/publish.yml from cancelled) status=cancelled ;; to cancelled) status=failure ;;.yarn vitest run src/publish/__tests__/publish-workflow.js -t 'reports exactly one terminal status' --printConsoleTrace failed as intended under Vitest v4.1.0: 1 test file failed; 6 tests total; 1 failed and 5 skipped; test duration 20ms, total duration 309ms; exit code 1.src/publish/__tests__/publish-workflow.js:113: expected cancelled) status=cancelled ;; but received cancelled) status=failure ;;, proving the regression directly detects the terminal-status policy change.cancelled) status=cancelled ;; in .github/workflows/publish.yml.