@ai-matrx/tap-target 0.1.2 → 0.2.1

package/CHANGELOG.md

@@ -1,5 +1,87 @@
 # Changelog
 
+## 0.2.1 — 2026-09-07
+
+**Census row 19i is now fully closed — the spinner stops being a coin flip.**
+`LoadingTapButton` wore core Tailwind's `animate-spin`. Core Tailwind, so it
+survived in all four current consumers and the defect was invisible; but a
+package cannot ship a class it does not define, and the first host without
+Tailwind's core animate utilities gets a spinner that stands still. That is not
+a missing flourish — it is a load-bearing lie, because a still spinner says the
+work has stopped, and there is no error anywhere to find it by. Exactly the
+class of host reliance `@ai-matrx/design-system@0.10.0`'s motion sweep closed
+for its own eleven primitives, and the last open half of the row that sweep
+left behind.
+
+**The fix imports; it does not copy.** This package has depended on
+`@ai-matrx/design-system` since 0.2.0, so the spinner now wears that package's
+`matrx-spin` — via its exported `MOTION_SPIN` constant, whose keyframe and rule
+ship in ITS `styles.css` and are asserted present in ITS packed tarball.
+Copying those four lines here would have created a second owner for one
+animation: the very twin the census row exists to kill. Under
+`prefers-reduced-motion` the shared rule slows the loop rather than stopping it,
+because a stopped spinner removes information rather than motion.
+
+**`src/styles.css` now `@import`s `@ai-matrx/design-system/styles.css`.** That
+sheet is a REQUIREMENT of this one, not a recommendation — half the spinner's
+truth lives there. `@ai-matrx/design-system` is a real `dependencies` entry, so
+the bare specifier resolves from a plain `npm install @ai-matrx/tap-target` with
+nothing else in the host's manifest, and a host that already imports the
+design-system sheet loses nothing (bundlers resolve both to one file). Any
+future rule in this sheet must go BELOW that `@import`.
+
+**The guard (`src/motion.test.tsx`), proven failing-then-passing.** A
+class-name assertion alone would have passed throughout the defect, so — like
+design-system's own motion guard — every check has two halves: the class
+reaches the DOM, AND a sheet that actually reaches the consumer defines a rule
+for it whose keyframe that same sheet declares. It also fails on ANY
+`animate-*` utility appearing in any source file or in the stylesheet (comments
+excluded, so the prose explaining the removal can name it), and on a
+`@keyframes matrx-spin` being copied back in here. Re-pointing the spinner at
+`animate-spin` and dropping the `@import` fails three tests by name.
+
+### Consumer action (C28)
+
+**None** — take the patch. No API change, no prop change, no geometry change.
+Hosts already importing `@ai-matrx/design-system/styles.css` see no difference
+at all; hosts that were not now get the spinner rule through
+`@ai-matrx/tap-target/styles.css`.
+
+## 0.2.0 — 2026-09-07
+
+**The tooltip moved out.** This package shipped a Tooltip family whose own file
+header said what it was: an inlined PORT of matrx-frontend's
+`components/ui/tooltip.tsx`, written because ~60 tap buttons need a tooltip and
+no shared package owned one. Four repos then adopted `TooltipProvider` from
+here — which made a button-geometry package the accidental owner of a
+design-system surface, while a second copy lived on in the biggest host.
+
+A tooltip is a design-system surface. `@ai-matrx/design-system@0.7.0` owns it
+now. This package takes design-system as an ordinary sibling dependency
+(`workspace:*` in the monorepo, `latest` outside), imports the Tooltip from it,
+and **re-exports nothing** — one implementation, one import path. `src/tooltip.tsx`
+is deleted. The sibling DAG already ordered design-system before tap-target, so
+this edge introduces no cycle; design-system publishes first.
+
+The design-system version also RESTORES the seam this copy had dropped: the
+content portals through `PortalContainerProvider`, so a tooltip inside a
+popped-out panel lands in the right document instead of always `document.body`.
+
+### Consumer action (C28)
+
+Anything importing `Tooltip`, `TooltipTrigger`, `TooltipContent` or
+`TooltipProvider` from `@ai-matrx/tap-target` must import them from
+`@ai-matrx/design-system` instead. Mechanical:
+
+```
+# in each consumer repo
+grep -rl '@ai-matrx/tap-target' --include='*.ts' --include='*.tsx' . \
+  | xargs grep -l 'Tooltip'
+```
+
+Nothing else changes — the tap buttons' own tooltip behaviour, props
+(`tooltip` / `tooltipSide` / `tooltipAlign`) and geometry are untouched.
+
 ## 0.1.1 — 2026-08-29
 
 - `mobileIconOnly` prop on `TapTargetButton` / `Transparent` / `Solid` /

package/README.md

@@ -34,6 +34,12 @@ nothing renders correctly without it:
 import "@ai-matrx/tap-target/styles.css";
 ```
 
+That one line is enough: since 0.2.1 this sheet `@import`s
+`@ai-matrx/design-system/styles.css`, which it REQUIRES — the loading button's
+spinner wears design-system's `matrx-spin`, whose keyframe is defined there
+(never `animate-spin`, a host utility this package cannot ship). If your app
+already imports the design-system sheet, nothing is duplicated.
+
 Tailwind users migrating from the in-repo Matrx copy can keep their existing
 `globals.css` `.matrx-tap-*` block until the C9 swap removes it — the rules are
 identical; just don't load both forever.