check_milestone_cut.sh: exempt the release epic by its issue number from 06x-release-schedule.md §5, not by title/label match #3460

kind:code · follow-up to #3445 / #3455 · not started

Defect (measured at d79a6875b)

scripts/check_milestone_cut.sh exempts the train's release epic by label + title match: an issue labelled epic whose title literally starts with EPIC: release train <milestone> followed by end or whitespace (is_release_epic in the judge). It does not use the epic's issue number. That number is already recorded in docs/specifications/06x-release-schedule.md §5 (| 0.69.0 | #3080 | …, | 0.70.0 | #3081 | …).

Holes in the match:

• If the real epic is closed or moved and a look-alike issue (label epic, same title prefix) is open in the milestone, the look-alike is admitted and the gate PASSES.
• Two look-alikes are exit 2 (cannot judge), never exit 1 (named RED).

Fix

Exempt exactly the issue number that the 06x §5 row names for the milestone. A milestone with no §5 row exits 2. Every other open item is ordinary, however it is titled or labelled.

Exit: mutations RED

• A second issue titled like the epic ⇒ still RED (exit 1, the look-alike named).
• The real epic closed plus a look-alike open ⇒ RED.
• Exemption removed ⇒ the milestone's own epic reads RED.
• §5 row deleted ⇒ exit 2.