Wave 6 exit - the work package's general information

Five tasks, three probes, 156 new checks. Every wave-6 item persists, exports
and filters, and the rollup adds up at every level rather than only at the leaf.

Each task had one decision it had to make rather than inherit, and each is
recorded in wave-6.md because a later reader will otherwise read the behaviour
as an accident:

  T6.1  blanks sort LAST in both directions
  T6.2  priority sorts by escalation, not alphabetically
  T6.3  the stored value is the full path, not the node's own code
  T6.4  the unassigned group is shown, or the totals do not reconcile
  T6.5  a card has three states, so it needs three status lines

admin.js is byte-identical. A7's note about localization is the loudest "do not"
in the wave file and cards_check proves it two ways.

Screenshots re-captured at 390 and 1440 across all seven pages. One overflow,
the known creator@390 (BL-001), unchanged.

Carried forward unchanged: BL-010 (829 spacing/type literals - wave 6 re-laid-out
none of the pages carrying them), BL-018, BL-019. BL-018 has now cost three
separate probes a hand-seeded SOP; browser_check's fixture should adopt the
production {sop, state} shape when it is fixed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/reference/file-map.md

@@ -243,6 +243,26 @@ python tests/sections_check.py      # CR-006/CR-002/CR-016 — hidden, not delet
 python tests/validation_check.py    # S1 wizard — errors at the field, no dialogs 81 checks
 ```
 
+Wave 6 added three more:
+
+```bash
+python tests/generalinfo_check.py   # CR-001/CR-003 — P6 activity, priority     49 checks
+python tests/rollup_check.py        # CR-004/CR-018 — codes, and totals that add 63 checks
+python tests/cards_check.py         # A7 — card status, footer, localization    44 checks
+```
+
+**Two probes were re-pointed at `T6.5`, and the reason is worth carrying forward.**
+`aggregates_check.py` matched the launcher card's exact wording (`"SOP complete"`), and it
+also waited for the status line to be non-empty — which stopped meaning "the answer has
+arrived" once the card gained a line for the in-flight state too. Both assertions now match
+the ANSWER rather than the sentence, which is what that check was ever about. A probe that
+breaks on wording is a probe somebody edits carelessly the next time wording changes.
+
+**Windows consoles are cp1252.** Several probes print page text back in a failure message,
+and a glyph outside cp1252 (`✓`, `✕`, `→`) crashes the *reporter* instead of
+reporting the failure — losing the diagnosis, which is the only thing that run was for.
+The wave 5 and 6 probes route any page-derived text through an `ascii_()` helper.
+
 `pipeline_check.py` reads the dashboard's state out of the **iframe's DOM**, not its
 globals: `dashFilter` and `currentView` are declared with `let` in a classic script, so
 they are not properties of `window` and a cross-frame read of either comes back