8b2e4121dd
forgejo-issue.py warns that a milestone title starting with a version token has everything after it dropped from the dashboard phase -- `0.2 Payments` displays as `0.2`. README.md was teaching exactly that form, and two adopted repos followed it: Closer-Couples and fruit-fall both carry version-first titles and lose their batch names on the card. PrivacyLLC-Web uses `Batch 05 — ...` and displays whole. The guidance now names the working form, and carries the comma rule the script also enforces: a comma breaks the `milestones=` filter and the card shows the wrong next action. WORK_CYCLE.md gains the trap the same script documents and no document did: the dashboard's next action is the NEWEST open issue in the current milestone, not the most severe -- severity labels have no influence at all. Filing a routine P2 into the active batch silently replaces what the project card shows. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| architecture | ||
| data | ||
| design | ||
| history | ||
| planning | ||
| qa | ||
| security | ||
| DOC_TRUST_MAP.md | ||
| TOOLS.md | ||
| WORK_CYCLE.md | ||