Dashboard › craft › Distillation
639eb6fb-bf32-4771-b76c-9a8ad45e3452["lore_tm_v1_O9kzEFZ-9N2aMU0T0dAMMZTF8LrUbB4X4AFZi1RDeQ0","lore_tm_v1_5CKKEaQpzOSei4I557ZiSOLCNNC4WzPog1AoVjUwccE","lore_tm_v1_z3_VRlV9Gw5T8uQE71pbzgmWlBrp3EJ5_lfhzOKTDGQ","lore_tm_v1_KqDmO97z2BiAyv4zYBVQj8RmIqxDRtmNAE5AhhjlwRk"]
Date: Sep 8, 2026
.github/workflows/ci-poller.yml, .github/workflows/publish.yml, docs/publish-issue-format.md, scripts/generate-publish-issue-title-parser.js, src/modules/__tests__/publish-workflow.js, src/modules/publish-issue-title.js, src/modules/publish-issue-title.peggy, src/modules/release-revision.js, src/publish/inputs.js, src/publish/resolve-location.js, and src/publish/resolve-release-revision.js; untracked paths: src/publish/__tests__/ and src/publish/discover-location.js.Unexpected end of JSON input.src/modules/publish-issue-title.peggy:46 uses "/checks/"?, making the entire /checks/ suffix optional; generated src/modules/publish-issue-title.js:911-924 therefore accepts a bare commit URL and rejects /checks without a trailing slash, regressing the intended /checks/? contract. Existing coverage in src/modules/__tests__/release-revision.js:19-22 tests only /checks/.src/modules/publish-issue-title.peggy:58-61, generated src/modules/publish-issue-title.js:304-307, and src/modules/release-revision.js:3-10 only recognizes lines beginning - [View check runs](. Thus, an inline or blockquoted second check-runs link bypasses counting; a body containing two such links was accepted and returned the header SHA. Existing decoy coverage in src/modules/__tests__/release-revision.js:56-71 tests only a line-start duplicate.scripts/generate-publish-issue-title-parser.js:50-59 documentation-generation validation permits removal of the generated documentation block entirely: replace() leaves markerless documentation unchanged and the equality branch then skips verifying marker presence. Consequently, check:generated could pass when documentation lacks the canonical grammar.src/publish/discover-location.js:33-36 parses empty Craft workspace output with raw JSON parsing and throws Unexpected end of JSON input, rather than the required contextual discovery error. src/publish/__tests__/discover-location.js:37-47 covers invalid output {} only, not empty output.docs/publish-issue-format.md:93-94 documents Merge target as optional, while the canonical release-revision grammar in src/modules/publish-issue-title.peggy:42-46 requires a non-empty Merge target: line; src/modules/details-from-context.js:54-59 also extracts it as optional/defaults to "". An issue accepted by the documentation can therefore fail during release-revision resolution.latest; and .github/workflows/ci-poller.yml uses checkout v7 while retaining workflow_dispatch.DO-NOT-MERGE due to the 3 MUST-FIX and 2 MAJOR findings.