@intentic/extension-ui 1.224.0 → 1.226.0

package/README.md

@@ -11,29 +11,29 @@ actually use. One of the two packages an extension may depend on (with
 This package's [`src/index.ts`](src/index.ts) is its one public surface (the repo's re-export exception). The
 kit is **host-provided**: the web app maps this module into its import map
 ([extension-host/hostModules.ts](../../_editor/web/src/extension-host/hostModules.ts)), so a third-party bundle
-that marks it external resolves to the **shell's own** component instances and theming — one Vue, one
+that marks it external resolves to the **shell's own** component instances and theming: one Vue, one
 PrimeVue, one theme across the host and every extension. In-repo builtin extensions bundle this same module
 and land on the same instances.
 
-The scope reads oddly — an `@intentic/*` package depending on the app-side `@intentic/ui` — but it is
+The scope reads oddly (an `@intentic/*` package depending on the app-side `@intentic/ui`) but it is
 deliberate: the dependency is build-time-only (for in-repo builtins); at runtime the import map supplies the
 shell's instances, so no second copy is shipped.
 
 ## Drift assertion
 
-Export names are mirrored in [`names.mjs`](names.mjs), which drives shim generation and a drift assertion —
+Export names are mirrored in [`names.mjs`](names.mjs), which drives shim generation and a drift assertion:
 keep the two in sync when adding or removing an export. Publishing a typed npm artifact for out-of-repo
 authors is a marketplace-phase task.
 
 ## Key files
 
-- [src/index.ts](src/index.ts) — the whole surface: which components and helpers an extension may render with.
-- [src/format.ts](src/format.ts) — the shared formatters, so two extensions render a duration the same way.
+- [src/index.ts](src/index.ts), the whole surface: which components and helpers an extension may render with.
+- [src/format.ts](src/format.ts): the shared formatters, so two extensions render a duration the same way.
 
 ## The one control worth calling out
 
-`AgentRunButton` and `useAgentRunPick` are re-exported because four extensions start an agent for the user —
-pipelines, deployments, maintenance, acceptance — and each had reached its own answer about how you choose what
+`AgentRunButton` and `useAgentRunPick` are re-exported because four extensions start an agent for the user:
+pipelines, deployments, maintenance, acceptance: and each had reached its own answer about how you choose what
 that costs. Press the primary half and the run opens on the sandbox's standing agent-run model; use the caret
 and it opens on something else, for that run only.
 

package/dist/format.js

@@ -1,8 +1,8 @@
-// Generated by scripts/build.mjs — do not edit.
+// Generated by scripts/build.mjs: do not edit.
 // The formatting half of the kit, off the same host bridge as ./index.js.
 const host = globalThis.__intenticHost;
 if (host === undefined) {
-    throw new Error("@intentic/extension-ui was loaded outside an intentic host — its helpers come from the app, not from this package.");
+    throw new Error("@intentic/extension-ui was loaded outside an intentic host: its helpers come from the app, not from this package.");
 }
 const m = host.modules["@intentic/extension-ui"];
 export const formatBytes = m["formatBytes"];

package/dist/index.js

@@ -1,12 +1,12 @@
-// Generated by scripts/build.mjs — do not edit.
-/* The kit is HOST-PROVIDED. These components must be the shell's own instances — a second copy would
- * render unthemed, outside the app's reactivity and outside its one query cache — so this module reads
+// Generated by scripts/build.mjs: do not edit.
+/* The kit is HOST-PROVIDED. These components must be the shell's own instances: a second copy would
+ * render unthemed, outside the app's reactivity and outside its one query cache, so this module reads
  * them off the bridge the host publishes rather than containing any. Marking "@intentic/extension-ui"
  * external in your bundler is the tidier route (the app's import map answers it); this file is what makes
  * forgetting to do that harmless instead of silent. */
 const host = globalThis.__intenticHost;
 if (host === undefined) {
-    throw new Error("@intentic/extension-ui was loaded outside an intentic host — its components come from the app, not from this package.");
+    throw new Error("@intentic/extension-ui was loaded outside an intentic host: its components come from the app, not from this package.");
 }
 const m = host.modules["@intentic/extension-ui"];
 export const AgentRunButton = m["AgentRunButton"];

package/names.mjs

@@ -1,4 +1,4 @@
-// The kit's export names — the single source consumed by the web app's shim generator
+// The kit's export names: the single source consumed by the web app's shim generator
 // (_editor/web/scripts/generate-ext-shims.mjs) and hostModules' dev-time coverage assertion. Update alongside
 // src/index.ts; the assertion catches drift on the next dev boot.
 export const extensionUiNames = [

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@intentic/extension-ui",
-  "version": "1.224.0",
-  "description": "The UI kit intentic extensions render with — host-provided at runtime (the app's own components via the import map), so extension UI is always native to the shell",
+  "version": "1.226.0",
+  "description": "The UI kit intentic extensions render with, host-provided at runtime (the app's own components via the import map), so extension UI is always native to the shell",
   "license": "MIT",
   "type": "module",
   "repository": {

package/src/index.ts

@@ -252,7 +252,7 @@ export type {
 /* The raw primitives, kept deliberately short. Handing out a primitive the KIT already wraps is how an
  * extension screen ends up wearing OS chrome next to the app's own: `Select` and `InputText` used to ship here
  * and four views took them, so a dropdown with a different focus ring sat beside <Picker> and a text field with
- * different padding beside `ui.input`. Those two are gone — <Picker> and `ui.input()` are the spellings.
+ * different padding beside `ui.input`. Those two are gone: <Picker> and `ui.input()` are the spellings.
  * <Dialog> was the third, and it is gone for the same reason: it stayed "until the kit has a general dialog
  * shell", six extension views took it, and every one of them typed its own width into a style attribute with
  * no viewport clamp, the exact spread that <Modal> above now exists to end. The shell is here, so the raw one