@cat-factory/app 0.234.0 → 0.234.2

package/README.md

@@ -3,10 +3,10 @@
 The user-facing app, packaged as a **reusable Nuxt 4 layer**: a single-page app
 that runs entirely in the browser and renders the architecture board, drives agent
 pipelines, and reflects live execution. A deployment consumes it via
-`extends: ['@cat-factory/app']` (see [`deploy/frontend`](../../deploy/frontend)).
-It talks to the [backend Worker](../../backend/README.md) over REST and a single
+`extends: ['@cat-factory/app']` (see [`deploy/frontend`](https://github.com/kibertoad/cat-factory/tree/main/deploy/frontend)).
+It talks to the [backend Worker](https://github.com/kibertoad/cat-factory/blob/main/backend/README.md) over REST and a single
 WebSocket, sharing wire types from
-[`@cat-factory/contracts`](../../backend/packages/contracts).
+[`@cat-factory/contracts`](https://github.com/kibertoad/cat-factory/tree/main/backend/packages/contracts).
 
 The SPA source lives under `app/` (the Nuxt srcDir).
 
@@ -364,7 +364,7 @@ is SUPPRESSED rather than unmounted, because it holds the running tour's resolve
 remount would re-resolve it against gates that may have flipped since the tour started.
 
 The decisions behind this surface, and why each alternative was rejected, are recorded in
-[ADR 0036](../../backend/docs/adr/0036-in-app-tutorials.md). This section is the authority on how
+[ADR 0036](https://github.com/kibertoad/cat-factory/blob/main/backend/docs/adr/0036-in-app-tutorials.md). This section is the authority on how
 the thing WORKS.
 
 A tour is **data, not components**: an ordered list of steps, each pointing at an on-screen
@@ -583,7 +583,7 @@ event left to restore it.
 All user-facing SPA copy goes through `@nuxtjs/i18n`; never hard-code a display string. This
 layer ships the base `en` locale, and a downstream deployment overrides by dropping its own files
 (the per-layer deep-merge is the override seam, consumer wins key by key). Migration status:
-[`docs/internal/localization.md`](../../docs/internal/localization.md).
+[`docs/internal/localization.md`](https://github.com/kibertoad/cat-factory/blob/main/docs/internal/localization.md).
 
 - `i18n/locales/<locale>.json`: the catalogs (the v9+ `i18n/` convention, NOT `app/locales/`).
 - `i18n/i18n.config.ts`: runtime vue-i18n behaviour only (fallback locale, the plural
@@ -688,7 +688,7 @@ auto-imported
 (`ResultWindowShell`, the `StepRunMeta` run-metadata block, `useResultView`, …), and the
 namespacing / degradation rules are in
 [`app/docs/consumer-extensions.md`](./app/docs/consumer-extensions.md); a full worked
-example ships in [`deploy/frontend`](../../deploy/frontend) (the `acme:security` module).
+example ships in [`deploy/frontend`](https://github.com/kibertoad/cat-factory/tree/main/deploy/frontend) (the `acme:security` module).
 
 ## Key UI surfaces
 
@@ -795,5 +795,5 @@ pnpm lint         # oxlint + oxfmt --check
 ```
 
 > Building/deploying the static site is covered in the deployment docs: see the
-> [top-level README → Deployment](../../README.md#deployment) and
-> [`deploy/frontend/README.md`](../../deploy/frontend/README.md).
+> [top-level README → Deployment](https://github.com/kibertoad/cat-factory/blob/main/README.md#deployment) and
+> [`deploy/frontend/README.md`](https://github.com/kibertoad/cat-factory/blob/main/deploy/frontend/README.md).

package/app/docs/consumer-extensions.md

@@ -4,19 +4,19 @@ A deployment that consumes this layer (`extends: ['@cat-factory/app']`) can cont
 its own **components** (result windows, navigation entries, inspector panels, agent-kind
 palette data) **without forking the layer**. This is the frontend counterpart of the
 backend's public registries (`registerAgentKind`, `registerGate`; see
-[`backend/docs/custom-agents.md`](../../../backend/docs/custom-agents.md)). The governing
+[`backend/docs/custom-agents.md`](https://github.com/kibertoad/cat-factory/blob/main/backend/docs/custom-agents.md)). The governing
 principle is the same: **zero host edits for a consumer extension**.
 
 A worked, end-to-end example ships in the template deployment:
-[`deploy/frontend/app/`](../../../deploy/frontend) (the `acme:security` module): the
+[`deploy/frontend/app/`](https://github.com/kibertoad/cat-factory/tree/main/deploy/frontend/app) (the `acme:security` module): the
 frontend analogue of the backend
-[`@cat-factory/example-custom-agent`](../../../backend/internal/example-custom-agent)
+[`@cat-factory/example-custom-agent`](https://github.com/kibertoad/cat-factory/tree/main/backend/internal/example-custom-agent)
 package. Read this guide alongside it.
 
 > This is the **landed** surface (modular-vue adoption slices 1–5). The larger consumer
 > extension programme (custom task types, generic interactive phases, overlays, consumer
 > notification kinds, stream events, and the hardened public export surface) is tracked in
-> [`docs/initiatives/frontend-extension-mechanism.md`](../../../docs/initiatives/frontend-extension-mechanism.md).
+> [`docs/initiatives/frontend-extension-mechanism.md`](https://github.com/kibertoad/cat-factory/blob/main/docs/initiatives/frontend-extension-mechanism.md).
 
 ## The one seam: `registerAppModule`
 
@@ -219,8 +219,11 @@ suite can address a row and the caption inside it.
 Together, `fields` + `defaultFragmentIds` + `defaultPipelineId` are what turns a task type from a
 badge into a **reusable operation**: a canned unit of work an org runs repeatedly with per-case
 input, whose collected values reach every agent's prompt. See
-[`backend/docs/reusable-operations.md`](../../../../backend/docs/reusable-operations.md) and the
-`org:introduce-api` worked example in `backend/internal/example-custom-agent`.
+[`backend/docs/reusable-operations.md`](https://github.com/kibertoad/cat-factory/blob/main/backend/docs/reusable-operations.md) and the
+[`org:introduce-api` worked example](https://github.com/kibertoad/cat-factory/tree/main/backend/internal/example-custom-agent).
+Both links are absolute on purpose: this page ships inside the `@cat-factory/app` tarball, so a
+relative path out of it resolves only from a checkout, which is the one place its reader is not.
+(`scripts/check-shipped-doc-links.mjs` fails CI on a shipped doc that grows one.)
 
 The **same type can be delivered from the backend** instead of code-shipped: register it on the
 deployment's app-owned `TaskTypeRegistry` and it arrives in the workspace snapshot's

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cat-factory/app",
-  "version": "0.234.0",
+  "version": "0.234.2",
   "description": "Reusable Nuxt layer for the Agent Architecture Board SPA (components, stores, composables, pages). Consume it from a thin deployment app via `extends: ['@cat-factory/app']` and point it at your backend with NUXT_PUBLIC_API_BASE. See deploy/frontend for an example.",
   "repository": {
     "type": "git",
@@ -40,7 +40,7 @@
     "valibot": "^1.4.2",
     "vue": "3.5.40",
     "wretch": "^3.0.9",
-    "@cat-factory/contracts": "0.252.0"
+    "@cat-factory/contracts": "0.254.0"
   },
   "devDependencies": {
     "@toad-contracts/testing": "0.3.2",