@7365admin1/layer-common 3.2.2-staging.167 → 3.2.2-staging.168

package/assets/css/screens.css

@@ -183,9 +183,28 @@
  * appear on 35 files across the layer and eleven applications.
  *
  * `--muted` is the design's own secondary ink and is a token, so it follows
- * the theme: 4.77:1 light, 4.71:1 dark on the same surfaces. Redirected here,
- * once, rather than renamed at 35 call sites - the layer's stylesheet ships to
- * every application, so the class keeps working and simply reads correctly.
+ * the theme. Redirected here, once, rather than renamed at 35 call sites - the
+ * layer's stylesheet ships to every application, so the class keeps working.
+ *
+ * THE READING THIS COMMENT USED TO CLAIM IS NO LONGER TRUE, and the correction
+ * matters because it inverts the justification above.
+ *
+ * It said "4.77:1 light, 4.71:1 dark". That was measured when `--muted` was
+ * `#6b7079` - one of the six values darkened on 2026-08-13 to clear AA. The
+ * owner REVERSED that on 2026-08-14 in favour of 100% design fidelity, and
+ * `--muted` went back to the handoff's `#8b8f98`. Re-measured on the current
+ * token, alpha composited:
+ *
+ *     --muted on a card   3.24:1   (the old #7e7e7e read 4.06:1)
+ *     --muted on the page 2.99:1   - below even the 3.0 large-text floor
+ *
+ * So on the LIGHT theme this redirect is now a DOWNGRADE for the ~5 files that
+ * still use the class, not the improvement the original comment describes. It
+ * is left in place deliberately: `#7e7e7e` was a fixed grey that ignored the
+ * theme entirely and read 4.10:1 on dark where `--muted` reads 4.93:1, so
+ * reverting would trade a light-theme gain for a dark-theme loss. Which way
+ * this should go is a PALETTE decision for the owner, not a per-class one -
+ * see `utils/theme-aa-ledger.ts`, which pins every one of these readings.
  */
 .text-fontgray {
   color: var(--muted) !important;

package/package.json

@@ -2,7 +2,7 @@
   "name": "@7365admin1/layer-common",
   "license": "MIT",
   "type": "module",
-  "version": "3.2.2-staging.167",
+  "version": "3.2.2-staging.168",
   "author": "7365admin1",
   "main": "./nuxt.config.ts",
   "//files": "What a consumer extending this layer actually loads. Without this npm ships the whole working tree - the changesets, the CI workflows, the render harness in tools/ and any scratch directory that happened to exist at publish time. Nuxt resolves a layer by directory, so every runtime directory below has to stay listed; adding a new top-level runtime directory means adding it here too.",