@eduardoalvarez/arrecife 0.11.0 → 0.12.1

package/CHANGELOG.md

@@ -1,5 +1,38 @@
 # Changelog
 
+## [0.12.1](https://github.com/Proskynete/arrecife/compare/v0.12.0...v0.12.1) (2026-09-17)
+
+
+### 🐛 Correcciones
+
+* **components:** the footer signature is a column, so the credit stops pushing the icons ([6760744](https://github.com/Proskynete/arrecife/commit/67607443882b65fae8c7166554075e0ca7b9fe10))
+
+
+### 📚 Documentación
+
+* § 64, the signature is a column of its own ([6be8d1e](https://github.com/Proskynete/arrecife/commit/6be8d1e6cfc8a04bc3c999f672da3cb0d896f4d7))
+
+## [0.12.0](https://github.com/Proskynete/arrecife/compare/v0.11.0...v0.12.0) (2026-09-12)
+
+
+### 🚀 Novedades
+
+* **components:** the footer can credit the library, and it is off by default ([9b80bd8](https://github.com/Proskynete/arrecife/commit/9b80bd80dc2bc1d4637a132e3b3b9dfbc254f653))
+* **storybook:** the site wears the projects' mark and prints its version ([4c36b94](https://github.com/Proskynete/arrecife/commit/4c36b94d31d7353982eaa58ab75da2b309d972ef))
+
+
+### 🐛 Correcciones
+
+* **storybook:** the docs page stops showing the first story twice ([66f0016](https://github.com/Proskynete/arrecife/commit/66f00163ee6b1f5feb111022762928db112b709e))
+* **tokens:** emit the whole token set, so a var() read from JS resolves ([68836c8](https://github.com/Proskynete/arrecife/commit/68836c861a6a80d74bd6d23c279bfc05978626dc))
+
+
+### 📚 Documentación
+
+* one file per decision, so a reference stops carrying a version ([1deda8e](https://github.com/Proskynete/arrecife/commit/1deda8e3f09585856741e23bceebf5d18e5b5336))
+* **readme:** [@theme](https://github.com/theme) static, builtWith, and how a decision is cited ([ded6f2c](https://github.com/Proskynete/arrecife/commit/ded6f2ca6cc32c4a6746ad66417afa29f66b881d))
+* three decisions, and two of them are about what the library says of itself ([c52c89f](https://github.com/Proskynete/arrecife/commit/c52c89f0507d99bb3886d412e91fc11922debcd4))
+
 ## [0.11.0](https://github.com/Proskynete/arrecife/compare/v0.10.0...v0.11.0) (2026-09-11)
 
 

package/README.md

@@ -16,7 +16,10 @@ in a project with a `#E05252` that this README has declared wrong for months, an
 nobody saw it because the document was not greppable from the code.
 
 `docs/decisions/` is the other half: the points where the code and the document
-do not say the same thing, each with its resolution and its reason.
+do not say the same thing, each with its resolution and its reason. One file per
+decision, named for its number — `045-signature-halo.md` — so a «§ 45» written
+in a comment, a commit or a PR resolves by sorting the folder, and no reference
+has to carry a version.
 
 ## The two documents for agents
 
@@ -52,6 +55,16 @@ One source, `src/tokens/tokens.ts`. One generated output,
 `scripts/build-tokens.mjs`; it is not edited by hand and it is regenerated on
 every build.
 
+The block is `@theme static`, so **every token reaches `:root` whether or not a
+class asks for it** — you can read any of them with `var(--color-…)` from your
+own JavaScript or an inline style and it will be there. That is one word and it
+is a bug fix: Tailwind v4 emits a theme variable only when some generated
+utility uses one, and the four `--color-series-*` are read by `seriesColor()`
+through `var()` and requested by no class anywhere, so they were being dropped
+as unused and the charts drew black on a dark page with nothing erroring. It
+costs +234 B gzipped for a project using the system's whole vocabulary, and the
+ceiling is the token set. See `docs/decisions/` § 61.
+
 Phase 0 decision: **v4 only**. The portfolio (`eduardoalvarez.dev`) migrates from
 Tailwind v3 to v4 before consuming Arrecife. If that migration slips, publishing
 the v3 preset again is one more emitter in `build-tokens.mjs` reading the same
@@ -404,7 +417,7 @@ now draws Phosphor through `astro-icon` and its own docstring lists the divergen
 «every icon on the page — the six in the cards and the four here — is then one set
 at one weight». `eduardoalvarez.dev` did the same in `site-footer.tsx`. Two
 consumers walking away from a subpath built for them is the library being out of
-step, not the consumers. See `docs/decisions/0.10.md` § 51.
+step, not the consumers. See `docs/decisions/` § 51.
 
 **In a Next Server Component, take the glyph from `@phosphor-icons/react/ssr`.**
 `./icons` carries no `"use client"` on purpose, so an icon renders on the server
@@ -456,7 +469,7 @@ stroke` story shows the bars so the claim can be checked instead of believed.
 `glyphs.tsx` drew at 0.109em — three quarters heavier than both — and 0.7.0
 measured it, said so and left it alone, because aligning it restyles every
 primitive in the library. 0.10.0 is that change: the file is gone and there is
-one line in the system. See `docs/decisions/0.10.md` § 51.
+one line in the system. See `docs/decisions/` § 51.
 
 **The weight is an axis with three values, and `tone` is how you name them.**
 `weight` is not a prop: Phosphor ships six and this system reads three, because
@@ -474,7 +487,7 @@ one channel WCAG 1.4.1 says may not carry meaning** — the fill is the second
 channel, and it is the one that survives a forced-colours mode where the biolume
 does not. `quiet` is the opposite problem: in a metadata row the icon is not the
 point of the line, and at `regular` it draws as heavy as the date beside it.
-`docs/decisions/0.7.md` § 35 has the rest.
+`docs/decisions/` § 35 has the rest.
 
 `@phosphor-icons/react` is an **optional** peer dependency on its own subpath, by
 the same rule as `./form` and `./chart`: two of the five projects use no icons and
@@ -586,12 +599,19 @@ collision is deliberate: what they replace is not an import, it is sixty lines o
 composition — a `linearGradient` with a hardcoded id, a `CartesianGrid
 vertical={false}`, two axes with the line and the tick off, a `type="natural"`
 and a `strokeWidth` — which `cursos` wrote four times, once per chart. None of
-that is a decision the project made. See `docs/decisions/0.8.md` § 43.
+that is a decision the project made. See `docs/decisions/` § 43.
 
 A chart of a quantity with a ceiling passes it: `valueMax={100}` on a percentage.
 Without it the value axis ends at the largest datum, and a horizontal ranking —
 whose value axis is hidden — draws a course watched to 40 % as a full bar. See
-`docs/decisions/0.11.md` § 58.
+`docs/decisions/` § 58.
+
+`seriesColor(i)` returns `var(--color-series-N)` and not a hexadecimal, so the
+palette follows the mode instead of freezing to whichever one was live when the
+chart mounted. **Do not add a fallback to it**: the variable is always in
+`:root`, because the token block is `@theme static` for exactly this reason. On a
+version before that fix the `var()` resolved to nothing and the bars came out
+black — see `docs/decisions/` § 61.
 
 `check:exports` verifies that the five portable ones — `./tokens`, `./theme`,
 `./variants`, `./og` and `./shiki` — bring no React into the published `dist/`,
@@ -662,7 +682,7 @@ cannot see: axe does not evaluate text over a gradient, so both modes passed it.
 
 The light blocks now sweep between `background` and `surface` and never touch
 `surfaceRaised`, so the darkest point of either one is the page itself — a token
-that passes on the page passes at every point of the sweep. `docs/decisions/0.6.md` § 9 has the measurements, including the two other things the first composition
+that passes on the page passes at every point of the sweep. `docs/decisions/` § 9 has the measurements, including the two other things the first composition
 got wrong.
 
 ### The third correction: a semantic color is not a text color over its own tint
@@ -861,7 +881,7 @@ run summary.
   `SidebarNav` was on that list and came off it in 0.8.0. It met the rule below
   on the identity half and never on the consumer half: the two admin projects it
   was built for each wrote their own and never imported it. See
-  `docs/decisions/0.8.md` § 48.
+  `docs/decisions/` § 48.
 
   The criterion for deciding what gets in is still the same: **it encodes an
   identity rule, it has two or more consumers, and it drags in no project
@@ -902,7 +922,7 @@ about as library pieces. They get in anyway: the CLI aesthetic — the bar's
   optional peer on `./icons` so the set a project chooses is drawn at the system's
   weight; and 0.10.0 deleted `glyphs.tsx` and `./social` and made Phosphor
   required, because a library drawing in three hands cannot say which one is
-  right. See «The social icons are yours too» above and `docs/decisions/0.10.md`
+  right. See «The social icons are yours too» above and `docs/decisions/`
   § 51. What survives verbatim is the part that was always the real rule: the
   icons are the project's, the LINE is the system's. The rest of this bullet is
   the 0.7.0 argument, kept because it is what the reversal was measured against:
@@ -939,7 +959,7 @@ about as library pieces. They get in anyway: the CLI aesthetic — the bar's
   than width failed axe on `scrollable-region-focusable` immediately. It is
   unconditional, because whether a table overflows depends on the viewport and
   the only alternative is a ResizeObserver on every table in the system. See
-  `docs/decisions/0.8.md` § 39.
+  `docs/decisions/` § 39.
 
 ### The syntax palette
 
@@ -1056,7 +1076,7 @@ On a site that switches theme, `background="auto"` renders both and the `light:`
 variant shows the one that reads, so no call site has to know which theme is on.
 A background that does not follow the theme — a dark panel on a light page —
 still names itself: `auto` reads the page, not the panel. See
-`docs/decisions/0.11.md` § 60.
+`docs/decisions/` § 60.
 
 **Rule 5 as API.** The wordmark comes from `naming.wordmark` and always reads
 «Eduardo Álvarez». There is no prop that changes that text, and Tiburoncín never
@@ -1133,7 +1153,7 @@ spatial continuity. A sixth lands on that or it does not exist.
 The bar is 2px and not a block because a halo needs something thin to radiate
 from, the colour is `var(--color-accent)` so it follows the mode, and
 `motion-safe` is the one thing not copied from `cursos` — whose span animates
-regardless of the setting. See `docs/decisions/0.8.md` § 45, and § 23 for the entry
+regardless of the setting. See `docs/decisions/` § 45, and § 23 for the entry
 it reverses.
 
 ### The second motion exception
@@ -1180,7 +1200,7 @@ text, and `surfaceRaised` is where a toolbar lives.
 `destructiveOutline` fills on hover, and that is a declared exception to
 «secondary is never filled» — a destructive that looks identical to a secondary
 until you read it is the problem the variant exists to fix. See
-`docs/decisions/0.6.md` § 21.
+`docs/decisions/` § 21.
 
 ### `icon-sm`, for the one admin app
 
@@ -1191,7 +1211,7 @@ three actions per table row, and at 42 the row grows with them.
 `size="icon-sm"` is 32×32, and it is 32 and not the 28 that project actually had:
 32 is `sm`'s height, so a dense icon button lines up with a small text button and
 a toolbar mixing the two stays on one baseline. It does not replace `icon` — a
-page's primary action stays at 42. See `docs/decisions/0.6.md` § 22.
+page's primary action stays at 42. See `docs/decisions/` § 22.
 
 ### The theme script, and the mode a site already decided
 

package/dist/brand/index.cjs

@@ -75,7 +75,7 @@ var typeScale = {
    * (plankton 5.57:1 over abyss), which is the part that is not negotiable.
    *
    * At 13 the three badge families grew past the size of a small button and
-   * outweighed the title they accompany. See `docs/decisions/`.
+   * outweighed the title they accompany. See `docs/decisions/` § 10.
    */
   chip: { family: "mono", size: 11.5, lineHeight: 1.4, weight: 400 },
   /**
@@ -121,7 +121,7 @@ var control = {
    * baseline; 28 would have been a fifth height that matches nothing.
    *
    * It does not replace `icon`. A page's primary action stays at 42; this is for
-   * a row of a table. See `docs/decisions/0.6.md` § 22.
+   * a row of a table. See `docs/decisions/` § 22.
    */
   iconSm: 32
 };

package/dist/brand/index.d.cts

@@ -35,7 +35,7 @@ type IsotypeProps = Omit<ComponentPropsWithoutRef<'img'>, 'src' | 'alt'> & {
  * server does not know the theme, and a fin picked in JavaScript would be wrong
  * on the first paint half the time. `cursos` had written exactly this by hand
  * after a surface changed mode and its fin vanished — not looked wrong: vanished,
- * with no error and no gap in the layout. See `docs/decisions/0.11.md` § 60.
+ * with no error and no gap in the layout. See `docs/decisions/` § 60.
  *
  * Dark is the system default, so the foam fin is the one shown unless
  * `data-theme="light"` says otherwise, and the two-blue one hides everywhere

package/dist/brand/index.d.ts

@@ -35,7 +35,7 @@ type IsotypeProps = Omit<ComponentPropsWithoutRef<'img'>, 'src' | 'alt'> & {
  * server does not know the theme, and a fin picked in JavaScript would be wrong
  * on the first paint half the time. `cursos` had written exactly this by hand
  * after a surface changed mode and its fin vanished — not looked wrong: vanished,
- * with no error and no gap in the layout. See `docs/decisions/0.11.md` § 60.
+ * with no error and no gap in the layout. See `docs/decisions/` § 60.
  *
  * Dark is the system default, so the foam fin is the one shown unless
  * `data-theme="light"` says otherwise, and the two-blue one hides everywhere

package/dist/brand/index.js

@@ -1,5 +1,5 @@
 'use client';
-export { Isotype, Logo, Mascot, MascotFace } from '../chunk-RKGKO2TW.js';
-import '../chunk-FAAGZG7A.js';
+export { Isotype, Logo, Mascot, MascotFace } from '../chunk-BRDTB44R.js';
+import '../chunk-TMUGT3Y3.js';
 export { ASSETS_PATH, faceList, faceUsage, faces, fins, poseList, poses } from '../chunk-CKRSQPTX.js';
-import '../chunk-FGFNK72B.js';
+import '../chunk-5YWGOFDX.js';

package/dist/chart/index.cjs

@@ -46,7 +46,7 @@ var typeScale = {
    * (plankton 5.57:1 over abyss), which is the part that is not negotiable.
    *
    * At 13 the three badge families grew past the size of a small button and
-   * outweighed the title they accompany. See `docs/decisions/`.
+   * outweighed the title they accompany. See `docs/decisions/` § 10.
    */
   chip: { family: "mono", size: 11.5, lineHeight: 1.4, weight: 400 },
   /**
@@ -92,7 +92,7 @@ var control = {
    * baseline; 28 would have been a fifth height that matches nothing.
    *
    * It does not replace `icon`. A page's primary action stays at 42; this is for
-   * a row of a table. See `docs/decisions/0.6.md` § 22.
+   * a row of a table. See `docs/decisions/` § 22.
    */
   iconSm: 32
 };

package/dist/chart/index.d.cts

@@ -29,7 +29,7 @@ import { Legend, Tooltip } from 'recharts';
  * What IS published, since this version, are three CHART TYPES on top of that
  * chassis: `AreaChart`, `BarChart` and `LineChart`. They are not wrappers over
  * Recharts' components of the same name — they take `data`, `series` and `xKey`
- * and draw the whole thing. See `docs/decisions/0.8.md` § 43 for why the names
+ * and draw the whole thing. See `docs/decisions/` § 43 for why the names
  * collide on purpose.
  */
 /**
@@ -175,7 +175,7 @@ type SeriesChartProps = Omit<ChartContainerProps, 'children'> & {
      * `2026-07-15` repeated thirty times, overlapping into a grey band.
      *
      * The library imposes no format: a date key can be a day, a month or a course
-     * name, and only the project knows which. See `docs/decisions/0.9.md` § 50.
+     * name, and only the project knows which. See `docs/decisions/` § 50.
      */
     xTickFormatter?: ((value: unknown) => string) | undefined;
     /**
@@ -200,7 +200,7 @@ type SeriesChartProps = Omit<ChartContainerProps, 'children'> & {
      * The bottom is always zero. A bar that does not start at zero is a
      * different lie, and this prop is not a way into it. It is a floor for the
      * top and not a clip either: a datum above it extends the axis instead of
-     * running off the edge. See `docs/decisions/0.11.md` § 58.
+     * running off the edge. See `docs/decisions/` § 58.
      */
     valueMax?: number | undefined;
     /**

package/dist/chart/index.d.ts

@@ -29,7 +29,7 @@ import { Legend, Tooltip } from 'recharts';
  * What IS published, since this version, are three CHART TYPES on top of that
  * chassis: `AreaChart`, `BarChart` and `LineChart`. They are not wrappers over
  * Recharts' components of the same name — they take `data`, `series` and `xKey`
- * and draw the whole thing. See `docs/decisions/0.8.md` § 43 for why the names
+ * and draw the whole thing. See `docs/decisions/` § 43 for why the names
  * collide on purpose.
  */
 /**
@@ -175,7 +175,7 @@ type SeriesChartProps = Omit<ChartContainerProps, 'children'> & {
      * `2026-07-15` repeated thirty times, overlapping into a grey band.
      *
      * The library imposes no format: a date key can be a day, a month or a course
-     * name, and only the project knows which. See `docs/decisions/0.9.md` § 50.
+     * name, and only the project knows which. See `docs/decisions/` § 50.
      */
     xTickFormatter?: ((value: unknown) => string) | undefined;
     /**
@@ -200,7 +200,7 @@ type SeriesChartProps = Omit<ChartContainerProps, 'children'> & {
      * The bottom is always zero. A bar that does not start at zero is a
      * different lie, and this prop is not a way into it. It is a floor for the
      * top and not a clip either: a datum above it extends the axis instead of
-     * running off the edge. See `docs/decisions/0.11.md` § 58.
+     * running off the edge. See `docs/decisions/` § 58.
      */
     valueMax?: number | undefined;
     /**

package/dist/chart/index.js

@@ -1,8 +1,8 @@
 'use client';
-import { Text } from '../chunk-TRPBID2W.js';
+import { Text } from '../chunk-BFYNBIVJ.js';
 import '../chunk-ODBFN44D.js';
-import { cn } from '../chunk-FAAGZG7A.js';
-import { radius } from '../chunk-FGFNK72B.js';
+import { cn } from '../chunk-TMUGT3Y3.js';
+import { radius } from '../chunk-5YWGOFDX.js';
 import { useId } from 'react';
 import { ResponsiveContainer, Tooltip, Legend, AreaChart as AreaChart$1, CartesianGrid, XAxis, YAxis, Area, BarChart as BarChart$1, Bar, LineChart as LineChart$1, Line } from 'recharts';
 import { jsxs, jsx } from 'react/jsx-runtime';

package/dist/{chunk-FGFNK72B.js → chunk-5YWGOFDX.js}

@@ -144,7 +144,7 @@ var typeScale = {
    * (plankton 5.57:1 over abyss), which is the part that is not negotiable.
    *
    * At 13 the three badge families grew past the size of a small button and
-   * outweighed the title they accompany. See `docs/decisions/`.
+   * outweighed the title they accompany. See `docs/decisions/` § 10.
    */
   chip: { family: "mono", size: 11.5, lineHeight: 1.4, weight: 400 },
   /**
@@ -198,7 +198,7 @@ var control = {
    * baseline; 28 would have been a fifth height that matches nothing.
    *
    * It does not replace `icon`. A page's primary action stays at 42; this is for
-   * a row of a table. See `docs/decisions/0.6.md` § 22.
+   * a row of a table. See `docs/decisions/` § 22.
    */
   iconSm: 32
 };
@@ -221,7 +221,7 @@ var size = {
    * together eat the top of the content area. 56 is what `cursos` had arrived at
    * on its own, and it is the same reasoning as `control.iconSm`: the one admin
    * app of the five is denser than the four reading sites. See
-   * `docs/decisions/0.7.md` § 30.
+   * `docs/decisions/` § 30.
    */
   navCompact: 56,
   /**
@@ -294,7 +294,20 @@ var naming = {
   wordmark: "Eduardo \xC1lvarez",
   mascot: "Tiburonc\xEDn",
   /** The domain, for the footer CLI signature: `$ cd ~/eduardoalvarez.dev/2026`. */
-  domain: "eduardoalvarez.dev"
+  domain: "eduardoalvarez.dev",
+  /** The library's own name, for a footer that credits it. */
+  library: "Arrecife",
+  /**
+   * Where the library is published, for `Footer builtWith`.
+   *
+   * It is here and not written into the component for the reason the domain is:
+   * one string, five projects. It is the same URL as `homepage` in
+   * `package.json` and it cannot be derived from it — this file imports nothing
+   * — so `check:exports` compares the two on every build. Without that, moving
+   * the Storybook would update what npm prints and leave five production
+   * footers linking at the old address.
+   */
+  libraryUrl: "https://arrecife.eduardoalvarez.dev"
 };
 
 export { brand, colors, control, dark, fonts, gradient, light, limits, motion, naming, radius, series, shadow, size, spacing, syntax, tagline, typeScale };

package/dist/{chunk-5A5GH2PF.js → chunk-6QJQ6K7J.js}

@@ -1,4 +1,4 @@
-import { naming, tagline, motion, shadow, series, syntax, gradient, size, spacing, control, radius, limits, typeScale, fonts, brand, colors } from './chunk-FGFNK72B.js';
+import { naming, tagline, motion, shadow, series, syntax, gradient, size, spacing, control, radius, limits, typeScale, fonts, brand, colors } from './chunk-5YWGOFDX.js';
 
 // src/tokens/index.ts
 var tokens = {

package/dist/{chunk-TRPBID2W.js → chunk-BFYNBIVJ.js}

@@ -1,5 +1,5 @@
 import { text } from './chunk-ODBFN44D.js';
-import { cn } from './chunk-FAAGZG7A.js';
+import { cn } from './chunk-TMUGT3Y3.js';
 import { Slot } from '@radix-ui/react-slot';
 import 'class-variance-authority';
 import { jsx } from 'react/jsx-runtime';

package/dist/{chunk-RKGKO2TW.js → chunk-BRDTB44R.js}

@@ -1,6 +1,6 @@
-import { cn } from './chunk-FAAGZG7A.js';
+import { cn } from './chunk-TMUGT3Y3.js';
 import { fins, ASSETS_PATH, poses, faces } from './chunk-CKRSQPTX.js';
-import { naming, tagline } from './chunk-FGFNK72B.js';
+import { naming, tagline } from './chunk-5YWGOFDX.js';
 import { jsxs, Fragment, jsx } from 'react/jsx-runtime';
 
 function Isotype({

package/dist/{chunk-XXDATT3A.js → chunk-FF33ARRA.js}

@@ -19,7 +19,7 @@ var button = cva(
         ],
         // The one control whose focus ring is not biolume. It is the system's
         // only sand fill, and a biolume ring three pixels off a sand button puts
-        // both of the brand's accents in the same glance. See `docs/decisions/0.7.md` § 37.
+        // both of the brand's accents in the same glance. See `docs/decisions/` § 37.
         conversion: "bg-warm text-warm-on hover:bg-warm-hover focus-ring-warm",
         secondary: [
           "border-hairline-hover border bg-transparent text-text-primary",

package/dist/{chunk-FAAGZG7A.js → chunk-TMUGT3Y3.js}

@@ -1,4 +1,4 @@
-import { spacing, control, radius, typeScale } from './chunk-FGFNK72B.js';
+import { spacing, control, radius, typeScale } from './chunk-5YWGOFDX.js';
 import { clsx } from 'clsx';
 import { extendTailwindMerge } from 'tailwind-merge';
 

package/dist/{chunk-6IGD5REB.js → chunk-W75O3Z77.js}

@@ -1,4 +1,4 @@
-import { cn } from './chunk-FAAGZG7A.js';
+import { cn } from './chunk-TMUGT3Y3.js';
 import * as LabelPrimitive from '@radix-ui/react-label';
 import { jsx } from 'react/jsx-runtime';
 

package/dist/{chunk-ZSCSKCTY.js → chunk-WU66TPJT.js}

@@ -1,4 +1,4 @@
-import { cn } from './chunk-FAAGZG7A.js';
+import { cn } from './chunk-TMUGT3Y3.js';
 import { jsx } from 'react/jsx-runtime';
 
 var ICON_WEIGHT = "regular";

package/dist/form/index.cjs

@@ -67,7 +67,7 @@ var typeScale = {
    * (plankton 5.57:1 over abyss), which is the part that is not negotiable.
    *
    * At 13 the three badge families grew past the size of a small button and
-   * outweighed the title they accompany. See `docs/decisions/`.
+   * outweighed the title they accompany. See `docs/decisions/` § 10.
    */
   chip: { family: "mono", size: 11.5, lineHeight: 1.4, weight: 400 },
   /**
@@ -113,7 +113,7 @@ var control = {
    * baseline; 28 would have been a fifth height that matches nothing.
    *
    * It does not replace `icon`. A page's primary action stays at 42; this is for
-   * a row of a table. See `docs/decisions/0.6.md` § 22.
+   * a row of a table. See `docs/decisions/` § 22.
    */
   iconSm: 32
 };

package/dist/form/index.js

@@ -1,9 +1,9 @@
 'use client';
-import { Label } from '../chunk-6IGD5REB.js';
-import { Text } from '../chunk-TRPBID2W.js';
+import { Label } from '../chunk-W75O3Z77.js';
+import { Text } from '../chunk-BFYNBIVJ.js';
 import '../chunk-ODBFN44D.js';
-import { cn } from '../chunk-FAAGZG7A.js';
-import '../chunk-FGFNK72B.js';
+import { cn } from '../chunk-TMUGT3Y3.js';
+import '../chunk-5YWGOFDX.js';
 import { createContext, useContext, useId } from 'react';
 import { FormProvider, Controller, useFormContext, useFormState } from 'react-hook-form';
 import { Slot } from '@radix-ui/react-slot';

package/dist/icons/index.cjs

@@ -41,7 +41,7 @@ var typeScale = {
    * (plankton 5.57:1 over abyss), which is the part that is not negotiable.
    *
    * At 13 the three badge families grew past the size of a small button and
-   * outweighed the title they accompany. See `docs/decisions/`.
+   * outweighed the title they accompany. See `docs/decisions/` § 10.
    */
   chip: { family: "mono", size: 11.5, lineHeight: 1.4, weight: 400 },
   /**
@@ -87,7 +87,7 @@ var control = {
    * baseline; 28 would have been a fifth height that matches nothing.
    *
    * It does not replace `icon`. A page's primary action stays at 42; this is for
-   * a row of a table. See `docs/decisions/0.6.md` § 22.
+   * a row of a table. See `docs/decisions/` § 22.
    */
   iconSm: 32
 };

package/dist/icons/index.d.cts

@@ -43,7 +43,7 @@ import { IconWeight, IconProps as IconProps$1, Icon as Icon$1 } from '@phosphor-
  * THE WEIGHT IS AN AXIS, AND IT IS THE ONLY ONE AN ICON HAS. There are three
  * roles and `tone` is how you name them; the weights themselves are not a prop,
  * because Phosphor's other three — `thin`, `bold`, `duotone` — say nothing this
- * system means. See `TONE_WEIGHT` below and `docs/decisions/0.7.md` § 35.
+ * system means. See `TONE_WEIGHT` below and `docs/decisions/` § 35.
  *
  * IT IS NOW THE ONLY LINE THE LIBRARY DRAWS, which is what 0.10.0 changed.
  * `lib/glyphs.tsx` drew at 1.75 on a 16 grid — 0.109em, three quarters heavier
@@ -51,7 +51,7 @@ import { IconWeight, IconProps as IconProps$1, Icon as Icon$1 } from '@phosphor-
  * third hand. 0.7.0 left both alone because reconciling them restyles every
  * primitive in the library; that is exactly what 0.10.0 did, and both files are
  * gone. There is one description of what a line looks like here, and it is
- * Phosphor's. See `docs/decisions/0.10.md` § 51.
+ * Phosphor's. See `docs/decisions/` § 51.
  *
  * IN NEXT, IMPORT FROM `@phosphor-icons/react/ssr` inside a Server Component.
  * Phosphor's default build reads `IconContext` through `useContext`, and a hook

package/dist/icons/index.d.ts

@@ -43,7 +43,7 @@ import { IconWeight, IconProps as IconProps$1, Icon as Icon$1 } from '@phosphor-
  * THE WEIGHT IS AN AXIS, AND IT IS THE ONLY ONE AN ICON HAS. There are three
  * roles and `tone` is how you name them; the weights themselves are not a prop,
  * because Phosphor's other three — `thin`, `bold`, `duotone` — say nothing this
- * system means. See `TONE_WEIGHT` below and `docs/decisions/0.7.md` § 35.
+ * system means. See `TONE_WEIGHT` below and `docs/decisions/` § 35.
  *
  * IT IS NOW THE ONLY LINE THE LIBRARY DRAWS, which is what 0.10.0 changed.
  * `lib/glyphs.tsx` drew at 1.75 on a 16 grid — 0.109em, three quarters heavier
@@ -51,7 +51,7 @@ import { IconWeight, IconProps as IconProps$1, Icon as Icon$1 } from '@phosphor-
  * third hand. 0.7.0 left both alone because reconciling them restyles every
  * primitive in the library; that is exactly what 0.10.0 did, and both files are
  * gone. There is one description of what a line looks like here, and it is
- * Phosphor's. See `docs/decisions/0.10.md` § 51.
+ * Phosphor's. See `docs/decisions/` § 51.
  *
  * IN NEXT, IMPORT FROM `@phosphor-icons/react/ssr` inside a Server Component.
  * Phosphor's default build reads `IconContext` through `useContext`, and a hook

package/dist/icons/index.js

@@ -1,3 +1,3 @@
-export { ICON_WEIGHT, Icon, TONE_WEIGHT } from '../chunk-ZSCSKCTY.js';
-import '../chunk-FAAGZG7A.js';
-import '../chunk-FGFNK72B.js';
+export { ICON_WEIGHT, Icon, TONE_WEIGHT } from '../chunk-WU66TPJT.js';
+import '../chunk-TMUGT3Y3.js';
+import '../chunk-5YWGOFDX.js';