@alexkroman1/aai-ui 16.0.0 → 16.1.0

package/dist/components/audio-result.d.ts

@@ -58,9 +58,9 @@ export type AudioResultProps = {
  * and that is the whole reason both pages hand this a hook result rather than a
  * path.
  *
- * **A caption track is a judgement, not a default.** `spoken-summary` passes
+ * **A caption track is a judgement, not a default.** `spoken-summary-workflow` passes
  * `captions`: the summary was written before it was spoken, so one cue
- * spanning the clip is an honest transcript of it. `call-audit` deliberately
+ * spanning the clip is an honest transcript of it. `call-audit-workflow` deliberately
  * does not: the spoken text is rendered in full immediately below the player,
  * which is the same information a track would carry. Both are right, which is
  * why the prop is optional in both directions.

package/dist/components/facts.d.ts

@@ -42,7 +42,7 @@ export type FactsProps = {
  * 1,840 words".
  *
  * Nine pages had written this by hand under four different typographies for
- * one role, two of them (`call-audit` and `spoken-summary`) byte-identical down
+ * one role, two of them (`call-audit-workflow` and `spoken-summary-workflow`) byte-identical down
  * to the payload. Three things it takes off the caller:
  *
  * - **The separator cannot be forgotten, and neither can the space around it.**

package/dist/components/workflow-run-panel.d.ts

@@ -40,7 +40,7 @@ export type WorkflowRunPanelProps<O> = {
  * button, the run's own narration, the live slot while it works, the completed
  * body once it has, and the announced error if it failed.
  *
- * Two pages had written this shell — `redline` and `transcription-workflow` —
+ * Two pages had written this shell — `document-redline-workflow` and `transcription-workflow` —
  * with the same header, the same `text-xs underline` Clear, the same
  * {@link WorkflowProgress} under it, the same `run.status === "completed"`
  * discrimination above the same {@link WorkflowRunError}, and each spread

package/dist/context.d.ts

@@ -62,7 +62,7 @@ export declare function useSessionCore(): BrowserSession;
  * rebuilds the snapshot object on every change. Measured consequence: four
  * components across three templates re-rendered on every STT partial and every
  * streaming delta, in files whose every other component is narrowly subscribed
- * on purpose. One of them (`infocom-adventure`'s `TitleScreen`) reads nothing
+ * on purpose. One of them (`text-adventure-agent`'s `TitleScreen`) reads nothing
  * from the snapshot at all and subscribes to all of it for `session.start`.
  *
  * **Why publishing this does not reopen what `/internal` closed.**

package/dist/context.js

@@ -47,7 +47,7 @@ function useSessionCore() {
 * rebuilds the snapshot object on every change. Measured consequence: four
 * components across three templates re-rendered on every STT partial and every
 * streaming delta, in files whose every other component is narrowly subscribed
-* on purpose. One of them (`infocom-adventure`'s `TitleScreen`) reads nothing
+* on purpose. One of them (`text-adventure-agent`'s `TitleScreen`) reads nothing
 * from the snapshot at all and subscribes to all of it for `session.start`.
 *
 * **Why publishing this does not reopen what `/internal` closed.**

package/dist/hooks.d.ts

@@ -133,7 +133,7 @@ export declare function useAgentState<S = DefaultToolResult>(): S | null;
  * is expensive to IMPORT.** A projection is built from the slot, so the browser
  * bundle gets whatever that module pulls in — and the cost is the static import
  * graph rather than the `create()` call, so no option on the slot can avoid it.
- * `retail` is the worked example: its slot lives beside a 107 KB seed, so the
+ * `retail-orders-agent` is the worked example: its slot lives beside a 107 KB seed, so the
  * page passes a `fallback` built by running the same view over a cheap empty
  * state, from a module that imports no seed. Reach for this overload
  * everywhere the slot's module is cheap, which is every other stateful

package/dist/index.js

@@ -48,9 +48,9 @@ function captionsUrl(text, durationMs) {
 * and that is the whole reason both pages hand this a hook result rather than a
 * path.
 *
-* **A caption track is a judgement, not a default.** `spoken-summary` passes
+* **A caption track is a judgement, not a default.** `spoken-summary-workflow` passes
 * `captions`: the summary was written before it was spoken, so one cue
-* spanning the clip is an honest transcript of it. `call-audit` deliberately
+* spanning the clip is an honest transcript of it. `call-audit-workflow` deliberately
 * does not: the spoken text is rendered in full immediately below the player,
 * which is the same information a track would carry. Both are right, which is
 * why the prop is optional in both directions.
@@ -191,7 +191,7 @@ const FACT_SEPARATOR = " · ";
 * 1,840 words".
 *
 * Nine pages had written this by hand under four different typographies for
-* one role, two of them (`call-audit` and `spoken-summary`) byte-identical down
+* one role, two of them (`call-audit-workflow` and `spoken-summary-workflow`) byte-identical down
 * to the payload. Three things it takes off the caller:
 *
 * - **The separator cannot be forgotten, and neither can the space around it.**
@@ -1680,7 +1680,7 @@ const WORKFLOW_STATUS_LABELS = {
 * button, the run's own narration, the live slot while it works, the completed
 * body once it has, and the announced error if it failed.
 *
-* Two pages had written this shell — `redline` and `transcription-workflow` —
+* Two pages had written this shell — `document-redline-workflow` and `transcription-workflow` —
 * with the same header, the same `text-xs underline` Clear, the same
 * {@link WorkflowProgress} under it, the same `run.status === "completed"`
 * discrimination above the same {@link WorkflowRunError}, and each spread
@@ -1952,7 +1952,7 @@ function useDownloadUrl(uploadId, options = {}) {
 * coming back on Friday to press Stop is the ordinary case rather than an edge
 * one, and a tab-scoped key would answer that with an empty form beside a run
 * still posting somewhere. It is as far as a key can go without a login, and no
-* further. `podcast-digest` is that template, and the reason this hook is still
+* further. `podcast-digest-workflow` is that template, and the reason this hook is still
 * called by name anywhere; the other five take the tab-scoped default the
 * submit hook mints for them.
 *
@@ -2749,7 +2749,7 @@ function coalesceUploadReports(set) {
 *
 * A page that submits a workflow always needs the same four pieces of state:
 * the run id, whether a submit is in flight, whether the RUN is still going, and
-* whichever of the two failed. `link-digest` writes them out by hand, which is
+* whichever of the two failed. `link-digest-workflow` writes them out by hand, which is
 * the right shape for a template teaching the primitives and the wrong shape to
 * write a third time — and it is easy to get subtly wrong: dropping the previous
 * run id before the new `POST` returns is what stops a finished result sitting

package/dist/use-run-key.d.ts

@@ -51,7 +51,7 @@
  * coming back on Friday to press Stop is the ordinary case rather than an edge
  * one, and a tab-scoped key would answer that with an empty form beside a run
  * still posting somewhere. It is as far as a key can go without a login, and no
- * further. `podcast-digest` is that template, and the reason this hook is still
+ * further. `podcast-digest-workflow` is that template, and the reason this hook is still
  * called by name anywhere; the other five take the tab-scoped default the
  * submit hook mints for them.
  *

package/dist/use-workflow-form.d.ts

@@ -10,7 +10,7 @@
  *
  * A page that submits a workflow always needs the same four pieces of state:
  * the run id, whether a submit is in flight, whether the RUN is still going, and
- * whichever of the two failed. `link-digest` writes them out by hand, which is
+ * whichever of the two failed. `link-digest-workflow` writes them out by hand, which is
  * the right shape for a template teaching the primitives and the wrong shape to
  * write a third time — and it is easy to get subtly wrong: dropping the previous
  * run id before the new `POST` returns is what stops a finished result sitting

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@alexkroman1/aai-ui",
-  "version": "16.0.0",
+  "version": "16.1.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -46,7 +46,7 @@
     "use-stick-to-bottom": "^1.1.6",
     "use-sync-external-store": "^1.6.0",
     "xstate": "^5.32.6",
-    "@alexkroman1/aai": "16.0.0"
+    "@alexkroman1/aai": "16.1.0"
   },
   "devDependencies": {
     "@tailwindcss/vite": "^4.3.3",

package/styles.css

@@ -101,8 +101,8 @@
  * reaches the TEMPLATES.** Every template's `client.tsx` opens with
  * `import "@alexkroman1/aai-ui/styles.css"`, and several then declare keyframes
  * of their own in an inline `<style>` block: `dc-pulse`/`dc-slide-in`
- * (dispatch-center), `rt-pulse`/`rt-slide-in` (retail), `crisisPulse`
- * (solo-rpg), and `ic-flicker`/`ic-scanline`/`ic-pulse` (infocom-adventure,
+ * (emergency-dispatch-agent), `rt-pulse`/`rt-slide-in` (retail), `crisisPulse`
+ * (tabletop-rpg-agent), and `ic-flicker`/`ic-scanline`/`ic-pulse` (text-adventure-agent,
  * which flickers the whole viewport's opacity and sweeps a scanline across the
  * page — the worst thing in the repo for a motion-sensitive reader). Nothing in
  * this package knows those names, and no per-component fix could: it would have