docs: classify issue test taxonomy

docs/reviews/2026-08-18-r3-test-truth-ledger.md

@@ -788,3 +788,27 @@ Batch O verification:
 The 24 remaining elapsed-time methods retain their reviewed Batch H
 classification: cancellation fakes, intentional real-time protocol behavior,
 cooperative yields, bounded integration polling, or a positive timeout guard.
+
+## Batch Q issue-number taxonomy review
+
+The 47 `Issue###` files contain 155 attributed methods. They are not a hidden
+duplicate or source-freeze family: none reads production source text and none
+contains a direct timing wait. Twenty-nine methods are explicitly classified
+`Purpose=Diagnostic`; the other 126 are executable regression contracts.
+Ninety-four methods belong to the installed-DAT lane, overlapping both groups
+where retail assets are the evidence prerequisite.
+
+The issue prefix still has concrete navigation value. Every number maps to a
+named section in `docs/ISSUES.md`, and the descriptive suffix already exposes
+the owning behavior—for example `Issue334BspBoxCellMembershipTests` and
+`Issue345SteepSlopeGlideTests`. A 47-file mass rename would discard that direct
+evidence key, create large history churn, and would not make the individual
+contracts materially easier to understand.
+
+R3's recommendation is therefore to retain the current `Issue###` class/file
+prefixes. Continue correcting individual method names whose oracle overclaims,
+and keep diagnostic methods outside the release count, but do not re-home 126
+useful regressions merely to erase their provenance. If the issue archive is
+later split into component-owned records, a class-level `Issue` trait can
+preserve filtering before any component-based file rename. This recommendation
+remains a user approval item because it closes T-016 without code churn.