@celestia-island/hikari 0.55.127 → 0.55.130

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celestia-island/hikari",
-  "version": "0.55.127",
+  "version": "0.55.130",
   "private": false,
   "type": "module",
   "description": "Hikari Vue 3 component library — production-grade UI components based on shittim-chest design system",

package/src/components/HkBlockingToast.scss

@@ -93,6 +93,87 @@
   color: #fff;
 }
 
+// ── Actions on a tinted surface ─────────────────────────────────────
+// The card's surface IS the variant color, so the action row takes its
+// ink from that surface instead of leaking the global accent: a plain
+// primary button reads as a foreign brand on the tinted card (a pink
+// confirm on the teal info card under a pink-themed consumer), and the
+// danger confirm's own red dissolves into its red card. The confirm
+// inverts to a filled white control labeled in a deepened shade of the
+// variant color — the strongest move on every variant surface — and the
+// cancel quiets to a translucent outline in the card's own ink (the
+// house grammar for quiet controls on tinted toast surfaces).
+.hk-blocking-toast-info {
+  --hk-blocking-toast-ink: var(--hi-color-info, #6abed6);
+}
+
+.hk-blocking-toast-warning {
+  --hk-blocking-toast-ink: var(--hi-color-warning, #eed677);
+}
+
+.hk-blocking-toast-danger {
+  --hk-blocking-toast-ink: var(--hi-color-danger, #f85149);
+}
+
+/* The confirm arrives as .hk-btn-primary (info/warning cards) or
+   .hk-btn-danger (danger card) — both recolor to the same inverted
+   control. Labels darken the variant ink (55% toward black) so every
+   variant stays readable on the white fill; svg rides the label color
+   so a themed glyph ink can't wash out against it. */
+.hk-blocking-toast-actions .hk-btn-primary,
+.hk-blocking-toast-actions .hk-btn-danger {
+  background: #fff;
+  border-color: transparent;
+  color: color-mix(in srgb, var(--hk-blocking-toast-ink, #6abed6) 55%, #000);
+
+  svg {
+    color: inherit;
+  }
+}
+
+.hk-blocking-toast-actions .hk-btn-primary:hover:not(:disabled):not(:focus-visible),
+.hk-blocking-toast-actions .hk-btn-danger:hover:not(:disabled):not(:focus-visible) {
+  filter: none;
+  box-shadow: none;
+  background: rgb(255 255 255 / 88%);
+}
+
+.hk-blocking-toast-actions .hk-btn-primary:active:not(:disabled),
+.hk-blocking-toast-actions .hk-btn-danger:active:not(:disabled) {
+  filter: none;
+  background: rgb(255 255 255 / 78%);
+}
+
+/* The secondary cancel stops being a heavy surface block (it rendered
+   as a white pill competing with the confirm on the tinted card) and
+   picks up the quiet outline in the card's currentColor — white on
+   info/danger, near-black on warning — so it reads on every variant
+   without its own per-variant table. */
+.hk-blocking-toast-actions .hk-btn-secondary {
+  background: transparent;
+  border-color: color-mix(in srgb, currentColor 45%, transparent);
+  backdrop-filter: none;
+  color: inherit;
+}
+
+.hk-blocking-toast-actions .hk-btn-secondary:hover:not(:disabled) {
+  border-color: color-mix(in srgb, currentColor 70%, transparent);
+  background: color-mix(in srgb, currentColor 18%, transparent);
+}
+
+.hk-blocking-toast-actions .hk-btn-secondary:active:not(:disabled) {
+  filter: none;
+  background: color-mix(in srgb, currentColor 28%, transparent);
+}
+
+/* The keyboard ring follows the card ink too — the global primary ring
+   would leak the same foreign accent the fill just removed. */
+.hk-blocking-toast-actions .hk-btn:focus-visible {
+  box-shadow:
+    0 0 0 2px rgb(255 255 255 / 60%),
+    0 0 0 4px currentColor;
+}
+
 // Enter/leave mirrors the toast slide (settle, no bounce); leaving
 // cards go absolute so the remaining ones glide up (hk-toast pattern).
 .hk-blocking-toast-enter-active {

package/src/composables/useSurfaceContentHold.ts

@@ -18,8 +18,20 @@ import type { SurfacePhase } from "../runtime/surfaceMachine";
  * always plays over the content the user was actually looking at. Vue's
  * patch skips identical vnode references, so the held DOM is never
  * re-patched during the close; child components with their own store
- * subscriptions may still self-update (harmless — the failure mode under
- * repair is content VANISHING, not content ticking).
+ * subscriptions may still self-update.
+ *
+ * ⚠️ CONTRACT for bodies under this hold (the 2026-10-06 chest crash:
+ * `TypeError: Cannot read properties of null (reading 'content')` in a
+ * report window's close fold): a held child that subscribed to the body's
+ * reactive reads re-renders with the FROZEN slot closures, so any slot
+ * body that re-reads a live ref at invocation time sees the host's
+ * teardown null and throws. The "self-updates are harmless" claim the
+ * original comment made is wrong in exactly that case. Bodies must render
+ * a per-render SNAPSHOT of their nullable state (read it once in the
+ * render function, hand the captured value to every deferred closure) —
+ * never re-read the live ref inside a slot or callback the fold can
+ * re-run. (The failure mode under repair remains content VANISHING; a
+ * throwing deferred read is the second, sharper failure mode.)
  *
  * The hold releases the moment the surface leaves a closing phase: a
  * reopen interrupt (closing → openingFrom) serves live slots again, and

package/src/scale.scss

@@ -7,7 +7,7 @@
  * foundation) were normalized to the values the production composition
  * resolves to (chest: admin-tokens + foundation last). This file is the
  * upstream of styles/theme/scale.scss — edit here, then re-run
- * scripts/theme/sync-vendored.sh; do not hand-edit the vendored copy.
+ * scripts/theme/sync-vendored.py; do not hand-edit the vendored copy.
  */
 :root {
   /* Spacing (N px at the 16px root). */

package/src/styles/theme/scale.scss

@@ -9,7 +9,7 @@
  * foundation) were normalized to the values the production composition
  * resolves to (chest: admin-tokens + foundation last). This file is the
  * upstream of styles/theme/scale.scss — edit here, then re-run
- * scripts/theme/sync-vendored.sh; do not hand-edit the vendored copy.
+ * scripts/theme/sync-vendored.py; do not hand-edit the vendored copy.
  */
 :root {
   /* Spacing (N px at the 16px root). */

package/src/styles/vendoredSync.test.ts

@@ -16,7 +16,7 @@ import { describe, expect, it } from "vitest";
  *
  * The re-copy adds exactly one provenance header comment block; everything
  * after it must match the upstream byte-for-byte. Edit the UPSTREAM, then
- * re-run scripts/theme/sync-vendored.sh — never hand-edit the copies.
+ * re-run scripts/theme/sync-vendored.py — never hand-edit the copies.
  */
 
 const stylesDir = resolve(dirname(fileURLToPath(import.meta.url)));