@lessly/sdk-app 47.1.0 → 47.1.1

package/docs/README.md

@@ -16,7 +16,7 @@ handed to it by the shell that hosts it.
 
 Contrast this with a Lessly **extension**: an extension owns a backend
 service, a database, and typically an MCP endpoint, and is built against the
-extensions-guide contracts (`MFST-*`, `PRD-*`, `MCP-*`, etc.). An App has none
+toolkit-guide contracts (`MFST-*`, `PRD-*`, `MCP-*`, etc.). An App has none
 of that surface. If your task involves a database migration, a service-to-service
 scope, or an MCP tool, you are building an extension, not an App — this guide
 does not apply.

package/docs/recipes/federation.md

@@ -3,7 +3,7 @@
 How to wire the Module Federation contract an App must implement (APP-004),
 and the dual-mode CSS graph that goes with it (APP-008, APP-009, APP-010).
 This page shows the *how*; for exact wording, rationale, and examples of the
-shared rules, see the referenced `FED-*` IDs in the extensions-guide — this
+shared rules, see the referenced `FED-*` IDs in the toolkit-guide — this
 recipe does not restate them.
 
 ## Expose `./App` — and nothing else

package/docs/rules.md

@@ -10,7 +10,7 @@ Rule IDs (`APP-NNN`) are immutable once merged: a rule's ID and meaning never
 change, even if its wording is later clarified. Some of these rules cover
 ground shared with extensions and the platform's Module Federation host; where
 that's true, this file references the existing `FED-*` rule ID from the
-extensions-guide instead of restating it — go there for the full rule text,
+toolkit-guide instead of restating it — go there for the full rule text,
 rationale, and examples.
 
 ---
@@ -162,7 +162,7 @@ declares layer order and is harmless; the forbidden shape is the block,
 more than custom properties.
 
 For the production defect this comes from — a remote's late-loading `body`
-rule re-fonting the shell's chrome — see FED-008 in the extensions-guide.
+rule re-fonting the shell's chrome — see FED-008 in the toolkit-guide.
 `recipes/federation.md` has the canonical stylesheets.
 
 ### APP-009 (MUST) — One source of scale vocabulary: `lesslyPreset`
@@ -194,7 +194,7 @@ by their sheets. Do not write a guard that way.
 
 When both sides build on the same preset, rules that share a class name compile
 identically and the collision stops existing. See FED-013 in the
-extensions-guide for the measurements (13px → 14px, line-height 19.5 → 20) and
+toolkit-guide for the measurements (13px → 14px, line-height 19.5 → 20) and
 for the three wrong fixes it rules out.
 
 ### APP-010 (MUST) — Federation utilities land in `layer(remote-utilities)`
@@ -229,7 +229,7 @@ therefore **highest**-priority — layer, so every App utility beats every shell
 utility: strictly worse than the defect. Verify the shell first; adopting early
 is a regression, not a head start.
 
-See FED-014 in the extensions-guide for the measurement (App `.px-2` against
+See FED-014 in the toolkit-guide for the measurement (App `.px-2` against
 shell `.sm:px-2.5` — different rule names, so no shared preset can reach them;
 5 of 283 shell chrome nodes affected) and for the accepted symmetric risk on
 the App's own nodes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lessly/sdk-app",
-  "version": "47.1.0",
+  "version": "47.1.1",
   "type": "module",
   "sideEffects": false,
   "engines": {