T9.9 - C4 + the backlog sweep: nine entries closed, each re-measured first

The colour half (C4, approved Aug 18 - "change them"):
- BL-004: the help centre's own 52-colour palette collapsed onto theme tokens
- BL-005: the JS-built dialogs (auth-guard, wp-format) and project-data's
  badges read tokens; the creator's categorical badge palette moved to
  theme-light as --wp-chart-1..10, read by computed style at boot; the print
  popup - a document with no stylesheet - inlines live token VALUES
- BL-008: the second brand blue (#2563d6) is deleted; .sop-inherited tints
  with THE blue at the same 7% alpha
- BL-009: the ninth amber (--wp-status-warning-text-alt) is deleted
- theme-light gained the two missing feedback tokens the consoles carried as
  literals (--wp-status-success-text / -error-text)
- NEW tests/color_check.py 4/4: zero hex literals outside theme-light.css,
  comments stripped (the BL-017 lesson), with the exceptions named in full
  (meta theme-color cannot resolve a var; rgba alphas are opacity recipes)

The correctness half, each re-measured before touching, as the task ordered:
- BL-011 STILL REPRODUCED: the sync badge mounted on the first async sync
  event; its holder now mounts at DOMContentLoaded, so the three overlays land
  in script order deterministically
- BL-012 fixed and MEASURED: baseline_shots freezes Date and Math.random per
  document; two consecutive admin captures came back byte-identical
- BL-016 fixed: a step-less wizard URL is step 1; stepper_check's deliberately
  wrong pin flipped with the fix, exactly as the entry planned
- BL-018 fixed both halves: the false-complete write now requires the
  {sop,state} production shape, and browser_check.seed writes that shape -
  which un-detoured four probes' creators from the SOP gate. stepper_check
  re-pointed at projB (no SOP) because its premise is a wizard someone is
  STARTING, and projA now legitimately restores a finished one.
- BL-019 fixed: a stored cost code that left COST_CODES is kept as an option
  (the gov_wosize pattern), so opening a package no longer blanks its record
- hold_check's AST sweep refined in passing detection: it flagged T8.3's
  notification-row .status as a release transition; it now reads wp.status only

Every wave-9-pointing backlog entry is closed with its measurement recorded.

Verification (each probe run alone): color_check 4/4, stepper_check 71/71,
validation_check 77/77, url_state_check 23/23, autosave_check 34/34,
a11y_check 22/22, launcher_check 58/58, aggregates_check 16/16,
kitting_check 26/26, hold_check 50/50, mobile_check 24/24, frame_check 38/38,
sections_check 95/95, form_structure_check 50/51 (BL-022's question).

Items: C4, BL-004, BL-005, BL-008, BL-009, BL-011, BL-012, BL-016, BL-018, BL-019

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

html/theme-light.css

@@ -143,11 +143,8 @@
   --wp-status-error-bg: #fff1f1;
   --wp-status-warning-bg: #fdf6dd;
   --wp-status-warning-text: #8e6a00;
-  /* Four points from --wp-status-warning-text and doing the same job, on the
-     field view's warn pill. Almost certainly a typo rather than a decision, but
-     merging it moves a rendered colour, so T3.2 names it and T3.5 merges it.
-     BL-009 / docs/reference/tokens.md section 8-K. */
-  --wp-status-warning-text-alt: #8a6d00;
+  /* BL-009, CLOSED at T9.9 (C4): the ninth amber (--wp-status-warning-text-alt,
+     #8a6d00, four points from this one) is deleted; its consumers use this. */
   /* Carbon green-70. The value is Carbon, the role is not — Carbon has no
      "hover for a green fill", because green is not one of its action colours.
      Declared in no sheet today; written raw in five places. */
@@ -321,11 +318,22 @@
   --wp-btn-danger-fill-bg: var(--cds-support-error);
   --wp-btn-danger-fill-fg: var(--cds-text-on-color);
 
-  /* -- the second blue -------------------------------------------------------
-     #2563d6, not #0f62fe. Fills .sop-inherited — every field a work package
-     inherited from its SOP — at 7% alpha, which is why nobody has noticed a
-     second brand blue. Named here so it is visible; swapped at T3.5 (BL-008). */
-  --wp-sop-inherited-bg: rgba(37, 99, 214, .07);
+  /* BL-008, CLOSED at T9.9 (C4, approved Aug 18): the second brand blue is
+     gone. .sop-inherited now tints with THE blue at the same 7% alpha. */
+  --wp-sop-inherited-bg: rgba(15, 98, 254, .07);
+
+  /* The console feedback trio's success text (auth-guard / project-data /
+     wp-format carried it as a literal until C4). */
+  --wp-status-success-text: #0e6027;
+  --wp-status-error-text: #a2191f;
+
+  /* The categorical badge palette (the creator's navigator). Data-vis colours,
+     not UI states - named here because here is the only place a colour value
+     may exist (C4); the app reads them by computed style at boot. */
+  --wp-chart-1: #0f62fe;  --wp-chart-2: #8a3ffc;  --wp-chart-3: #007d79;
+  --wp-chart-4: #d02670;  --wp-chart-5: #ba4e00;  --wp-chart-6: #1192e8;
+  --wp-chart-7: #198038;  --wp-chart-8: #a56eff;  --wp-chart-9: #9f1853;
+  --wp-chart-10: #005d5d;
 }
 
 /* Typography */