@signal9/era-ui 26.1.0 → 27.0.0

package/CHANGELOG.md

@@ -1,3 +1,24 @@
+## [27.0.0](https://github.com/sig-nine/era-ui/compare/v26.1.1...v27.0.0) (2026-08-14)
+
+### ⚠ BREAKING CHANGES
+
+* **docs:** @signal9/era-ui/docs/llms-txt is removed. It resolved through
+the ./* wildcard rather than by design, and returned stale content — the
+served /llms.txt and /llms-full.txt are unaffected.
+
+Claude-Session: https://claude.ai/code/session_011FjvULDrmxd61z2xUnYs6Z
+
+### Bug Fixes
+
+* **docs:** delete the llms.txt builder nothing has called since it was copied ([6986b0d](https://github.com/sig-nine/era-ui/commit/6986b0d0d79839901d7a04b1bf4997d03f2e5b9d))
+* **docs:** the registry parser dropped two components and misattributed a third ([374ec4b](https://github.com/sig-nine/era-ui/commit/374ec4b69d68e6061bfcddadc7d61d46a662ccd5))
+
+## [26.1.1](https://github.com/sig-nine/era-ui/compare/v26.1.0...v26.1.1) (2026-08-14)
+
+### Bug Fixes
+
+* **nav:** the link variant's current weight is 600, because 500 does nothing in mono ([012eeed](https://github.com/sig-nine/era-ui/commit/012eeedc34cfe42088a3d75c7fdc1f9d28b804cd))
+
 ## [26.1.0](https://github.com/sig-nine/era-ui/compare/v26.0.1...v26.1.0) (2026-08-14)
 
 ### Features

package/dist/docs/consumer-import.d.ts

@@ -25,6 +25,34 @@
  * specifiers the rest of src/lib/docs uses.
  */
 export declare const PACKAGE = "@signal9/era-ui";
+/**
+ * The install command WITH the pin, because npm's default fights era's cadence.
+ *
+ * `npm install @signal9/era-ui` writes a caret range. A caret still holds the
+ * major — `^26.1.0` resolves `<27.0.0` — so it is not the open subscription to
+ * the next breaking release it gets mistaken for. The real exposure is smaller
+ * and sharper than that, and it is worse:
+ *
+ *   1. era's majors are not annual. Measured at 26.1.1: 132 releases in the
+ *      preceding 30 days, 24 of them major. The protection a caret buys is
+ *      about a day and a quarter of era time.
+ *   2. Inside that window the minors and patches MOVE PIXELS. `fix(command): a
+ *      row carries its OWN tier's radius` is a patch, and it changes what every
+ *      command palette row looks like. For a library whose output is geometry
+ *      there is no such thing as a rendering-neutral patch, so semver's promise
+ *      — "patches are safe to float" — does not describe what era ships.
+ *
+ * So era's advice is to pin exact. This is that advice as the command that
+ * PRODUCES the pin, rather than as a sentence printed next to a command that
+ * does not: a reader who copies the snippet is pinned, whereas a reader given a
+ * bare `npm install` and a note about `--save-exact` is pinned only if they
+ * copied the prose too.
+ *
+ * Found by signalnine.org, which shipped a caret it never meant to and caught it
+ * reading its own diff. Every other pin in that repo was exact and deliberate —
+ * the docs had simply never said so, and the default quietly answered instead.
+ */
+export declare const INSTALL = "npm install --save-exact @signal9/era-ui";
 /** How a component is re-exported by the internal barrel. */
 export type ImportKind = 'named' | 'namespace';
 /** The import statement, in the spelling that actually resolves. */

package/dist/docs/consumer-import.js

@@ -25,6 +25,34 @@
  * specifiers the rest of src/lib/docs uses.
  */
 export const PACKAGE = '@signal9/era-ui';
+/**
+ * The install command WITH the pin, because npm's default fights era's cadence.
+ *
+ * `npm install @signal9/era-ui` writes a caret range. A caret still holds the
+ * major — `^26.1.0` resolves `<27.0.0` — so it is not the open subscription to
+ * the next breaking release it gets mistaken for. The real exposure is smaller
+ * and sharper than that, and it is worse:
+ *
+ *   1. era's majors are not annual. Measured at 26.1.1: 132 releases in the
+ *      preceding 30 days, 24 of them major. The protection a caret buys is
+ *      about a day and a quarter of era time.
+ *   2. Inside that window the minors and patches MOVE PIXELS. `fix(command): a
+ *      row carries its OWN tier's radius` is a patch, and it changes what every
+ *      command palette row looks like. For a library whose output is geometry
+ *      there is no such thing as a rendering-neutral patch, so semver's promise
+ *      — "patches are safe to float" — does not describe what era ships.
+ *
+ * So era's advice is to pin exact. This is that advice as the command that
+ * PRODUCES the pin, rather than as a sentence printed next to a command that
+ * does not: a reader who copies the snippet is pinned, whereas a reader given a
+ * bare `npm install` and a note about `--save-exact` is pinned only if they
+ * copied the prose too.
+ *
+ * Found by signalnine.org, which shipped a caret it never meant to and caught it
+ * reading its own diff. Every other pin in that repo was exact and deliberate —
+ * the docs had simply never said so, and the default quietly answered instead.
+ */
+export const INSTALL = `npm install --save-exact ${PACKAGE}`;
 /** The import statement, in the spelling that actually resolves. */
 export function importLine(kind, alias, slug) {
     const spec = `"${PACKAGE}/${slug}"`;