Checks README: a tracking issue that lives only in the tracker counts, and what that cannot catch (issue 436)

2026-10-11 02:07:01 +02:00
parent a5d1e0fbf6
commit d188941e73
1 changed files with 4 additions and 1 deletions
@@ -71,7 +71,10 @@ off — "until renamed", "left for later", "not decided here", "postponed", "fut
 change" — names the issue that tracks it, as tracking it ("tracked by issue N", or "issue N tracks"), in that
 paragraph or list item, or in a dated progressive insight that speaks about it: one in the same section, or one
 that quotes it. An issue cited for another reason tracks nothing, and one insight does not excuse every deferral
-in a record. A rejected option is not work put off and is not held, judged by its `##` section, so an option under a
+in a record. The tracking issue counts when it has a folder in `04-ISSUES/`, or when its number is above every
+folder's: since ADR 0275 an issue from 365 on lives only in the issue tracker, which a checkout cannot read, and the
+tracker hands out numbers in order (issue 436). A made-up number above the folders therefore passes; the reviewer
+checks that the issue exists, with `issue-tracker.get`. A rejected option is not work put off and is not held, judged by its `##` section, so an option under a
 `###` subheading of "Considered Options" is skipped too
 ([issue 354](../../04-ISSUES/354-a-decided-rename-was-never-scheduled-and-the-operator-believed-it-live/00-report.md):
 ADR 0244 deferred the code renames with no issue, and two days later the operator believed them done). Held to