Dev Tracker

Every confirmed issue / risk / debt / improvement is logged as a permanent QRS-### id with the full field set and a status lifecycle. Log-after-confirmation, never fix-and-forget.

Delivery observations live separately. Per-request notes on how work got delivered — what went well, what cost time, what was avoidable — are in Delivery Log, not here. This page is for defects, debt and decisions; mixing the two would mean a search for open bugs returned retrospectives (QRS-241).

Lifecycle

Rules

• Permanent id. QRS-### never gets reused or renumbered.
• Reference the id in commits that touch the issue.
• Groom every session/PR — status stays current.
• Categories: bug · debt · risk · improvement.

Where the tracker lives

Known Issues in this portal is the tracker — authoritative, not a staging area. There is no separate system, and waiting for one is what left ~170 confirmed items unnumbered until 2026-07-26.

Every item carries a permanent QRS-###. Ids are allocated from the next free id banner at the top of the tracker page — take it, then bump it in the same edit. Ids are never renumbered, reused or reassigned: they are referenced from commits, ADRs, READMEs and code comments, so a renumber silently invalidates all of those. Numbering is document order as of the bulk assignment, so it is neither chronological nor a priority ranking.

An id is an identity, not a status. Items still awaiting reproduction live in the tracker's Candidate findings — … sections and keep their id when promoted — confirmation is never signalled by withholding a number.

Pre-baseline findings additionally staged in known-issues-pending-tracker.md (historical).