@lssm/example.learning-journey-ui-onboarding 0.0.0-canary-20251217062139 → 0.0.0-canary-20251217072406

package/dist/index.mjs

@@ -1,10 +1,11 @@
-import { i as Overview, n as ProgressView, r as Steps, t as Timeline } from "./views-BuZeDMLr.mjs";
-import { n as StepChecklist, t as JourneyMap } from "./JourneyMap-Cu8t0fYp.mjs";
+import { i as Overview, n as ProgressView, r as Steps, t as Timeline } from "./views-BS9u6UnM.mjs";
+import { n as StepChecklist, t as JourneyMap } from "./JourneyMap-CZ47DksM.mjs";
 import { t as CodeSnippet } from "./components-OUN5S2z0.mjs";
 import { useCallback, useState } from "react";
 import { Card, CardContent } from "@lssm/lib.ui-kit-web/ui/card";
 import { ViewTabs, useLearningProgress } from "@lssm/example.learning-journey-ui-shared";
 import { jsx, jsxs } from "react/jsx-runtime";
+import { registerDocBlocks } from "@lssm/lib.contracts/docs";
 
 //#region src/OnboardingMiniApp.tsx
 function OnboardingMiniApp({ track, progress: externalProgress, onStepComplete: externalOnStepComplete, onViewChange, initialView = "overview" }) {
@@ -88,3079 +89,9 @@ const example = {
 };
 var example_default = example;
 
-//#endregion
-//#region ../../libs/contracts/dist/docs/presentations.js
-const e = [
-	`markdown`,
-	`application/json`,
-	`application/xml`,
-	`react`
-];
-function t$27(e$1) {
-	if (!e$1.length) return `/`;
-	let t$28 = e$1.startsWith(`/`) ? e$1 : `/${e$1}`;
-	return t$28 === `/` ? `/` : t$28.replace(/\/+$/, ``);
-}
-function n$1(e$1, n$2) {
-	if (e$1.route) return t$27(e$1.route);
-	let r$2 = n$2 ?? `/docs`, i$2 = e$1.id.replace(/^docs\.?/, ``).replace(/\./g, `/`).replace(/\/+/g, `/`);
-	return t$27(i$2.startsWith(`/`) ? i$2 : `${r$2}/${i$2}`);
-}
-function r$1(e$1, t$28) {
-	return t$28 ? `${t$28}.${e$1.id}` : e$1.id;
-}
-function i$1(t$28, n$2) {
-	let i$2 = n$2?.defaultTargets ?? e, a$2 = t$28.version ?? n$2?.defaultVersion ?? 1, o$2 = t$28.stability ?? n$2?.defaultStability ?? `stable`;
-	return {
-		meta: {
-			name: r$1(t$28, n$2?.namespace),
-			version: a$2,
-			description: t$28.summary ?? t$28.title,
-			tags: t$28.tags,
-			owners: t$28.owners,
-			domain: t$28.domain,
-			stability: o$2
-		},
-		policy: t$28.visibility && t$28.visibility !== `public` ? { flags: [t$28.visibility] } : void 0,
-		source: {
-			type: `blocknotejs`,
-			docJson: t$28.body
-		},
-		targets: i$2
-	};
-}
-function a$1(e$1, t$28) {
-	let n$2 = e$1.version ?? t$28?.defaultVersion ?? 1, i$2 = e$1.stability ?? t$28?.defaultStability ?? `stable`;
-	return {
-		meta: {
-			name: r$1(e$1, t$28?.namespace),
-			version: n$2,
-			stability: i$2,
-			tags: e$1.tags,
-			owners: e$1.owners,
-			description: e$1.summary ?? e$1.title
-		},
-		content: {
-			kind: `markdown`,
-			content: e$1.body
-		}
-	};
-}
-function o$1(e$1, t$28) {
-	return e$1.map((e$2) => ({
-		block: e$2,
-		route: n$1(e$2, t$28?.routePrefix),
-		descriptor: i$1(e$2, t$28)
-	}));
-}
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/registry.js
-var n = class {
-	routes = /* @__PURE__ */ new Map();
-	constructor(e$1 = [], t$28) {
-		e$1.forEach((e$2) => this.register(e$2, t$28));
-	}
-	register(e$1, n$2) {
-		let [r$2] = o$1([e$1], n$2);
-		return r$2 && this.routes.set(e$1.id, r$2), this;
-	}
-	list() {
-		return [...this.routes.values()];
-	}
-	get(e$1) {
-		return this.routes.get(e$1);
-	}
-	toRouteTuples() {
-		return this.list().map(({ route: e$1, descriptor: t$28 }) => [e$1, t$28]);
-	}
-	toPresentationSpecs(t$28) {
-		return this.list().map(({ block: n$2 }) => a$1(n$2, t$28));
-	}
-};
-const r = [
-	`id`,
-	`title`,
-	`body`,
-	`kind`,
-	`visibility`,
-	`route`
-], i = new n();
-function a(e$1) {
-	for (let t$28 of e$1) {
-		for (let e$2 of r) if (!t$28[e$2]) throw Error(`DocBlock ${t$28.id ?? `<missing id>`} missing field ${String(e$2)}`);
-		i.register(t$28);
-	}
-}
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/PUBLISHING.docblock.js
-const t$26 = [{
-	id: `docs.PUBLISHING`,
-	title: `Publishing ContractSpec Libraries`,
-	summary: `This guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/PUBLISHING`,
-	tags: [`PUBLISHING`],
-	body: `# Publishing ContractSpec Libraries
-
-This guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).
-
-## Release Tracks
-
-| Track | Branch | npm Tag | Frequency | Versioning | Use Case |
-|-------|--------|---------|-----------|------------|----------|
-| **Stable** | \`release\` | \`latest\` | Manual | SemVer (e.g., \`1.7.4\`) | Production, external users |
-| **Canary** | \`main\` | \`canary\` | Every Push | Snapshot (e.g., \`1.7.4-canary...\`) | Dev, internal testing |
-
-## Prerequisites
-
-- ✅ \`NPM_TOKEN\` secret is configured in GitHub (owner or automation token with _publish_ scope).
-- ✅ \`GITHUB_TOKEN\` (built-in) has permissions to create PRs (enabled by default in new repos).
-- ✅ For stable releases: \`release\` branch exists and is protected.
-
-## Canary Workflow (Automatic)
-
-Every commit pushed to \`main\` triggers the \`.github/workflows/publish-canary.yml\` workflow.
-
-1. **Trigger**: Push to \`main\`.
-2. **Versioning**: Runs \`changeset version --snapshot canary\` to generate a temporary snapshot version.
-3. **Publish**: Packages are published to npm with the \`canary\` tag using \`changeset publish --tag canary\`.
-
-### Consuming Canary Builds
-
-To install the latest bleeding-edge version:
-
-\`\`\`bash
-npm install @lssm/lib.contracts@canary
-# or
-bun add @lssm/lib.contracts@canary
-\`\`\`
-
-## Stable Release Workflow (Manual)
-
-Stable releases are managed via the \`release\` branch using the standard [Changesets Action](https://github.com/changesets/action).
-
-1. **Develop on \`main\`**: Create features and fixes.
-2. **Add Changesets**: Run \`bun changeset\` to document changes and impact (major/minor/patch).
-3. **Merge to \`release\`**: When ready to ship, open a PR from \`main\` to \`release\` or merge manually.
-4. **"Version Packages" PR**:
-   - The GitHub Action detects new changesets and automatically creates a Pull Request titled **"Version Packages"**.
-   - This PR contains the version bumps and updated \`CHANGELOG.md\` files.
-5. **Merge & Publish**:
-   - Review and merge the "Version Packages" PR.
-   - The Action runs again, detects the versions have been bumped, builds the libraries, and publishes them to npm with the \`latest\` tag.
-
-### Publishing Steps
-
-1. Ensure all changesets are present on \`main\`.
-2. Merge \`main\` into \`release\`:
-   \`\`\`bash
-   git checkout release
-   git pull origin release
-   git merge main
-   git push origin release
-   \`\`\`
-3. Go to GitHub Pull Requests. You will see a **"Version Packages"** PR created by the bot.
-4. Merge that PR.
-5. The release is now live on npm!
-
-## Manual Verification (Optional)
-
-Before publishing a new version you can run:
-
-\`\`\`bash
-bun run build:not-apps
-npx npm-packlist --json packages/libs/contracts
-\`\`\`
-
-## Rollback
-
-If a publish fails mid-way, re-run the workflow once the issue is fixed. Already published packages are skipped automatically. Use \`npm deprecate <package>@<version>\` if we need to warn consumers about a broken release.
-`
-}];
-a(t$26);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/accessibility_wcag_compliance_specs.docblock.js
-const t$25 = [{
-	id: `docs.accessibility_wcag_compliance_specs`,
-	title: `Accessibility & WCAG Compliance — **specs.md**`,
-	summary: `> **Goal:** Ship interfaces that are usable by everyone, by default. This spec sets non‑negotiable rules, checklists, and CI gates to meet **WCAG\xA02.2 AA** (aim for AAA where low‑cost), align with **EN\xA0301\xA0549** (EU), and keep parity on **web (Next.js)** and **mobile (Expo/React\xA0Native)**.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/accessibility_wcag_compliance_specs`,
-	tags: [`accessibility_wcag_compliance_specs`],
-	body: `# Accessibility & WCAG Compliance — **specs.md**
-
-> **Goal:** Ship interfaces that are usable by everyone, by default. This spec sets non‑negotiable rules, checklists, and CI gates to meet **WCAG\xA02.2 AA** (aim for AAA where low‑cost), align with **EN\xA0301\xA0549** (EU), and keep parity on **web (Next.js)** and **mobile (Expo/React\xA0Native)**.
-
----
-
-## 0) Scope & Principles
-
-- **Standards:** WCAG\xA02.2\xA0AA (incl. new 2.2 SCs: Focus Not Obscured, Focus Appearance, Target Size, Dragging Movements, Accessible Authentication, Redundant Entry). EN\xA0301\xA0549 compliance by conformance to WCAG.
-- **Principles:** Perceivable, Operable, Understandable, Robust (POUR).
-- **Rule of ARIA:** “No ARIA is better than bad ARIA.” Prefer native elements.
-- **Definition of Done (DoD):** No Critical/Major a11y issues in CI; keyboard complete; SR (screen reader) smoke test passed; contrasts pass; acceptance criteria below satisfied.
-- **Repo Alignment:** Web apps use **Radix Primitives + shadcn** wrappers centralized in \`packages/lssm/libs/ui-kit-web\`. Prefer those components over per‑app duplicates (\`packages/*/apps/*/src/components/ui\`). When missing, add to \`ui-kit-web\` first, then adopt app‑side.
-
----
-
-## 1) Design Requirements (Design System & Tokens)
-
-**1.1 Color & Contrast**
-
-- Body text, icons essential to meaning: **≥\xA04.5:1**; large text (≥\xA018.66px regular / 14px bold): **≥\xA03:1**.
-- Interactive states (default/hover/active/disabled/focus) must maintain contrast **≥\xA03:1** against adjacent colors; text within components follows text ratios.
-- Provide light & dark themes with tokens that guarantee minimums. **Never rely solely on color** to convey meaning; pair with text, shape, or icon.
-
-**1.2 Focus Indicators (WCAG\xA02.4.11/12)**
-
-- Every interactive element has a **visible focus** with clear offset; indicator contrast **≥\xA03:1** vs adjacent colors and indicator **area ≥\xA02\xA0CSS\xA0px** thick.
-- Focus **must not be obscured** by sticky headers/footers or scroll containers.
-
-**1.3 Motion & Preferences**
-
-- Respect \`prefers-reduced-motion\`: suppress large parallax, auto‑animations; provide instant alternatives.
-- Avoid motion that could trigger vestibular issues; under PRM, use fade/scale under **150ms**.
-
-**1.4 Target Size (2.5.8)**
-
-- Hit areas **≥\xA024×24\xA0CSS\xA0px** (web) and **≥\xA044×44\xA0dp** (mobile) unless exempt.
-
-**1.5 Typography & Layout**
-
-- Support zoom to **400%** without loss of content/functionality; responsive reflow at **320\xA0CSS\xA0px** width.
-- Maintain clear heading hierarchy (h1…h6), one **h1** per view.
-
-- Repository baseline (Web): default body text uses Tailwind \`text-lg\` (≈18px). As of 2025‑09‑20, the repository bumped all Tailwind typography scale usages by +1 step (e.g., \`text-sm\`→\`text-base\`, \`text-base\`→\`text-lg\`, …, \`text-8xl\`→\`text-9xl\`). For long‑form content, default to \`prose-lg\`.
-- Do not use \`text-xs\` for body copy. Reserve \`text-sm\` only for non‑essential meta (timestamps, fine print) while ensuring contrast and touch targets remain compliant.
-- When increasing font size, ensure line height supports readability. Prefer Tailwind defaults or \`leading-relaxed\`/\`leading-7\` for body text where dense blocks appear.
-
-**1.6 Iconography & Imagery**
-
-- Decorative images: \`alt=""\` or \`aria-hidden="true"\`.
-- Informative images: concise, specific **alt**; complex charts require a **data table or long description**.
-
----
-
-## 2) Content Requirements (UX Writing)
-
-- Links say **what happens** (avoid “click here”).
-- Buttons start with verbs; avoid ambiguous labels.
-- Form labels are **visible**; placeholders are **not labels**.
-- Error messages: human + programmatic association; avoid color‑only.
-- Authentication: allow **copy/paste**, password managers, and avoid cognitive tests alone (**3.3.7/3.3.8/3.3.9**).
-- Avoid CAPTCHAs that block users; if unavoidable, provide **multiple alternatives** (logic-free).
-
----
-
-## 3) Engineering Requirements (Web — Next.js/React)
-
-> Use and extend \`packages/lssm/libs/ui-kit-web\` as the default UI surface. It wraps **Radix** primitives with sensible a11y defaults (focus rings, roles, keyboard, ARIA binding). When a gap exists, add it to \`ui-kit-web\` first.
-
-**3.1 Semantics & Landmarks**
-
-- Use native elements: \`<button>\`, \`<a href>\`, \`<label for>\`, \`<fieldset>\`, \`<legend>\`, \`<table>\`, etc.
-- Landmarks per page: \`header\`, \`nav\`, \`main\`, \`aside\`, \`footer\`. Provide a **Skip to main content** link.
-- Provide a **Route Announcer** (\`aria-live="polite"\`) and move focus to page **h1** after navigation.
-
-**3.2 Keyboard**
-
-- All functionality available with keyboard alone. Tab order follows DOM/visual order; **no keyboard traps**.
-- Common bindings:
-  - Space/Enter → activate button; Enter on link;
-  - Esc closes dialogs/menus;
-  - Arrow keys for lists/menus/tablists with **roving tabindex**.
-
-**3.3 Focus Management**
-
-- On route change (Next.js), move focus to the page \`<h1>\` or container and announce via a live region.
-- Dialogs/menus: **trap focus** inside; return focus to invoking control on close.
-- Don’t steal focus except after explicit user action.
-
-**3.4 Forms**
-
-- Each input has a \`<label>\` or \`aria-label\`. Group related inputs with \`<fieldset><legend>\`.
-- Associate errors via \`aria-describedby\` or inline IDs; announce with \`role="alert"\` (assertive only for critical).
-- Provide **autocomplete** tokens for known fields; show **inline validation** and do not block on **onBlur** alone.
-
-**3.5 ARIA Usage**
-
-- Only when needed; match patterns (dialog, menu, combobox, tablist, listbox) per ARIA Authoring Practices.
-- Ensure **name/role/value** are programmatically determinable.
-
-**3.6 Media**
-
-- Videos: **captions**; provide **transcripts** for audio; audio descriptions for essential visual info.
-- No auto‑playing audio. Auto‑playing video must be muted and pausable; provide controls.
-
-**3.7 Tables & Data**
-
-- Use \`<th scope>\` for headers; captions via \`<caption>\`; announce sorting via \`aria-sort\`.
-- Provide CSV/JSON export where charts are primary.
-
-**3.8 Performance & Robustness**
-
-- Avoid content shifts that move focus; reserve space or use skeletons.
-- Maintain accessible names through hydration/SSR; avoid \`dangerouslySetInnerHTML\` where possible.
-
-**3.9 Next.js specifics**
-
-- Use \`next/link\` for navigation; ensure links are **links**, not buttons.
-- \`next/image\` must include **alt** (empty if decorative).
-- Announce route changes with a **global live region** and shift focus to the new view.
-
-**3.10 Accessibility library integration**
-
-- Import \`@lssm/lib.accessibility\` at app root. It auto-imports its \`styles.css\` via the package entry; ensure bundlers keep CSS side effects. If your app tree-shakes CSS, explicitly import the stylesheet once in your root layout:
-
-\`\`\`tsx
-// app/layout.tsx
-import '@lssm/lib.accessibility'; // includes tokens and provider exports
-// or if needed: import '@lssm/lib.accessibility/src/styles.css';
-\`\`\`
-
-- Wrap the app with \`AccessibilityProvider\` and include an element with \`id="main"\` for the skip link target.
-
----
-
-## 3b) lssm/ui-kit-web — Component Patterns & Defaults
-
-> Source: \`packages/lssm/libs/ui-kit-web/ui/*\`
-
-- **Button/Input/Textarea**: Built‑in \`focus-visible\` rings; ensure visible labels via \`FormLabel\` or \`aria-label\`.
-- **Form** (\`form.tsx\`): \`FormControl\` wires \`aria-invalid\` and \`aria-describedby\` to \`FormMessage\` and \`FormDescription\`. Prefer \`FormMessage\` for inline errors. Add \`role="alert"\` only for critical.
-- **Dialog/Sheet/Dropdown**: Use Radix wrappers for focus‑trap and return‑focus. Provide \`DialogTitle\` + \`DialogDescription\` for name/description.
-- **Select/Combobox**: Prefer \`SelectTrigger\` with visible label; for icon‑only triggers, supply \`aria-label\`. Document examples in each app.
-- **Tabs**: Use \`TabsList\`, \`TabsTrigger\`, \`TabsContent\`; names are programmatically determinable.
-- **Toast/Toaster**: Prefer non‑blocking announcements; map critical to assertive region; include action buttons with clear labels.
-- **Table**: Use \`TableCaption\`; ensure \`TableHead\` cells use proper \`scope\`. Provide \`aria-sort\` on sortable headers.
-- **Utilities to add (repo action)**:
-  - \`SkipLink\` component and pattern in layouts.
-  - \`RouteAnnouncer\` (\`aria-live="polite"\`) and **FocusOnRouteChange** helper.
-  - \`VisuallyHidden\` wrapper (Radix visually-hidden or minimal utility).
-  - \`useReducedMotion\` helper; honor in animated components.
-  - Touch‑size variants (≥44×44) for interactive atoms.
-
----
-
-## 4) Engineering Requirements (Mobile — Expo/React\xA0Native)
-
-- Set \`accessibilityLabel\`, \`accessibilityHint\`, and \`accessibilityRole\` on touchables.
-- Ensure **hit slop** / min size **≥\xA044×44\xA0dp**.
-- Support Dynamic Type / font scaling; no clipped text at **200%**.
-- Respect **Invert Colors** and **Reduce Motion**; avoid flashing.
-- Group related items with \`accessibilityElements\` ordering; hide decoration with \`accessible={false}\` or \`importantForAccessibility="no-hide-descendants"\` when appropriate.
-- Test with **VoiceOver (iOS)** and **TalkBack (Android)**.
-
----
-
-## 5) Component Patterns (Acceptance Rules)
-
-**Buttons & Links**
-
-- Use \`<button>\` for actions, \`<a href>\` for navigation. Provide disabled states that are perceivable beyond color.
-
-**Navigation**
-
-- Provide **Skip link**. One primary nav landmark. Indicate current page (\`aria-current="page"\`).
-
-**Menus/Combobox/Autocomplete**
-
-- Follow ARIA patterns: focus moves into list; \`aria-expanded\`, \`aria-controls\`, \`aria-activedescendant\` when applicable; Esc closes; typing filters.
-
-**Modals/Dialogs**
-
-- \`role="dialog"\` or \`alertdialog\` with **label**; focus trapped; background inert; Esc closes; return focus to trigger.
-
-**Tabs**
-
-- \`role="tablist"\`; tabs are in the tab order; arrow keys switch focus; content is \`role="tabpanel"\` with \`aria-labelledby\`.
-
-**Toasts/Notifications**
-
-- Non-critical: \`aria-live="polite"\`; critical: \`role="alert"\` sparingly.
-
-**Infinite Scroll / “Load More”**
-
-- Provide **Load more** control; announce new content to SR; preserve keyboard position.
-
-**Drag & Drop (2.5.7)**
-
-- Provide **non‑drag** alternative (e.g., move up/down buttons).
-
-**Charts & Maps**
-
-- Provide **table alternative** or textual summary; keyboard access to datapoints where interactive.
-
----
-
-## 6) Testing & CI (Blocking Gates)
-
-**Static & Unit**
-
-- \`eslint-plugin-jsx-a11y\` — error on violations.
-- \`jest-axe\` — unit tests for components.
-
-**Automated Integration**
-
-- \`axe-core\` via Playwright or Cypress on critical flows.
-- \`pa11y-ci\` on key routes; threshold: **0 Critical / 0 Serious** to merge.
-- Lighthouse CI a11y score **≥\xA095** on target pages.
-
-**Manual QA (per release)**
-
-- **Keyboard patrol:** navigate primary flows without mouse.
-- **Screen reader smoke:** NVDA (Windows) or VoiceOver (macOS/iOS) across login, navigation, forms, dialogs.
-- **Zoom & Reflow:** 200–400% & 320\xA0px width.
-- **Color/Contrast check:** tokens in both themes.
-
-**Reporting**
-
-- A11y issues labeled: \`a11y-blocker\`, \`a11y-bug\`, \`a11y-enhancement\` with WCAG ref.
-
----
-
-## 7) Repository‑Specific Adoption Plan
-
-- Centralize UI usage on \`packages/lssm/libs/ui-kit-web\` and de‑duplicate per‑app \`components/ui\` where feasible.
-- Introduce \`SkipLink\`, \`RouteAnnouncer\`, \`FocusOnRouteChange\`, and \`VisuallyHidden\` in \`ui-kit-web\`. Adopt in app layouts (\`app/layout.tsx\`) first.
-- Add \`useReducedMotion\` and wire into animated components (e.g., \`drawer\`, \`tooltip\`, \`carousel\`).
-- Add touch‑size variants to \`Button\`, \`IconButton\`, \`TabsTrigger\`, toggles.
-- Document Select label patterns and error association in Forms.
-
----
-
-## 8) Code Snippets
-
-**Skip Link**
-
-\`\`\`html
-<a
-  class="sr-only focus:not-sr-only focus-visible:outline focus-visible:ring-4 focus-visible:ring-offset-2"
-  href="#main"
-  >Skip to main content</a
->
-<main id="main">…</main>
-\`\`\`
-
-**Dialog (Radix + shadcn/ui) — essentials**
-
-\`\`\`tsx
-// Ensure label, description, focus trap, and return focus on close remain intact
-<Dialog>
-  <DialogTrigger asChild>
-    <button aria-haspopup="dialog">Open settings</button>
-  </DialogTrigger>
-  <DialogContent aria-describedby="settings-desc">
-    <DialogTitle>Settings</DialogTitle>
-    <p id="settings-desc">Update your preferences.</p>
-    <DialogClose asChild>
-      <button>Close</button>
-    </DialogClose>
-  </DialogContent>
-</Dialog>
-\`\`\`
-
-**Form error association**
-
-\`\`\`tsx
-<label htmlFor="email">Email</label>
-<input id="email" name="email" type="email" aria-describedby="email-err" />
-<p id="email-err" role="alert">Enter a valid email.</p>
-\`\`\`
-
-**Route change announcement (Next.js)**
-
-\`\`\`tsx
-// Add once at app root
-<div
-  aria-live="polite"
-  aria-atomic="true"
-  id="route-announcer"
-  className="sr-only"
-/>
-\`\`\`
-
----
-
-## 9) Exceptions & Waivers
-
-- If a criterion cannot be met, file an issue with: context, attempted alternatives, WCAG reference, impact assessment, and a remediation date. **Temporary waivers only.**
-
----
-
-## 10) Ownership
-
-- **Design:** maintains token contrast, component specs.
-- **Engineering:** enforces CI gates, implements patterns.
-- **QA:** runs manual checks per release.
-- **PM:** blocks release if AA not met on user‑visible flows.
-
----
-
-## 11) References (internalize; no external dependency at runtime)
-
-- WCAG\xA02.2 (AA), EN\xA0301\xA0549. ARIA Authoring Practices. Platform HIG (Apple, Material).
-- \`packages/lssm/libs/ui-kit-web\` as the canonical UI source for web.
-
-> **Bottom line:** Shipping means **accessible by default**. We don’t trade a11y for speed; we bake it into speed.
-
----
-
-## 12) Adoption Status (2025-09-23)
-
-- web-artisan: AccessibilityProvider integrated; sr-only/forced-colors applied; 44x44 targets; forms announce errors; jest-axe and cypress-axe in place.
-- web-strit: AccessibilityProvider integrated; forced-colors, sr-only; forms announce errors; 44x44 targets; contrast tokens and text-scale wired; jest-axe and cypress-axe in place.
-- web-coliving: AccessibilityProvider integrated; forced-colors and focus visibility added; text-scale wired; landing pages converted to \`Section\`/stacks with text-lg defaults; CTA capture standardized; ESLint guard for text-xs in main content; jest-axe and cypress-axe in place. Next: audit icon-only controls and ensure 44x44 targets; add role="alert" where critical.
-
-> CI gates: run eslint a11y, jest-axe on components, and cypress-axe on critical flows per app.
-
----
-
-## 13) CI Hardening & Visual QA
-
-- Linting: Run eslint with jsx-a11y rules across all web apps; block on violations.
-- Unit: Run jest-axe for ui-kit-web and app-level components.
-- Integration: cypress-axe on key flows (auth, forms, dialogs, tables).
-- Synthetic scans: pa11y-ci on critical pages (0 Critical/Serious policy).
-- Performance/A11y audit: Lighthouse CI with a11y score >= 95 on target routes.
-- Artifacts: Upload pa11y and Lighthouse reports per PR; annotate failures.
-
-### Recent additions (2025-09-26)
-
-- AutocompleteInput (groceries): Upgraded to ARIA combobox pattern with \`aria-controls\`, \`aria-activedescendant\`, \`Escape\`/\`Tab\` handling, and labelled listbox.
-- Cypress a11y tests added for furniture and incidents modules on \`/modules\` and operators flows; checks run axe with critical/serious impacts.
-
-## 14) Accessibility Telemetry (PostHog)
-
-- Events (anonymized): a11y_pref_changed (text_scale, contrast_mode, reduce_motion), a11y_panel_opened.
-- Properties: app, route, previous_value, new_value, timestamp.
-- Dashboards: Adoption over time, per app/route; correlation with reduced bounce on forms.
-- Privacy: No PII; aggregate only.
-`
-}];
-a(t$25);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/PHASE_1_QUICKSTART.docblock.js
-const t$24 = [{
-	id: `docs.tech.PHASE_1_QUICKSTART`,
-	title: `Phase 1: API Reference Index`,
-	summary: `Quick reference for all new Phase 1 APIs.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/PHASE_1_QUICKSTART`,
-	tags: [`tech`, `PHASE_1_QUICKSTART`],
-	body: `# Phase 1: API Reference Index
-
-Quick reference for all new Phase 1 APIs.
-
----
-
-## @lssm/lib.multi-tenancy
-
-### RLS
-\`\`\`typescript
-import { createRlsMiddleware, type TenantIdProvider } from '@lssm/lib.multi-tenancy/rls';
-\`\`\`
-
-### Provisioning
-\`\`\`typescript
-import { 
-  TenantProvisioningService,
-  type CreateTenantInput,
-  type TenantProvisioningConfig 
-} from '@lssm/lib.multi-tenancy/provisioning';
-\`\`\`
-
-### Isolation
-\`\`\`typescript
-import { IsolationValidator } from '@lssm/lib.multi-tenancy/isolation';
-\`\`\`
-
----
-
-## @lssm/lib.observability
-
-### Tracing
-\`\`\`typescript
-import { 
-  getTracer,
-  traceAsync,
-  traceSync,
-  createTracingMiddleware 
-} from '@lssm/lib.observability/tracing';
-\`\`\`
-
-### Metrics
-\`\`\`typescript
-import {
-  getMeter,
-  createCounter,
-  createUpDownCounter,
-  createHistogram,
-  standardMetrics
-} from '@lssm/lib.observability/metrics';
-\`\`\`
-
-### Logging
-\`\`\`typescript
-import {
-  Logger,
-  logger,
-  type LogLevel,
-  type LogEntry
-} from '@lssm/lib.observability/logging';
-\`\`\`
-
----
-
-## @lssm/lib.resilience
-
-### Circuit Breaker
-\`\`\`typescript
-import {
-  CircuitBreaker,
-  type CircuitState,
-  type CircuitBreakerConfig
-} from '@lssm/lib.resilience/circuit-breaker';
-\`\`\`
-
-### Retry
-\`\`\`typescript
-import { retry } from '@lssm/lib.resilience/retry';
-\`\`\`
-
-### Timeout
-\`\`\`typescript
-import { timeout } from '@lssm/lib.resilience/timeout';
-\`\`\`
-
-### Fallback
-\`\`\`typescript
-import { fallback } from '@lssm/lib.resilience/fallback';
-\`\`\`
-
----
-
-## Enhanced: @lssm/lib.contracts
-
-### DataViews
-\`\`\`typescript
-import { DataViewQueryGenerator } from '@lssm/lib.contracts/data-views/query-generator';
-import { DataViewRuntime } from '@lssm/lib.contracts/data-views/runtime';
-\`\`\`
-
-### Workflows
-\`\`\`typescript
-import { SLAMonitor, type SLABreachEvent } from '@lssm/lib.contracts/workflow/sla-monitor';
-import { PrismaStateStore } from '@lssm/lib.contracts/workflow/adapters/db-adapter';
-\`\`\`
-
----
-
-## Enhanced: @lssm/lib.design-system
-
-### DataView Components
-\`\`\`typescript
-import { DataViewRenderer } from '@lssm/lib.design-system/components/data-view/DataViewRenderer';
-// Also available: DataViewList, DataViewTable, DataViewDetail
-\`\`\`
-
----
-
-## Usage Examples
-
-### Complete Workflow with All Features
-
-\`\`\`typescript
-import { WorkflowRunner } from '@lssm/lib.contracts/workflow/runner';
-import { PrismaStateStore } from '@lssm/lib.contracts/workflow/adapters/db-adapter';
-import { SLAMonitor } from '@lssm/lib.contracts/workflow/sla-monitor';
-import { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';
-import { traceAsync } from '@lssm/lib.observability/tracing';
-
-const runner = new WorkflowRunner({
-  registry,
-  stateStore: new PrismaStateStore(db),
-  opExecutor: async (op, input, ctx) => {
-    return traceAsync(\`op.\${op.name}\`, async (span) => {
-      span.setAttribute('operation', op.name);
-      const breaker = getCircuitBreaker(op.name);
-      return breaker.execute(() => executeOperation(op, input, ctx));
-    });
-  },
-  eventEmitter: (event, payload) => {
-    if (event.startsWith('workflow.')) {
-      logger.info(event, payload);
-    }
-  },
-});
-
-const monitor = new SLAMonitor((event, payload) => {
-  logger.warn('SLA_BREACH', payload);
-  alertOps(payload);
-});
-
-// Start workflow
-const workflowId = await runner.start('payment.flow', 1);
-
-// Monitor SLA
-const state = await runner.getState(workflowId);
-const spec = registry.get('payment.flow', 1);
-monitor.check(state, spec!);
-\`\`\`
-
-### Complete DataView with Observability
-
-\`\`\`typescript
-import { DataViewRenderer } from '@lssm/lib.design-system';
-import { DataViewQueryGenerator } from '@lssm/lib.contracts/data-views/query-generator';
-import { traceAsync } from '@lssm/lib.observability/tracing';
-import { MyDataView } from './specs/users.data-view';
-
-export function UserListPage() {
-  const [page, setPage] = useState(1);
-  const [users, setUsers] = useState([]);
-
-  const loadUsers = async () => {
-    return traceAsync('load_users', async (span) => {
-      const generator = new DataViewQueryGenerator(MyDataView);
-      const query = generator.generate({ pagination: { page, pageSize: 20 } });
-      
-      span.setAttribute('page', page);
-      const result = await api.execute(query);
-      setUsers(result.data);
-    });
-  };
-
-  return (
-    <DataViewRenderer
-      spec={MyDataView}
-      items={users}
-      pagination={{ page, pageSize: 20, total: users.length }}
-      onPageChange={setPage}
-    />
-  );
-}
-\`\`\`
-
-### Complete Multi-Tenant Setup
-
-\`\`\`typescript
-// 1. RLS Middleware
-import { createRlsMiddleware } from '@lssm/lib.multi-tenancy/rls';
-db.$use(createRlsMiddleware(() => req.tenantId));
-
-// 2. Tenant Provisioning
-import { TenantProvisioningService } from '@lssm/lib.multi-tenancy/provisioning';
-const service = new TenantProvisioningService({ db });
-
-// 3. Create new tenant
-await service.provision({
-  id: 'acme',
-  name: 'Acme Corp',
-  slug: 'acme',
-  ownerEmail: 'admin@acme.com',
-});
-
-// 4. Validate isolation in tests
-import { IsolationValidator } from '@lssm/lib.multi-tenancy/isolation';
-
-test('queries are isolated', () => {
-  const isValid = IsolationValidator.validateQuery(
-    'User',
-    'findMany',
-    { where: { tenantId: 'acme' } },
-    'acme'
-  );
-  expect(isValid).toBe(true);
-});
-\`\`\`
-
----
-
-## Testing
-
-### Test Circuit Breakers
-
-\`\`\`typescript
-import { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';
-
-test('circuit opens after threshold', async () => {
-  const breaker = new CircuitBreaker({
-    failureThreshold: 3,
-    resetTimeoutMs: 5000,
-  });
-
-  // Trigger failures
-  for (let i = 0; i < 3; i++) {
-    await expect(
-      breaker.execute(() => Promise.reject('error'))
-    ).rejects.toThrow();
-  }
-
-  // Circuit should be open
-  await expect(
-    breaker.execute(() => Promise.resolve('ok'))
-  ).rejects.toThrow('CircuitBreaker is OPEN');
-});
-\`\`\`
-
-### Test Workflow Retry
-
-\`\`\`typescript
-test('workflow retries on failure', async () => {
-  let attempts = 0;
-  const opExecutor = async () => {
-    attempts++;
-    if (attempts < 3) throw new Error('fail');
-    return 'success';
-  };
-
-  const runner = new WorkflowRunner({ /* ... */ opExecutor });
-  await runner.executeStep(workflowId);
-  
-  expect(attempts).toBe(3);
-});
-\`\`\`
-
----
-
-## Common Patterns
-
-### Pattern: Resilient External Call
-
-\`\`\`typescript
-import { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';
-import { retry } from '@lssm/lib.resilience/retry';
-import { timeout } from '@lssm/lib.resilience/timeout';
-import { traceAsync } from '@lssm/lib.observability/tracing';
-
-const breaker = new CircuitBreaker({ failureThreshold: 5, resetTimeoutMs: 30000 });
-
-export async function callExternalAPI(input: any) {
-  return traceAsync('external_api_call', async (span) => {
-    span.setAttribute('service', 'stripe');
-    
-    return breaker.execute(() =>
-      retry(
-        () => timeout(() => stripe.api.call(input), 5000),
-        3,
-        1000,
-        true
-      )
-    );
-  });
-}
-\`\`\`
-
-**Benefits**: Circuit breaker + retry + timeout + tracing in one place.
-
----
-
-### Pattern: Tenant-Aware Operation
-
-\`\`\`typescript
-import { traceAsync } from '@lssm/lib.observability/tracing';
-
-export async function listUsers(tenantId: string) {
-  return traceAsync('list_users', async (span) => {
-    span.setAttribute('tenant_id', tenantId);
-    
-    // RLS middleware will inject WHERE tenantId = ?
-    return db.user.findMany();
-  });
-}
-\`\`\`
-
----
-
-### Pattern: Monitored Workflow
-
-\`\`\`typescript
-import { WorkflowRunner } from '@lssm/lib.contracts/workflow/runner';
-import { SLAMonitor } from '@lssm/lib.contracts/workflow/sla-monitor';
-import { logger } from '@lssm/lib.observability/logging';
-
-const monitor = new SLAMonitor((event, payload) => {
-  logger.warn('workflow.sla_breach', payload);
-});
-
-// In workflow poller
-const state = await runner.getState(workflowId);
-const spec = registry.get(state.workflowName, state.workflowVersion);
-if (spec) {
-  monitor.check(state, spec);
-}
-\`\`\`
-
----
-
-## Next Steps
-
-1. **Implement one quick win** (30 minutes)
-2. **Add tests for new functionality** (1 hour)
-3. **Deploy to staging and verify observability** (1 hour)
-4. **Roll out to production** (monitor closely)
-5. **Read full documentation** at https://contractspec.lssm.tech/docs
-
----
-
-**Questions?** See \`/docs/guides/phase-1-migration\` or reach out via https://contractspec.lssm.tech/contact
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-`
-}];
-a(t$24);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/PHASE_2_AI_NATIVE_OPERATIONS.docblock.js
-const t$23 = [{
-	id: `docs.tech.PHASE_2_AI_NATIVE_OPERATIONS`,
-	title: `Phase 2: AI-Native Operations`,
-	summary: `_Last updated: 2025-11-20_`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/PHASE_2_AI_NATIVE_OPERATIONS`,
-	tags: [`tech`, `PHASE_2_AI_NATIVE_OPERATIONS`],
-	body: `# Phase 2: AI-Native Operations
-
-_Last updated: 2025-11-20_
-
-Phase 2 turns ContractSpec into an AI-first operations stack. The new libraries below are the building blocks used by support bots, growth agents, and human-in-the-loop flows.
-
-## Libraries
-
-### @lssm/lib.ai-agent
-
-- **Spec + Registry**: \`defineAgent\`, \`AgentRegistry\` keep agent definitions type-safe.
-- **Runner**: \`AgentRunner\` drives LLM conversations, tool calls, retries, escalation, and telemetry hooks.
-- **Tools**: \`ToolExecutor\` standardizes schema validation + timeouts.
-- **Memory**: \`InMemoryAgentMemory\` + interfaces for plugging persistent stores.
-- **Approvals**: new \`ApprovalWorkflow\` + \`InMemoryApprovalStore\` capture low-confidence decisions and surface them to reviewers.
-
-### @lssm/lib.support-bot
-
-Composable support automation primitives:
-
-- \`TicketClassifier\` → heuristics + optional LLM validation for category, priority, sentiment.
-- \`TicketResolver\` → RAG pipeline backed by knowledge spaces.
-- \`AutoResponder\` → tone-aware drafts with citations.
-- \`SupportFeedbackLoop\` → tracks resolution rates.
-- \`createSupportTools\` → ready-made tool definitions for AgentRunner.
-
-### @lssm/lib.content-gen
-
-Content generators that consume a \`ContentBrief\` and output production-ready assets:
-
-- \`BlogGenerator\`, \`LandingPageGenerator\`, \`EmailCampaignGenerator\`, \`SocialPostGenerator\`.
-- \`SeoOptimizer\` builds metadata + schema markup.
-
-### @lssm/lib.analytics
-
-Queryless analytics helpers:
-
-- \`FunnelAnalyzer\` – conversion/drop-off per step.
-- \`CohortTracker\` – retention + LTV per cohort.
-- \`ChurnPredictor\` – recency/frequency/error scoring.
-- \`GrowthHypothesisGenerator\` – surfaces experiment ideas from metric trends.
-
-### @lssm/lib.growth
-
-A/B testing toolkit:
-
-- \`ExperimentRegistry\` + \`ExperimentRunner\` – deterministic bucketing.
-- \`ExperimentTracker\` – persist exposures + metrics.
-- \`StatsEngine\` – Welch’s t-test + improvement calculations.
-
-### Human-in-the-loop UI
-
-\`@lssm/lib.design-system\` now exposes:
-
-- \`ApprovalQueue\` – list + act on pending approvals.
-- \`AgentMonitor\` – live view of agent sessions with confidence + status.
-
-## Examples
-
-- \`examples/ai-support-bot/setup.ts\` shows ticket classification → resolution → response draft.
-- \`examples/content-generation/generate.ts\` produces blog, landing, email, social, SEO output from one brief.
-
-## Next Steps
-
-1. Wire these libraries into vertical apps (H-Circle, ArtisanOS, etc.).
-2. Add background workers that consume the new analytics/growth trackers.
-3. Expand web-landing to highlight these Phase 2 capabilities (see separate TODO).
-`
-}];
-a(t$23);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/PHASE_3_AUTO_EVOLUTION.docblock.js
-const t$22 = [{
-	id: `docs.tech.PHASE_3_AUTO_EVOLUTION`,
-	title: `Phase 3: Auto-Evolution Technical Notes`,
-	summary: `**Status**: In progress`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/PHASE_3_AUTO_EVOLUTION`,
-	tags: [`tech`, `PHASE_3_AUTO_EVOLUTION`],
-	body: `# Phase 3: Auto-Evolution Technical Notes
-
-**Status**: In progress  
-**Last updated**: 2025-11-21  
-
-Phase 3 introduces self-learning capabilities that analyze production telemetry, suggest new specs, safely roll out variants, and generate golden tests from real traffic. This document captures the main building blocks delivered in this iteration.
-
----
-
-## 1. Libraries
-
-### @lssm/lib.evolution
-
-- \`SpecAnalyzer\` converts raw telemetry samples into usage stats + anomalies.
-- \`SpecGenerator\` produces \`SpecSuggestion\` objects and validates confidence thresholds.
-- \`SpecSuggestionOrchestrator\` routes proposals through the AI approval workflow and writes approved specs to \`packages/libs/contracts/src/generated\`.
-- Storage adapters:
-  - \`InMemorySpecSuggestionRepository\` for tests.
-  - \`PrismaSpecSuggestionRepository\` persists to the new Prisma model (see §4).
-  - \`FileSystemSuggestionWriter\` emits JSON envelopes for git review.
-
-### @lssm/lib.observability
-
-- Added intent detection modules:
-  - \`IntentAggregator\` batches telemetry into rolling windows.
-  - \`IntentDetector\` surfaces latency/error/throughput regressions and sequential intents.
-- \`EvolutionPipeline\` orchestrates aggregation → detection → intent events and exposes hooks for downstream orchestrators.
-- \`createTracingMiddleware\` now accepts \`resolveOperation\`/\`onSample\` hooks to feed telemetry samples into the pipeline.
-
-### @lssm/lib.growth
-
-- New \`spec-experiments\` module:
-  - \`SpecExperimentRegistry\`, \`SpecExperimentRunner\`, \`SpecExperimentAdapter\`.
-  - \`SpecExperimentAnalyzer\` + \`SpecExperimentController\` handle guardrails and staged rollouts.
-  - Helper \`createSpecVariantResolver\` plugs directly into \`HandlerCtx.specVariantResolver\`.
-- \`SpecVariantResolver\` is now a first-class concept in \`@lssm/lib.contracts\`. The runtime will attempt to execute variant specs before falling back to the registered handler.
-
-### @lssm/lib.testing
-
-- \`TrafficRecorder\` + \`TrafficStore\` capture production requests with sampling and sanitization hooks.
-- \`GoldenTestGenerator\` converts \`TrafficSnapshot\`s into Vitest/Jest suites.
-- \`generateVitestSuite\` / \`generateJestSuite\` output self-contained test files, and \`runGoldenTests\` offers a programmatic harness for CI pipelines.
-
----
-
-## 2. Telemetry → Intent → Spec Pipeline
-
-1. \`createTracingMiddleware({ onSample })\` emits \`TelemetrySample\`s for every HTTP request.
-2. \`IntentAggregator\` groups samples into statistical windows (default 15 minutes).
-3. \`IntentDetector\` raises signals for:
-   - Error spikes
-   - Latency regressions
-   - Throughput drops
-   - Sequential workflows that hint at missing specs
-4. \`EvolutionPipeline\` emits \`intent.detected\` events and hands them to \`SpecGenerator\`.
-5. \`SpecSuggestionOrchestrator\` persists suggestions, triggers approval workflows, and—upon approval—writes JSON envelopes to \`packages/.../contracts/src/generated\`.
-
----
-
-## 3. Spec Experiments & Rollouts
-
-1. Register spec experiments in \`SpecExperimentRegistry\` with control + variant bindings.
-2. Expose bucketed specs by attaching \`createSpecVariantResolver\` to \`HandlerCtx.specVariantResolver\` inside adapters.
-3. Record outcomes via \`SpecExperimentAdapter.trackOutcome()\` (latency + error metrics).
-4. \`SpecExperimentController\` uses guardrails from config and \`SpecExperimentAnalyzer\` to:
-   - Auto-rollback on error/latency breaches.
-   - Advance rollout stages (1% → 10% → 50% → 100%) when metrics stay green.
-
----
-
-## 4. Data Models (Prisma)
-
-File: \`packages/libs/database/prisma/schema.prisma\`
-
-- \`SpecSuggestion\` – stores serialized suggestion payloads + statuses.
-- \`IntentSnapshot\` – captured detector output for auditing/training.
-- \`TrafficSnapshot\` – persisted production traffic (input/output/error blobs).
-- \`SpecExperiment\` / \`SpecExperimentMetric\` – rollout state + metrics for each variant.
-
-> Run \`bun database generate\` after pulling to refresh the Prisma client.
-
----
-
-## 5. Golden Test Workflow
-
-1. Capture traffic via middleware or direct \`TrafficRecorder.record\`.
-2. Use the new CLI command to materialize suites:
-
-\`\`\`bash
-contractspec test generate \\
-  --operation billing.createInvoice \\
-  --output tests/billing.createInvoice.golden.test.ts \\
-  --runner-import ./tests/run-operation \\
-  --runner-fn runBillingCommand \\
-  --from-production \\
-  --days 7 \\
-  --sample-rate 0.05
-\`\`\`
-
-3. Generated files import your runner and assert against recorded outputs (or expected errors for negative paths).
-
----
-
-## 6. Operational Notes
-
-- **Approvals**: By default, every suggestion still requires human approval. \`EvolutionConfig.autoApproveThreshold\` can be tuned per environment but should remain conservative (<0.3) until OverlaySpec tooling lands.
-- **Sampling**: Keep \`TrafficRecorder.sampleRate\` ≤ 0.05 in production to avoid sensitive payload storage; scrub PII through the \`sanitize\` callback before persistence.
-- **Rollouts**: Guardrails default to 5% error-rate and 750ms P99 latency. Override per experiment to match SLOs.
-
----
-
-## 7. Next Steps
-
-1. Wire \`SpecExperimentAdapter.trackOutcome\` into adapters (REST, GraphQL, Workers) so every execution logs metrics automatically.
-2. Add a UI for reviewing \`SpecSuggestion\` objects alongside approval status.
-3. Expand \`TrafficRecorder\` to ship directly to the Prisma-backed store (currently in-memory by default).
-4. Integrate \`EvolutionPipeline\` events with the Regenerator to close the loop (auto-open proposals + attach evidence).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-`
-}];
-a(t$22);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/PHASE_4_PERSONALIZATION_ENGINE.docblock.js
-const t$21 = [{
-	id: `docs.tech.PHASE_4_PERSONALIZATION_ENGINE`,
-	title: `Phase 4: Personalization Engine`,
-	summary: `**Status**: Complete`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/PHASE_4_PERSONALIZATION_ENGINE`,
-	tags: [`tech`, `PHASE_4_PERSONALIZATION_ENGINE`],
-	body: `# Phase 4: Personalization Engine
-
-**Status**: Complete  
-**Last updated**: 2025-11-21
-
-Phase 4 unlocks tenant-scoped personalization with zero bespoke code. We shipped three new libraries, a signing-aware Overlay editor, and the persistence layer required to observe usage and apply overlays safely.
-
----
-
-## 1. Libraries
-
-### @lssm/lib.overlay-engine
-
-- OverlaySpec types + validator mirror the public spec.
-- Cryptographic signer (\`ed25519\`, \`rsa-pss-sha256\`) with canonical JSON serialization.
-- Registry that merges tenant/role/user/device overlays with predictable specificity.
-- React hooks (\`useOverlay\`, \`useOverlayFields\`) for client-side rendering.
-- Runtime engine audits every applied overlay for traceability.
-
-### @lssm/lib.personalization
-
-- Behavior tracker buffers field/feature/workflow events and exports OTel metrics.
-- Analyzer summarizes field usage and workflow drop-offs into actionable insights.
-- Adapter translates insights into overlay suggestions or workflow tweaks.
-- In-memory store implementation + interface for plugging Prisma/ClickHouse later.
-
-### @lssm/lib.workflow-composer
-
-- \`WorkflowComposer\` merges base workflows with tenant/role/device extensions.
-- Step injection utilities keep transitions intact and validate anchor steps.
-- Template helpers for common tenant review/approval, plus merge helpers for multi-scope extensions.
-
----
-
-## 2. Overlay Editor App
-
-Path: \`packages/apps/overlay-editor\`
-
-- Next.js App Router UI for toggling field visibility, renaming labels, and reordering lists.
-- Live JSON preview powered by \`defineOverlay\`.
-- Server action that signs overlays via PEM private keys (Ed25519 by default) using the overlay engine signer.
-
----
-
-## 3. Persistence
-
-Added Prisma models (see \`packages/libs/database/prisma/schema.prisma\`):
-
-- \`UserBehaviorEvent\` – field/feature/workflow telemetry.
-- \`OverlaySigningKey\` – tenant managed signing keys with revocation timestamps.
-- \`Overlay\` – stored overlays (tenant/user/role/device scope) plus signature metadata.
-
----
-
-## 4. Integration Steps
-
-1. Track usage inside apps via \`createBehaviorTracker\`.
-2. Periodically run \`BehaviorAnalyzer.analyze\` to generate insights.
-3. Convert insights into OverlaySpecs or Workflow extensions.
-4. Register tenant overlays in \`OverlayRegistry\` and serve via presentation runtimes.
-5. Compose workflows per tenant using \`WorkflowComposer\`.
-
-See the \`docs/tech/personalization/*\` guides for concrete examples.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-`
-}];
-a(t$21);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS.docblock.js
-const t$20 = [{
-	id: `docs.tech.PHASE_5_ZERO_TOUCH_OPERATIONS`,
-	title: `Phase 5: Zero-Touch Operations`,
-	summary: `**Status**: In progress`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS`,
-	tags: [`tech`, `PHASE_5_ZERO_TOUCH_OPERATIONS`],
-	body: "# Phase 5: Zero-Touch Operations\n\n**Status**: In progress  \n**Last updated**: 2025-11-21\n\nPhase 5 delivers progressive delivery, SLO intelligence, cost attribution, and anomaly-driven remediation so the platform can deploy continuously without pager rotations.\n\n---\n\n## 1. New Libraries\n\n### @lssm/lib.progressive-delivery\n- `DeploymentStrategy` types capture canary vs blue-green rollouts.\n- `CanaryController` + `CanaryAnalyzer` orchestrate stage evaluation against telemetry thresholds.\n- `TrafficShifter` keeps stable/candidate splits in sync with feature-flag or router state.\n- `DeploymentCoordinator` drives stage progression, emits events, and triggers rollbacks.\n- `RollbackManager` encapsulates safe revert hooks (spec version revert, traffic shift, etc.).\n\n### @lssm/lib.slo\n- Declarative `SLODefinition` with latency + availability targets per capability/spec.\n- `SLOTracker` stores rolling snapshots + error budget positions.\n- `BurnRateCalculator` implements multi-window burn computations (fast vs slow burn).\n- `SLOMonitor` pushes incidents to Ops tooling automatically when burn exceeds thresholds.\n\n### @lssm/lib.cost-tracking\n- `CostTracker` normalizes DB/API/compute metrics into per-operation cost totals.\n- `BudgetAlertManager` raises tenant budget warnings (80% default) with contextual payloads.\n- `OptimizationRecommender` suggests batching, caching, or contract tweaks to cut spend.\n\n### Observability Anomaly Toolkit\n- `BaselineCalculator` establishes rolling intent metrics (latency, error rate, throughput).\n- `AnomalyDetector` flags spikes/drops via relative deltas after 10+ samples.\n- `RootCauseAnalyzer` correlates anomalies with recent deployments.\n- `AlertManager` deduplicates notifications and feeds MCP/SRE transports.\n\n---\n\n## 2. Data Model Additions\n\nFile: `packages/libs/database/prisma/schema.prisma`\n\n| Model | Purpose |\n| --- | --- |\n| `SLODefinition`, `SLOSnapshot`, `ErrorBudget`, `SLOIncident` | Persist definitions, rolling windows, and incidents. |\n| `OperationCost`, `TenantBudget`, `CostAlert`, `OptimizationSuggestion` | Track per-operation costs, budgets, and generated recommendations. |\n| `Deployment`, `DeploymentStage`, `RollbackEvent` | Audit progressive delivery runs and automated rollbacks. |\n| `MetricBaseline`, `AnomalyEvent` | Store computed baselines and anomaly evidence for training/analytics. |\n\nRun `bun database generate` after pulling to refresh the Prisma client.\n\n---\n\n## 3. Operational Flow\n\n1. **Deploy**: Define a `DeploymentStrategy` and feed telemetry via `@lssm/lib.observability`. Canary stages run automatically.\n2. **Protect**: `CanaryAnalyzer` evaluates error rate + latency thresholds. Failures trigger `RollbackManager`.\n3. **Observe**: `SLOMonitor` consumes snapshots and opens incidents when burn rate exceeds thresholds.\n4. **Optimize**: `CostTracker` aggregates spend per tenant + capability, while `OptimizationRecommender` surfaces fixes.\n5. **Detect**: Anomaly signals route to `RootCauseAnalyzer`, which links them to specific deployments for auto-rollback.\n\n---\n\n## 4. Integration Checklist\n\n1. Instrument adapters with `createTracingMiddleware({ onSample })` to feed metric points into `AnomalyDetector`.\n2. Register SLOs per critical operation (`billing.charge`, `knowledge.search`) and wire monitors to Ops notifications.\n3. Attach `CostTracker.recordSample` to workflow runners (DB instrumentation + external call wrappers).\n4. Store deployment metadata using the new Prisma models for auditing + UI surfacing.\n5. Update `@lssm/app.ops-console` (next iteration) to list deployments, SLO status, costs, and anomalies in one timeline.\n\n---\n\n## 5. Next Steps\n\n- Wire `DeploymentCoordinator` into the Contracts CLI so `contractspec deploy` can run staged rollouts.\n- Add UI for SLO dashboards (burn rate sparkline + incident feed).\n- Ship budget suggestions into Growth Agent for automated cost optimizations.\n- Connect `AnomalyEvent` stream to MCP agents for root-cause playbooks.\n"
-}];
-a(t$20);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/lifecycle-stage-system.docblock.js
-const t$19 = [{
-	id: `docs.tech.lifecycle-stage-system`,
-	title: `ContractSpec Lifecycle Stage System – Technical Design`,
-	summary: `This document describes how ContractSpec implements lifecycle detection and guidance. It covers architecture, module boundaries, scoring heuristics, and integration points so libraries, modules, bundles, and Studio surfaces stay synchronized.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/lifecycle-stage-system`,
-	tags: [`tech`, `lifecycle-stage-system`],
-	body: `## ContractSpec Lifecycle Stage System – Technical Design
-
-This document describes how ContractSpec implements lifecycle detection and guidance. It covers architecture, module boundaries, scoring heuristics, and integration points so libraries, modules, bundles, and Studio surfaces stay synchronized.
-
----
-
-### 1. Architecture Overview
-
-\`\`\`
-┌──────────────────────┐
-│ @lssm/lib.lifecycle  │  Types, enums, helpers (pure data)
-└───────────┬──────────┘
-            │
-┌───────────▼──────────┐    ┌───────────────────────────┐
-│ modules/lifecycle-   │    │ modules/lifecycle-advisor  │
-│ core (detection)     │    │ (guidance & ceremonies)    │
-└───────────┬──────────┘    └───────────┬───────────────┘
-            │                           │
-            ├────────────┬──────────────┤
-            ▼            ▼              ▼
-  Adapters: analytics, intent, questionnaires
-            │
-┌───────────▼──────────┐
-│ bundles/lifecycle-   │  Managed service for Studio
-│ managed              │  (REST handlers, AI agent)     │
-└───────────┬──────────┘
-            │
-  ContractSpec Studio surfaces
-  (web/mobile APIs, CLI, docs)
-\`\`\`
-
-- **Libraries** provide shared vocabulary.
-- **Modules** encapsulate logic, accepting adapters to avoid environment-specific code.
-- **Bundles** compose modules, register agents/events, and expose APIs for Studio.
-- **Apps** (web-landing, future Studio views) consume bundle APIs; they do not reimplement logic. For web-landing we now resolve \`@lssm/bundle.contractspec-studio\` and \`@lssm/lib.database-contractspec-studio\` directly from their \`packages/.../src\` folders via \`tsconfig\` path aliases so Prisma stays on the server build and Turbopack no longer pulls the prebundled \`dist\` artifacts into client chunks.
-
----
-
-### 2. Core Library (\`@lssm/lib.lifecycle\`)
-
-- Stage enum (0–6) with metadata (\`question\`, \`signals\`, \`traps\`).
-- Axes types (\`ProductPhase\`, \`CompanyPhase\`, \`CapitalPhase\`).
-- \`LifecycleSignal\` (source, metric, value, timestamp).
-- \`LifecycleMetricSnapshot\` (aggregated numbers).
-- \`LifecycleMilestone\`, \`LifecycleAction\`, \`LifecycleAssessment\` interfaces.
-- Utility helpers:
-  - \`formatStageSummary(stage, assessment)\`
-  - \`rankStageCandidates(scores)\`
-
-The library exports **no runtime dependencies** so it can be imported from apps, modules, and bundles alike.
-
----
-
-### 3. Lifecycle Core Module
-
-**Location:** \`packages/modules/lifecycle-core/\`
-
-#### Components
-1. **StageSignalCollector**
-   - Accepts adapter interfaces:
-     - \`AnalyticsAdapter\` (pulls metrics from \`@lssm/lib.analytics\` or fixture streams).
-     - \`IntentAdapter\` (hooks into \`@lssm/lib.observability\` intent detectors or logs).
-     - \`QuestionnaireAdapter\` (loads JSON questionnaires and responses).
-   - Produces normalized \`LifecycleSignal[]\`.
-
-2. **StageScorer**
-   - Weighted scoring model:
-     - Base weight per stage (reflecting expected maturity).
-     - Feature weights (retention, revenue, team size, qualitative feedback).
-     - Confidence computed via variance of contributing signals.
-   - Supports pluggable scoring matrices via JSON config.
-   - Accepts sparse metric snapshots; the orchestrator sanitizes metrics to numeric-only records before persisting assessments so downstream analytics stay consistent.
-
-3. **LifecycleOrchestrator**
-   - Coordinates collectors + scorer.
-   - Returns \`LifecycleAssessment\` with:
-     - \`stage\`, \`confidence\`, \`axisSnapshot\`, \`signalsUsed\`.
-     - Recommended focus areas (high-level categories only).
-   - Emits events (internally) when stage confidence crosses thresholds (consumed later by bundle).
-
-4. **LifecycleMilestonePlanner**
-   - Loads \`milestones-catalog.json\` (no DB).
-   - Filters upcoming milestones per stage + axis.
-   - Tracks completion using provided IDs (caller persists).
-
-#### Data Files
-- \`configs/stage-weights.json\`
-- \`configs/milestones-catalog.json\`
-- \`questionnaires/stage-readiness.json\`
-
-#### Extension Hooks
-- All adapters exported as TypeScript interfaces.
-- Implementations for analytics/intent can live in bundles or apps without modifying module code.
-
----
-
-### 4. Lifecycle Advisor Module
-
-**Location:** \`packages/modules/lifecycle-advisor/\`
-
-#### Components
-1. **LifecycleRecommendationEngine**
-   - Consumes \`LifecycleAssessment\`.
-   - Maps gaps to \`LifecycleAction[]\` using rule tables (\`stage-playbooks.ts\`).
-   - Supports override hooks for customer-specific rules.
-
-2. **ContractSpecLibraryRecommender**
-   - Maintains mapping from stage → recommended libraries/modules/bundles.
-   - Returns prioritized list with rationale and adoption prerequisites.
-
-3. **LifecycleCeremonyDesigner**
-   - Provides textual/structural data for ceremonies (title, copy, animation cues, soundtrack references).
-   - Ensures low-tech friendly instructions (clear copy, undo guidance).
-
-4. **AI Hooks**
-   - Defines prompt templates and tool manifests for lifecycle advisor agents (consumed by bundles).
-   - Keeps actual LLM integration outside module.
-
----
-
-### 5. Managed Bundle (\`lifecycle-managed\`)
-
-**Responsibilities**
-- Wire modules together.
-- Provide HTTP/GraphQL handlers (exact transport optional).
-- Register LifecycleAdvisorAgent via \`@lssm/lib.ai-agent\`.
-- LifecycleAdvisorAgent meta: domain \`operations\`, owners \`team-lifecycle\`, stability \`experimental\`, tags \`guide/lifecycle/ops\` so ops tooling can route incidents quickly.
-- Emit lifecycle events through \`@lssm/lib.bus\` + \`@lssm/lib.analytics\`.
-- Integrate with \`contractspec-studio\` packages:
-  - Use Studio contracts for authentication/tenant context (without accessing tenant DBs).
-  - Store assessments in Studio-managed storage abstractions (in-memory or file-based for now).
-
-**APIs**
-- \`POST /lifecycle/assessments\`: Accepts metrics + optional questionnaire answers. Returns \`LifecycleAssessment\`.
-- \`GET /lifecycle/playbooks/:stage\`: Returns stage playbook + ceremonies.
-- \`POST /lifecycle/advise\`: Invokes LifecycleAdvisorAgent with context.
-
-**Events**
-- \`LifecycleAssessmentCreated\`
-- \`LifecycleStageChanged\`
-- \`LifecycleGuidanceConsumed\`
-
----
-
-### 6. Library Enhancements
-
-| Library | Enhancement |
-| --- | --- |
-| \`@lssm/lib.analytics\` | Lifecycle metric collectors, helper to emit stage events, adapter implementation used by \`StageSignalCollector\`. |
-| \`@lssm/lib.evolution\` | Accepts \`LifecycleContext\` when ranking spec anomalies/suggestions. |
-| \`@lssm/lib.growth\` | Stage-specific experiment templates + guardrails referencing lifecycle enums. |
-| \`@lssm/lib.observability\` | Lifecycle KPI pipeline definitions (drift detection, regression alerts). |
-
-Each enhancement must import stage types from \`@lssm/lib.lifecycle\`.
-
----
-
-### 7. Feature Flags & Progressive Delivery
-
-- Add new flags in progressive-delivery library:
-  - \`LIFECYCLE_DETECTION_ALPHA\`
-  - \`LIFECYCLE_ADVISOR_ALPHA\`
-  - \`LIFECYCLE_MANAGED_SERVICE\`
-- Bundles/modules should check flags before enabling workflows.
-- Flags referenced in docs + Studio UI to avoid accidental exposure.
-
----
-
-### 8. Analytics & Telemetry
-
-- Events defined in analytics library; consumed by bundle/app:
-  - \`lifecycle_assessment_run\`
-  - \`lifecycle_stage_changed\`
-  - \`lifecycle_guidance_consumed\`
-- Observability pipeline includes:
-  - Composite lifecycle health metric (weighted sum of KPIs).
-  - Drift detection comparing stage predictions over time.
-  - Alert manager recipes for regression (e.g., PMF drop).
-
----
-
-### 9. Testing Strategy
-
-1. **Unit**
-   - StageScorer weight matrix.
-   - RecommendationEngine mapping.
-   - Library recommender stage coverage.
-
-2. **Contract**
-   - Adapters: ensure mock adapters satisfy interfaces.
-   - Bundles: ensure HTTP handlers respect request/response contracts even without persistence.
-
-3. **Integration**
-   - CLI example runs detection + guidance end-to-end on fixture data.
-   - Dashboard example renders assessments, verifying JSON structures remain stable.
-
----
-
-### 10. Implementation Checklist
-
-- [ ] Documentation (product, tech, ops, user).
-- [ ] Library creation (\`@lssm/lib.lifecycle\`).
-- [ ] Modules (\`lifecycle-core\`, \`lifecycle-advisor\`).
-- [ ] Bundle (\`lifecycle-managed\`) + Studio wiring.
-- [ ] Library enhancements (analytics/evolution/growth/observability).
-- [ ] Examples (CLI + dashboard).
-- [ ] Feature flags + telemetry.
-- [ ] Automated tests + fixtures.
-
-Keep this document in sync as modules evolve. When adding new stages or axes, update \`@lssm/lib.lifecycle\` first, then cascade to adapters, then refresh docs + Studio copy.*** End Patch*** End Patch
-
-
-`
-}];
-a(t$19);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/presentation-runtime.docblock.js
-const t$18 = [{
-	id: `docs.tech.presentation-runtime`,
-	title: `Presentation Runtime`,
-	summary: `Cross-platform runtime for list pages and presentation flows.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/presentation-runtime`,
-	tags: [`tech`, `presentation-runtime`],
-	body: "## Presentation Runtime\n\nCross-platform runtime for list pages and presentation flows.\n\n### Packages\n\n- `@lssm/lib.presentation-runtime-core`: shared types and config helpers\n- `@lssm/lib.presentation-runtime-react`: React hooks (web/native-compatible API)\n- `@lssm/lib.presentation-runtime-react-native`: Native entrypoint (re-exports React API for now)\n\n### Next.js config helper\n\n```ts\n// next.config.mjs\nimport { withPresentationNextAliases } from '@lssm/lib.presentation-runtime-core/next';\n\nconst nextConfig = {\n  webpack: (config) => withPresentationNextAliases(config),\n};\n\nexport default nextConfig;\n```\n\n### Metro config helper\n\n```js\n// metro.config.js (CJS)\nconst { getDefaultConfig } = require('expo/metro-config');\nconst {\n  withPresentationMetroAliases,\n} = require('@lssm/lib.presentation-runtime-core/src/metro.cjs');\n\nconst projectRoot = __dirname;\nconst config = getDefaultConfig(projectRoot);\n\nmodule.exports = withPresentationMetroAliases(config);\n```\n\n### React hooks\n\n- `useListCoordinator`: URL + RHF + derived variables (no fetching)\n- `usePresentationController`: Same plus `fetcher` integration\n- `DataViewRenderer` (design-system): render `DataViewSpec` projections (`list`, `table`, `detail`, `grid`) using shared UI atoms\n\nBoth accept a `useUrlState` adapter. On web, use `useListUrlState` (design-system) or a Next adapter.\n\n### KYC molecules (bundle)\n\n- `ComplianceBadge` in `@lssm/bundle.strit/presentation/components/kyc` renders a status badge for KYC/compliance snapshots. It accepts a `state` (missing_core | incomplete | complete | expiring | unknown) and optional localized `labels`. Prefer consuming apps to pass translated labels (e.g., via `useT('appPlatformAdmin')`).\n\n### Markdown routes and llms.txt\n\n- Each web app exposes `/llms` (and `/llms.txt`, `/llms.md`) via rewrites. See [llmstxt.org](https://llmstxt.org/).\n- Catch‑all markdown handler lives at `app/[...slug].md/route.ts`. It resolves a page descriptor from `app/.presentations.manifest.json` and renders via the `presentations.v2` engine (target: `markdown`).\n- Per‑page companion convention: add `app/<route>/ai.ts` exporting a `PresentationDescriptorV2`.\n- Build‑time tool: `tools/generate-presentations-manifest.mjs <app-root>` populates the manifest.\n- CI check: `pnpm llms:check` verifies coverage (% of pages with descriptors) and fails if below threshold.\n"
-}];
-a(t$18);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/auth/better-auth-nextjs.docblock.js
-const t$17 = [{
-	id: `docs.tech.auth.better-auth-nextjs`,
-	title: `Better Auth + Next.js integration (ContractSpec)`,
-	summary: `How ContractSpec wires Better Auth into Next.js (server config, client singleton, and proxy cookie-only redirects).`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/auth/better-auth-nextjs`,
-	tags: [
-		`auth`,
-		`better-auth`,
-		`nextjs`,
-		`cookies`,
-		`proxy`,
-		`hmr`
-	],
-	body: `# Better Auth + Next.js integration (ContractSpec)
-
-This repo uses Better Auth as the primary auth layer (sessions, organizations, teams, API keys, and OAuth).
-
-## Server config (Better Auth)
-
-- Source: \`packages/bundles/contractspec-studio/src/application/services/auth.ts\`
-- Important: \`nextCookies()\` must be the **last** plugin in the Better Auth plugin list so \`Set-Cookie\` is applied correctly in Next.js environments.
-
-## Better Auth Admin plugin
-
-ContractSpec Studio enables the Better Auth **Admin plugin** to support platform-admin user operations (list users, impersonation, etc.).
-
-- Server: \`admin()\` plugin in \`packages/bundles/contractspec-studio/src/application/services/auth.ts\`
-- Client: \`adminClient()\` in \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.ts\`
-
-### PLATFORM_ADMIN ⇒ Better Auth admin role
-
-Better Auth Admin endpoints authorize via \`user.role\`. ContractSpec enforces an org-driven rule:
-
-- If the **active organization** has \`type = PLATFORM_ADMIN\`, the signed-in user is ensured to have \`User.role\` containing \`admin\`.
-- This is applied in the session creation hook and re-checked in \`assertsPlatformAdmin()\`.
-
-This keeps admin enablement deterministic and avoids manual role backfills.
-
-## Client config (React web + Expo)
-
-To avoid duplicate background refresh/polling loops in dev (Fast Refresh/HMR), the Better Auth client is implemented as a singleton cached on \`globalThis\`.
-
-- Web client: \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.ts\`
-- Native client: \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.native.ts\`
-
-Import guidance:
-
-- If you only need the context/hook, prefer importing from \`@lssm/bundle.contractspec-studio/presentation/providers/auth\`.
-- If you explicitly need the Better Auth client instance (e.g. admin impersonation, direct API calls), import from \`@lssm/bundle.contractspec-studio/presentation/providers/auth/client\`.
-
-## Public routes (login / signup)
-
-Public auth pages should avoid eager \`authClient\` initialization.
-
-Pattern used:
-
-- In the submit handler, dynamically import \`@lssm/bundle.contractspec-studio/presentation/providers/auth/index.web\` and call \`authClient.signIn.*\` / \`authClient.signUp.*\`.
-
-This prevents session refresh behavior from starting just because a public page rendered.
-
-## Next.js proxy auth (web-landing)
-
-The Next.js proxy/middleware is used for **redirect decisions only**. It must not perform DB-backed session reads on every request.
-
-- Source: \`packages/apps/web-landing/src/proxy.ts\`
-- Approach: cookie-only checks via Better Auth cookies helpers:
-  - \`getSessionCookie(request)\`
-  - \`getCookieCache(request)\`
-
-These checks are intentionally optimistic and should only gate routing. Full authorization must still be enforced on server-side actions/routes and GraphQL resolvers.
-`
-}];
-a(t$17);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/schema/README.docblock.js
-const t$16 = [{
-	id: `docs.tech.schema.README`,
-	title: `Multi‑File Prisma Schema Conventions (per database)`,
-	summary: `We adopt Prisma multi‑file schema (GA ≥ v6.7) to organize each database’s models by domain and to import core LSSM module schemas locally.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/schema/README`,
-	tags: [
-		`tech`,
-		`schema`,
-		`README`
-	],
-	body: `# Multi‑File Prisma Schema Conventions (per database)
-
-We adopt Prisma multi‑file schema (GA ≥ v6.7) to organize each database’s models by domain and to import core LSSM module schemas locally.
-
-Canonical layout per DB:
-
-\`\`\`
-prisma/
-  schema/
-    main.prisma             # datasource + generators only
-    imported/
-      lssm_sigil/*.prisma   # imported models/enums only (no datasource/generator)
-      lssm_content/*.prisma # idem
-    <domain>/*.prisma       # vertical‑specific models split by bounded context
-\`\`\`
-
-Notes:
-
-- Imported files contain only \`model\` and \`enum\` blocks (strip \`datasource\`/\`generator\`).
-- Preserve \`@@schema("…")\` annotations to keep tables in their Postgres schemas; we now explicitly list schemas in \`main.prisma\` to avoid P1012: \`schemas = ["public","lssm_sigil","lssm_content","lssm_featureflags","lssm_ops","lssm_planning","lssm_quill","lssm_geoterro"]\`.
-- Use \`@lssm/app.cli-database\` CLI: \`database import|check|generate|migrate:*|seed\` to manage a single DB; \`@lssm/app.cli-databases\` orchestrates multiple DBs.
-
-## Typed merger config
-
-- Define imported module list once per DB with a typed config:
-
-\`\`\`ts
-// prisma-merger.config.ts
-import { defineMergedPrismaConfig } from '@lssm/app.cli-database';
-
-export default defineMergedPrismaConfig({
-  modules: [
-    '@lssm/app.cli-database-sigil',
-    '@lssm/app.cli-database-content',
-    // ...
-  ],
-});
-\`\`\`
-
-- Then run \`database import --target .\` (no need to pass \`--modules\`).
-
-## Prisma Config (prisma.config.ts)
-
-We use Prisma Config per official docs to point Prisma to the multi-file schema folder and migrations:
-
-\`\`\`ts
-// prisma.config.ts
-import path from 'node:path';
-import { defineConfig } from 'prisma/config';
-
-export default defineConfig({
-  schema: path.join('prisma', 'schema'),
-  migrations: { path: path.join('prisma', 'migrations') },
-});
-\`\`\`
-
-Reference: Prisma blog – Organize Your Prisma Schema into Multiple Files: https://www.prisma.io/blog/organize-your-prisma-schema-with-multi-file-support
-
----
-
-# LSSM Auth (Sigil) – Models & Integration
-
-This document tracks the identity models and integration points used by the LSSM Sigil module.
-
-## Models (Prisma \`lssm_sigil\`)
-
-- \`User\` – core identity with email, optional phone, role, passkeys, apiKeys
-- \`Session\` – session tokens and metadata; includes \`activeOrganizationId\`
-- \`Account\` – external providers (password, OAuth)
-- \`Organization\` – tenant boundary; includes \`type\` additional field
-- \`Member\`, \`Invitation\`, \`Team\`, \`TeamMember\` – org/teams
-- \`Role\`, \`Permission\`, \`PolicyBinding\` – RBAC
-- \`ApiKey\`, \`Passkey\` – programmable access and WebAuthn
-- \`SsoProvider\` – OIDC/SAML provider configuration (org- or user-scoped)
-- \`OAuthApplication\`, \`OAuthAccessToken\`, \`OAuthConsent\` – first/third-party OAuth
-
-These mirror STRIT additions so Better Auth advanced plugins (admin, organization, apiKey, passkey, genericOAuth) work uniformly across apps.
-
-## Better Auth (server)
-
-Enabled methods:
-
-- Email & password
-- Phone OTP (Telnyx)
-- Passkey (WebAuthn)
-- API keys
-- Organizations & Teams
-- Generic OAuth (FranceConnect+ via OIDC with JWE/JWS using JOSE)
-
-Server config lives at \`packages/lssm/modules/sigil/src/application/services/auth.ts\`.
-
-## Clients (Expo / React)
-
-Client config lives at \`packages/lssm/modules/sigil/src/presentation/providers/auth/expo.ts\` with plugins for admin, passkey, apiKey, organization, phone, genericOAuth.
-
-## Environment Variables
-
-Telnyx (phone OTP):
-
-- \`TELNYX_API_KEY\`
-- \`TELNYX_MESSAGING_PROFILE_ID\`
-- \`TELNYX_FROM_NUMBER\`
-
-FranceConnect+ (prefer LSSM*… but STRIT*… fallbacks are supported):
-
-- \`LSSM_FRANCECONNECTPLUS_DISCOVERY_URL\`
-- \`LSSM_FRANCECONNECTPLUS_CLIENT_ID\`
-- \`LSSM_FRANCECONNECTPLUS_CLIENT_SECRET\`
-- \`LSSM_FRANCECONNECTPLUS_ENC_PRIVATE_KEY_PEM\` (PKCS8; RSA-OAEP-256)
-
-Generic:
-
-- \`API_URL_IDENTITIES\` – base URL for Better Auth server
-- \`BETTER_AUTH_SECRET\` – server secret
-
-Keep this in sync with code changes to avoid drift.
-
-## HCircle domain splits and auth removal
-
-- Auth/identity models are not defined locally anymore. They come from \`@lssm/app.cli-database-sigil\` under the \`lssm_sigil\` schema.
-- \`packages/hcircle/libs/database-coliving/prisma/schema/domain/\` is split by domain; newsletter/waiting list lives in \`newsletter.prisma\` and uses \`@@map("waiting_list")\`.
-- To avoid collisions with module names, the local event models were renamed to \`SocialEvent\`, \`SocialEventAttendee\`, and \`SocialEventRecurrence\` with \`@@map\` pointing to existing table names.
-
----
-
-## Vertical profiles (current)
-
-### STRIT
-
-- prisma-merger modules:
-  - \`@lssm/app.cli-database-sigil\`, \`@lssm/app.cli-database-content\`, \`@lssm/app.cli-database-ops\`, \`@lssm/app.cli-database-planning\`, \`@lssm/app.cli-database-quill\`, \`@lssm/app.cli-database-geoterro\`
-- main.prisma schemas:
-  - \`schemas = ["public","lssm_sigil","lssm_content","lssm_ops","lssm_planning","lssm_quill","lssm_geoterro"]\`
-- domain splits (\`packages/strit/libs/database/prisma/schema/domain/\`):
-  - \`bookings.prisma\` (Booking, StritDocument + links to Content \`File\` and Sigil \`Organization\`)
-  - \`commerce.prisma\` (Wholesale models; \`sellerId\` linked to Sigil \`Organization\`)
-  - \`files.prisma\` (PublicFile, PublicFileAccessLog; \`ownerId\`→Organization, \`uploadedBy\`→User)
-  - \`geo.prisma\` (PublicCountry, PublicAddress, City; links to Spots/Series)
-  - \`spots.prisma\`, \`urbanism.prisma\`, \`analytics.prisma\`, \`onboarding.prisma\`, \`referrals.prisma\`, \`subscriptions.prisma\`, \`content.prisma\`
-- auth models are imported from Sigil (no local auth tables).
-- Back-relations for \`Organization\` (e.g., \`files\`, seller relations) are declared in the Sigil module to avoid scattering.
-
-### ARTISANOS
-
-- prisma-merger modules:
-  - \`@lssm/app.cli-database-sigil\`, \`@lssm/app.cli-database-content\`, \`@lssm/app.cli-database-featureflags\`, \`@lssm/app.cli-database-ops\`, \`@lssm/app.cli-database-planning\`, \`@lssm/app.cli-database-quill\`, \`@lssm/app.cli-database-geoterro\`
-- main.prisma schemas:
-  - \`schemas = ["public","lssm_sigil","lssm_content","lssm_featureflags","lssm_ops","lssm_planning","lssm_quill","lssm_geoterro"]\`
-- domain splits (\`packages/artisanos/libs/database-artisan/prisma/schema/domain/\`):
-  - \`sales.prisma\` (Client, Quote, QuoteTemplate, Invoice, FollowUps)
-  - \`subsidies.prisma\` (SubsidyProgram, AidApplication, SupportingDocument)
-  - \`projects.prisma\` (Project, ProjectPlanningSettings)
-  - \`crm.prisma\` (OrganizationProfessionalProfile, OrganizationCertification)
-  - \`professions.prisma\`, \`products.prisma\`, \`templates.prisma\`, \`analytics.prisma\`, \`onboarding.prisma\`, \`referrals.prisma\`, \`subscriptions.prisma\`, \`files.prisma\`
-- auth/organization/team models are provided by Sigil; local legacy copies were removed.
-- Where names collide with Content, local models are prefixed (e.g., \`PublicFile\`) and use \`@@map\` to keep existing table names where applicable.
-
-## Schema Dictionary: \`@lssm/lib.schema\`
-
-### Purpose
-
-Describe operation I/O once and generate:
-
-- zod (runtime validation)
-- GraphQL (Pothos types/refs)
-- JSON Schema (via \`zod-to-json-schema\` or native descriptors)
-
-### Primitives
-
-- **FieldType<T>**: describes a scalar or composite field and carries:
-  - \`zod\` schema for validation
-  - optional JSON Schema descriptor
-  - optional GraphQL scalar reference/name
-- **SchemaModel**: named object model composed of fields. Exposes helpers:
-  - \`getZod(): z.ZodObject<ZodShapeFromFields<Fields>> | z.ZodArray<z.ZodObject<...>>\`
-    - Preserves each field's schema, optionality, and array-ness
-    - Top-level lists are supported via \`config.isArray: true\`
-  - \`getJsonSchema(): JSONSchema7\` (export for docs, MCP, forms)
-  - \`getPothosInput()\` (GraphQL input object name)
-
-### Conventions
-
-- Name models with PascalCase; suffix with \`Input\`/\`Result\` when ambiguous.
-- Use explicit enums for multi-value constants; reuse the same enum across input/output.
-- Define domain enums via \`defineEnum('Name', [...])\` in the relevant domain package (e.g., \`packages/strit/libs/contracts-strit/src/enums/\`), not in \`ScalarTypeEnum\`.
-- Reference those enums in \`SchemaModel\` fields directly (they expose \`getZod\`, \`getPothos\`, \`getJsonSchema\`).
-
-#### Example (STRIT)
-
-\`\`\`ts
-// packages/strit/libs/contracts-strit/src/enums/recurrence.ts
-import { defineEnum } from '@lssm/lib.schema';
-export const SpotEnum = {
-  Weekday: () =>
-    defineEnum('Weekday', ['MO', 'TU', 'WE', 'TH', 'FR', 'SA', 'SU'] as const),
-  RecurrenceFrequency: () =>
-    defineEnum('RecurrenceFrequency', [
-      'DAILY',
-      'WEEKLY',
-      'MONTHLY',
-      'YEARLY',
-    ] as const),
-} as const;
-\`\`\`
-
-\`\`\`ts
-// usage in contracts
-frequency: { type: SpotEnum.RecurrenceFrequency(), isOptional: false },
-byWeekday: { type: SpotEnum.Weekday(), isOptional: true, isArray: true },
-\`\`\`
-
-- Use \`Date\` type for temporal values and ensure ISO strings in JSON transports where needed.
-
-### Mapping rules (summary)
-
-- Strings → GraphQL \`String\`
-- Numbers → \`Int\` if safe 32-bit integer else \`Float\`
-- Booleans → \`Boolean\`
-- Dates → custom \`Date\` scalar
-- Arrays<T> → list of mapped T (set \`isArray: true\` on the field)
-- Top-level arrays → set \`isArray: true\` on the model config
-- Objects → input/output object types with stable field order
-- Unions → supported for output; input unions map to JSON (structural input is not supported by GraphQL)
-
-### JSON Schema export
-
-Prefer \`getZod()\` + \`zod-to-json-schema\` for consistency. For advanced cases, provide a custom \`getJsonSchema()\` on the model.
-
-### Example
-
-\`\`\`ts
-import { ScalarTypeEnum, SchemaModel } from '@lssm/lib.schema';
-
-// Nested model
-const Weekday = new SchemaModel({
-  name: 'Weekday',
-  fields: {
-    value: { type: ScalarTypeEnum.String_unsecure(), isOptional: false },
-  },
-});
-
-// Parent model with array field and nested object
-const Rule = new SchemaModel({
-  name: 'Rule',
-  fields: {
-    timezone: { type: ScalarTypeEnum.TimeZone(), isOptional: false },
-    byWeekday: { type: Weekday, isOptional: true, isArray: true },
-  },
-});
-
-const CreateThingInput = new SchemaModel({
-  name: 'CreateThingInput',
-  fields: {
-    name: { type: ScalarTypeEnum.NonEmptyString(), isOptional: false },
-    rule: { type: Rule, isOptional: false },
-  },
-});
-
-// zod
-const z = CreateThingInput.getZod();
-\`\`\`
-`
-}];
-a(t$16);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/templates/runtime.docblock.js
-const t$15 = [{
-	id: `docs.tech.templates.runtime`,
-	title: `ContractSpec Template Runtime (Phase 9)`,
-	summary: `Phase 9 introduces a full local-first runtime for templates so anyone can preview apps directly in the browser without provisioning any infrastructure.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/templates/runtime`,
-	tags: [
-		`tech`,
-		`templates`,
-		`runtime`
-	],
-	body: "## ContractSpec Template Runtime (Phase 9)\n\nPhase 9 introduces a full local-first runtime for templates so anyone can preview apps directly in the browser without provisioning any infrastructure.\n\n### Building Blocks\n\n- **Local database** – `@lssm/lib.runtime-local` wraps `sql.js` (SQLite WASM) and `IndexedDB` so we can seed demo data, run migrations, and persist state between sessions. Tests point the runtime to `node_modules/sql.js/dist` so CI doesn’t need a browser.\n- **Local GraphQL** – `LocalGraphQLClient` wires Apollo Client + SchemaLink to resolvers for tasks, messaging, and i18n recipes. All `/templates`, `/studio`, and `/sandbox` previews use those resolvers so we never call remote APIs during demos.\n- **Template registry + installer** – `.../templates/registry.ts` stores the catalog (todos, messaging, recipes). `TemplateInstaller` can seed the runtime (`install`) or export a base64 snapshot via the new `saveTemplateToStudio` mutation.\n- **TemplateShell** – Shared UI wrapper that creates a `TemplateRuntimeProvider`, shows `LocalDataIndicator`, and (optionally) surfaces the new `SaveToStudioButton`.\n\n### Runtime Flows\n\n1. `/templates` now opens a modal that renders `TemplateShell` for each template. Users can explore without leaving the marketing site.\n2. `/studio` switches to a tabbed mini-app (Projects, Canvas, Specs, Deploy) to showcase Studio surfaces with mock data. Visitors see a **preview** shell, while authenticated users (Better Auth via Sigil) unlock full persistence, versioning, and deployment controls.\n3. `/sandbox` lets visitors pick a template and mode (Playground, Spec Editor, Visual Builder). The console at the bottom streams runtime events for transparency.\n\n### GraphQL Mutations\n\n- `saveTemplateToStudio(input: SaveTemplateInput!): SaveTemplateResult!` writes a placeholder project + spec so that templates installed from the sandbox appear in Studio. The mutation is intentionally simple right now: it records which template was imported, stores metadata, and returns `{ projectId, status: 'QUEUED' }` for the UI.\n- `saveCanvasDraft(input: SaveCanvasDraftInput!): CanvasVersion!` snapshots the current Visual Builder nodes to a draft version tied to a canvas overlay. Inputs include `canvasId`, arbitrary `nodes` JSON, and an optional `label`. The resolver enforces org/org access before calling `CanvasVersionManager`.\n- `deployCanvasVersion(input: DeployCanvasVersionInput!): CanvasVersion!` promotes a previously saved draft (`versionId`) to the deployed state. The returned object includes `status`, `nodes`, `createdAt`, and `createdBy` for UI timelines.\n- `undoCanvasVersion(input: UndoCanvasInput!): CanvasVersion` rewinds the visual builder to the prior snapshot (returns `null` when history is empty) so Studio’s toolbar can surface “Undo” without shelling out to local storage.\n\n### Studio GraphQL endpoint\n\n- The landing app exposes the Studio schema at `/api/studio/graphql` via Yoga so React Query hooks (`useStudioProjects`, `useCreateStudioProject`, `useDeployStudioProject`, etc.) can talk to the bundle without spinning up a separate server.\n\n### Spec Editor typing\n\n- Studio’s spec editor now preloads Monaco with ambient declarations for `@lssm/lib.contracts` and `zod`, so snippets receive autocomplete and inline errors even before the spec ships to the backend. The helper lives in `presentation/components/studio/organisms/monaco-spec-types.ts` and registers the extra libs once per browser session via `monaco.languages.typescript.typescriptDefaults.addExtraLib`.\n- Compiler options are aligned with our frontend toolchain (ES2020 + React JSX) which means drafts written in the editor behave like the compiled artifacts that flow through Studio pipelines.\n\n### Spec templates\n\n- Selecting a spec type now injects a ready-to-edit scaffold (capability, workflow, policy, dataview, component) so authors start from a canonical layout instead of a blank file. Templates live alongside `SpecEditor.tsx`, and we only overwrite the content when the previous value is empty or when the author explicitly switches types via the dropdown.\n\n### Spec preview\n\n- The validation side panel now embeds a `SpecPreview` widget that shows validation errors alongside transport artifacts (GraphQL schema, REST endpoints, component summaries) once a preview run completes. Tabs let authors toggle between “Validation” and “Artifacts,” mirroring the UX described in the Studio plan.\n\n### Testing\n\n- `src/templates/__tests__/runtime.test.ts` covers todos CRUD, messaging delivery, and recipe locale switching through the local GraphQL API.\n- Studio infrastructure tests live in `src/__tests__/e2e/project-lifecycle.test.ts` and continue to exercise project creation + deploy flows.\n\n### Next Steps\n\nFuture templates can register their React components via `registerTemplateComponents(templateId, components)` so TemplateShell can render them automatically. When new templates are added, remember to:\n\n1. Update the registry entry (schema + tags).\n2. Register components inside `presentation/components/templates`.\n3. Document the template under `docs/templates/`.\n\n\n\n\n\n"
-}];
-a(t$15);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/workflows/overview.docblock.js
-const t$14 = [{
-	id: `docs.tech.workflows.overview`,
-	title: `WorkflowSpec Overview`,
-	summary: "WorkflowSpec provides a declarative, versioned format for long-running flows that mix automation and human review. Specs stay inside `@lssm/lib.contracts` (`src/workflow/spec.ts`) so the same definition powers runtime execution, documentation, and future generation.",
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/workflows/overview`,
-	tags: [
-		`tech`,
-		`workflows`,
-		`overview`
-	],
-	body: "# WorkflowSpec Overview\n\n## Purpose\n\nWorkflowSpec provides a declarative, versioned format for long-running flows that mix automation and human review. Specs stay inside `@lssm/lib.contracts` (`src/workflow/spec.ts`) so the same definition powers runtime execution, documentation, and future generation.\n\n## Core Types\n\n- `WorkflowMeta`: ownership metadata (`title`, `domain`, `owners`, `tags`, `stability`) plus `name` and `version`.\n- `WorkflowDefinition`:\n  - `entryStepId?`: optional explicit entry point (defaults to first step).\n  - `steps[]`: ordered list of `Step` descriptors.\n  - `transitions[]`: directed edges between steps with optional expressions.\n  - `sla?`: aggregated timing hints for the overall flow or per-step budgets.\n  - `compensation?`: fallback operations executed when a workflow is rolled back or fails.\n- `Step`:\n  - `type`: `human`, `automation`, or `decision`.\n  - `action`: references either a `ContractSpec` (`operation`) or `FormSpec` (`form`).\n  - Optional `guard`, `timeoutMs`, and retry policy (`maxAttempts`, `backoff`, `delayMs`, `maxDelayMs?`).\n  - `requiredIntegrations?`: integration slot ids that must be bound before the step may execute.\n  - `requiredCapabilities?`: `CapabilityRef[]` that must be enabled in the resolved app config.\n- `Transition`: `from` → `to` with optional `condition` string (simple data expressions).\n\n## Registry & Validation\n\n- `WorkflowRegistry` (`src/workflow/spec.ts`) stores specs by key `<name>.v<version>` and exposes `register`, `list`, and `get`.\n- `validateWorkflowSpec()` (`src/workflow/validation.ts`) checks:\n  - Duplicate step IDs.\n  - Unknown `from`/`to` transitions.\n  - Empty guards/conditions.\n  - Reachability from the entry step.\n  - Cycles in the graph.\n  - Operation/Form references against provided registries.\n- `assertWorkflowSpecValid()` wraps validation and throws `WorkflowValidationError` when errors remain.\n\n## Runtime\n\n- `WorkflowRunner` (`src/workflow/runner.ts`) executes workflows and coordinates steps.\n  - `start(name, version?, initialData?)` returns a `workflowId`.\n  - `executeStep(workflowId, input?)` runs the current step (automation or human).\n  - `getState(workflowId)` retrieves the latest state snapshot.\n  - `cancel(workflowId)` marks the workflow as cancelled.\n  - `preFlightCheck(name, version?, resolvedConfig?)` evaluates integration/capability requirements before the workflow starts.\n  - Throws `WorkflowPreFlightError` if required integration slots are unbound or required capabilities are disabled.\n- `StateStore` (`src/workflow/state.ts`) abstracts persistence. V1 ships with:\n  - `InMemoryStateStore` (`src/workflow/adapters/memory-store.ts`) for tests/dev.\n  - Placeholder factories for file/database adapters (`adapters/file-adapter.ts`, `adapters/db-adapter.ts`).\n- Guard evaluation: expression guards run through `evaluateExpression()` (`src/workflow/expression.ts`); custom policy guards can be provided via `guardEvaluator`.\n- Events: the runner emits `workflow.started`, `workflow.step_completed`, `workflow.step_failed`, and `workflow.cancelled` through the optional `eventEmitter`.\n- React bindings (`@lssm/lib.presentation-runtime-react`):\n  - `useWorkflow` hook (polls state, exposes `executeStep`, `cancel`, `refresh`).\n  - `WorkflowStepper` progress indicator using design-system Stepper.\n  - `WorkflowStepRenderer` helper to render human/automation/decision steps with sensible fallbacks.\n\n## Authoring Checklist\n\n1. Reuse existing operations/forms; create new specs when missing.\n2. Prefer explicit `entryStepId` for clarity (especially with decision branches).\n3. Give automation steps an `operation` and human steps a `form` (warnings surface otherwise).\n4. Use short, meaningful step IDs (`submit`, `review`, `finalize`) to simplify analytics.\n5. Keep guard expressions deterministic; complex policy logic should move to PolicySpec (Phase 2).\n\n## Testing\n\n- Add unit tests for new workflows via `assertWorkflowSpecValid`.\n- Use the new Vitest suites (`validation.test.ts`, `expression.test.ts`, `runner.test.ts`) as examples.\n- CLI support will arrive in Phase 1 PR 3 (`contractspec create --type workflow`).\n\n## Tooling\n\n- `contractspec create --type workflow` scaffolds a WorkflowSpec with interactive prompts.\n- `contractspec build <spec.workflow.ts>` generates a runner scaffold (`.runner.ts`) wired to `WorkflowRunner` and the in-memory store.\n- `contractspec validate` understands `.workflow.ts` files and checks core structure (meta, steps, transitions).\n\n## Next Steps (Non-MVP)\n\n- Persistence adapters (database/file) for workflow state (Phase 2).\n- React bindings (`useWorkflow`, `WorkflowStepper`) and presentation-runtime integration (PR 3).\n- Policy engine integration (`guard.type === 'policy'` validated against PolicySpec).\n- Telemetry hooks for step execution metrics.\n\n"
-}];
-a(t$14);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/mcp-endpoints.docblock.js
-const t$13 = [{
-	id: `docs.tech.mcp.endpoints`,
-	title: `ContractSpec MCP endpoints`,
-	summary: `Dedicated MCP servers for docs, CLI usage, and internal development.`,
-	kind: `reference`,
-	visibility: `mixed`,
-	route: `/docs/tech/mcp/endpoints`,
-	tags: [
-		`mcp`,
-		`docs`,
-		`cli`,
-		`internal`
-	],
-	body: "# ContractSpec MCP endpoints\n\nThree dedicated MCP servers keep AI agents efficient and scoped:\n\n- **Docs MCP**: `/api/mcp/docs` — exposes DocBlocks as resources + presentations. Tool: `docs.search`.\n- **CLI MCP**: `/api/mcp/cli` — surfaces CLI quickstart/reference/README and suggests commands. Tool: `cli.suggestCommand`.\n- **Internal MCP**: `/api/mcp/internal` — internal routing hints, playbook, and example registry access. Tool: `internal.describe`.\n\n### Usage notes\n- Transports are HTTP POST (streamable HTTP); SSE is disabled.\n- Resources are namespaced (`docs://*`, `cli://*`, `internal://*`) and are read-only.\n- Internal MCP also exposes the examples registry via `examples://*` resources:\n  - `examples://list?q=<query>`\n  - `examples://example/<id>`\n- Prompts mirror each surface (navigator, usage, bootstrap) for quick agent onboarding.\n- GraphQL remains at `/graphql`; health at `/health`.\n"
-}];
-a(t$13);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/vscode-extension.docblock.js
-const t$12 = [{
-	id: `docs.tech.vscode.extension`,
-	title: `ContractSpec VS Code Extension`,
-	summary: `VS Code extension for spec-first development with validation, scaffolding, and MCP integration.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/vscode/extension`,
-	tags: [
-		`vscode`,
-		`extension`,
-		`tooling`,
-		`dx`
-	],
-	body: `# ContractSpec VS Code Extension
-
-The ContractSpec VS Code extension provides spec-first development tooling directly in your editor.
-
-## Features
-
-- **Real-time Validation**: Get instant feedback on spec errors and warnings as you save files
-- **Build/Scaffold**: Generate handler and component skeletons from specs (no AI required)
-- **Spec Explorer**: List and navigate all specs in your workspace
-- **Dependency Analysis**: Visualize spec dependencies and detect cycles
-- **MCP Integration**: Search ContractSpec documentation via Model Context Protocol
-- **Snippets**: Code snippets for common ContractSpec patterns
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| \`ContractSpec: Validate Current Spec\` | Validate the currently open spec file |
-| \`ContractSpec: Validate All Specs\` | Validate all spec files in the workspace |
-| \`ContractSpec: Build/Scaffold\` | Generate handler/component from the current spec |
-| \`ContractSpec: List All Specs\` | Show all specs in the workspace |
-| \`ContractSpec: Analyze Dependencies\` | Analyze and visualize spec dependencies |
-| \`ContractSpec: Search Docs (MCP)\` | Search documentation via MCP |
-
-## Configuration
-
-| Setting | Description | Default |
-|---------|-------------|---------|
-| \`contractspec.api.baseUrl\` | Base URL for ContractSpec API (enables MCP + remote telemetry) | \`""\` |
-| \`contractspec.telemetry.posthogHost\` | PostHog host URL for direct telemetry | \`"https://eu.posthog.com"\` |
-| \`contractspec.telemetry.posthogProjectKey\` | PostHog project key for direct telemetry | \`""\` |
-| \`contractspec.validation.onSave\` | Run validation on save | \`true\` |
-| \`contractspec.validation.onOpen\` | Run validation on open | \`true\` |
-
-## Architecture
-
-The extension uses:
-- \`@lssm/module.contractspec-workspace\` for pure analysis + templates
-- \`@lssm/bundle.contractspec-workspace\` for workspace services + adapters
-
-This allows the extension to work without requiring the CLI to be installed.
-
-## Telemetry
-
-The extension uses a hybrid telemetry approach:
-1. If \`contractspec.api.baseUrl\` is configured → send to API \`/api/telemetry/ingest\`
-2. Otherwise → send directly to PostHog (if project key configured)
-
-Telemetry respects VS Code's telemetry settings. No file paths, source code, or PII is collected.
-`
-}, {
-	id: `docs.tech.vscode.snippets`,
-	title: `ContractSpec Snippets`,
-	summary: `Code snippets for common ContractSpec patterns in VS Code.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/vscode/snippets`,
-	tags: [
-		`vscode`,
-		`snippets`,
-		`dx`
-	],
-	body: `# ContractSpec Snippets
-
-The VS Code extension includes snippets for common ContractSpec patterns.
-
-## Available Snippets
-
-| Prefix | Description |
-|--------|-------------|
-| \`contractspec-command\` | Create a new command (write operation) |
-| \`contractspec-query\` | Create a new query (read-only operation) |
-| \`contractspec-event\` | Create a new event |
-| \`contractspec-docblock\` | Create a new DocBlock |
-| \`contractspec-telemetry\` | Create a new TelemetrySpec |
-| \`contractspec-presentation\` | Create a new Presentation |
-
-## Usage
-
-Type the prefix in a TypeScript file and press Tab to expand the snippet. Tab through the placeholders to fill in your values.
-`
-}];
-a(t$12);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/telemetry-ingest.docblock.js
-const t$11 = [{
-	id: `docs.tech.telemetry.ingest`,
-	title: `Telemetry Ingest Endpoint`,
-	summary: `Server-side telemetry ingestion for ContractSpec clients (VS Code extension, CLI, etc.).`,
-	kind: `reference`,
-	visibility: `internal`,
-	route: `/docs/tech/telemetry/ingest`,
-	tags: [
-		`telemetry`,
-		`api`,
-		`posthog`,
-		`analytics`
-	],
-	body: `# Telemetry Ingest Endpoint
-
-The ContractSpec API provides a telemetry ingest endpoint for clients to send product analytics events.
-
-## Endpoint
-
-\`\`\`
-POST /api/telemetry/ingest
-\`\`\`
-
-## Request
-
-\`\`\`json
-{
-  "event": "contractspec.vscode.command_run",
-  "distinct_id": "client-uuid",
-  "properties": {
-    "command": "validate"
-  },
-  "timestamp": "2024-01-15T10:30:00.000Z"
-}
-\`\`\`
-
-### Headers
-
-| Header | Description |
-|--------|-------------|
-| \`x-contractspec-client-id\` | Optional client identifier (used as fallback for distinct_id) |
-| \`Content-Type\` | Must be \`application/json\` |
-
-### Body
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| \`event\` | string | Yes | Event name (e.g., \`contractspec.vscode.activated\`) |
-| \`distinct_id\` | string | Yes | Anonymous client identifier |
-| \`properties\` | object | No | Event properties |
-| \`timestamp\` | string | No | ISO 8601 timestamp |
-
-## Response
-
-\`\`\`json
-{
-  "success": true
-}
-\`\`\`
-
-## Configuration
-
-The endpoint requires \`POSTHOG_PROJECT_KEY\` environment variable to be set. If not configured, events are accepted but not forwarded.
-
-| Environment Variable | Description | Default |
-|---------------------|-------------|---------|
-| \`POSTHOG_HOST\` | PostHog host URL | \`https://eu.posthog.com\` |
-| \`POSTHOG_PROJECT_KEY\` | PostHog project API key | (required) |
-
-## Privacy
-
-- No PII is collected or stored
-- \`distinct_id\` is an anonymous client-generated UUID
-- File paths and source code are never included in events
-- Respects VS Code telemetry settings on the client side
-
-## Events
-
-### Extension Events
-
-| Event | Description | Properties |
-|-------|-------------|------------|
-| \`contractspec.vscode.activated\` | Extension activated | \`version\` |
-| \`contractspec.vscode.command_run\` | Command executed | \`command\` |
-| \`contractspec.vscode.mcp_call\` | MCP call made | \`endpoint\`, \`tool\` |
-
-### API Events
-
-| Event | Description | Properties |
-|-------|-------------|------------|
-| \`contractspec.api.mcp_request\` | MCP request processed | \`endpoint\`, \`method\`, \`success\`, \`duration_ms\` |
-`
-}, {
-	id: `docs.tech.telemetry.hybrid`,
-	title: `Hybrid Telemetry Model`,
-	summary: `How ContractSpec clients choose between direct PostHog and API-routed telemetry.`,
-	kind: `usage`,
-	visibility: `internal`,
-	route: `/docs/tech/telemetry/hybrid`,
-	tags: [
-		`telemetry`,
-		`architecture`,
-		`posthog`
-	],
-	body: `# Hybrid Telemetry Model
-
-ContractSpec uses a hybrid telemetry model where clients can send events either directly to PostHog or via the API server.
-
-## Decision Flow
-
-\`\`\`
-Is contractspec.api.baseUrl configured?
-├── Yes → Send via /api/telemetry/ingest
-└── No → Is posthogProjectKey configured?
-    ├── Yes → Send directly to PostHog
-    └── No → Telemetry disabled
-\`\`\`
-
-## Benefits
-
-### Direct PostHog
-- No server dependency
-- Works offline (with batching)
-- Lower latency
-
-### Via API
-- Centralized key management (no client-side keys)
-- Server-side enrichment and validation
-- Rate limiting and abuse prevention
-- Easier migration to other providers
-
-## Recommendation
-
-- **Development**: Use direct PostHog with a dev project key
-- **Production**: Route via API for better governance
-
-## Future: OpenTelemetry
-
-The current PostHog implementation is behind a simple interface that can be swapped for OpenTelemetry:
-
-\`\`\`typescript
-interface TelemetryClient {
-  send(event: TelemetryEvent): Promise<void>;
-}
-\`\`\`
-
-This allows future migration without changing client code.
-`
-}];
-a(t$11);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/contracts/openapi-export.docblock.js
-const t$10 = [{
-	id: `docs.tech.contracts.openapi-export`,
-	title: `OpenAPI export (OpenAPI 3.1) from SpecRegistry`,
-	summary: `Generate a deterministic OpenAPI document from a SpecRegistry using jsonSchemaForSpec + REST transport metadata.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/contracts/openapi-export`,
-	tags: [
-		`contracts`,
-		`openapi`,
-		`rest`
-	],
-	body: `## OpenAPI export (OpenAPI 3.1) from SpecRegistry
-
-### Purpose
-
-ContractSpec specs can be exported into an **OpenAPI 3.1** document for tooling (SDK generation, docs, gateways).
-
-The export is **spec-first**:
-
-- Uses \`jsonSchemaForSpec(spec)\` for input/output JSON Schema (from SchemaModel → zod → JSON Schema)
-- Uses \`spec.transport.rest.method/path\` when present
-- Falls back to deterministic defaults:
-  - Method: \`POST\` for commands, \`GET\` for queries
-  - Path: \`defaultRestPath(name, version)\` → \`/<dot/name>/v<version>\`
-
-### Library API
-
-- Function: \`openApiForRegistry(registry, options?)\`
-- Location: \`@lssm/lib.contracts/openapi\`
-
-### CLI
-
-Export OpenAPI from a registry module:
-
-\`\`\`bash
-contractspec openapi --registry ./src/registry.ts --out ./openapi.json
-\`\`\`
-
-The registry module must export one of:
-
-- \`registry: SpecRegistry\`
-- \`default(): SpecRegistry | Promise<SpecRegistry>\`
-- \`createRegistry(): SpecRegistry | Promise<SpecRegistry>\`
-
-### Notes / limitations (current)
-
-- Responses are generated as a basic \`200\` response (plus schemas when available).
-- Query (GET) inputs are currently represented as a JSON request body when an input schema exists.
-- Errors are not yet expanded into OpenAPI responses; that will be added when we standardize error envelopes.`
-}];
-a(t$10);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/workspaces.docblock.js
-const t$9 = [{
-	id: `docs.tech.studio.workspaces`,
-	title: `Studio projects, teams, environments`,
-	summary: `Organization-first Studio: projects live under an organization; teams refine access; projects deploy to multiple environments.`,
-	kind: `reference`,
-	visibility: `mixed`,
-	route: `/docs/tech/studio/workspaces`,
-	tags: [
-		`studio`,
-		`projects`,
-		`teams`,
-		`rbac`,
-		`environments`
-	],
-	body: `## Concepts
-
-- **Organization**: the primary grouping boundary for Studio projects.
-- **Project**: one application (specs, overlays, deployments, integrations, evolution, learning).
-- **Team**: refines who can see/edit a project within an organization.
-- **Environment**: deployment target (Development / Staging / Production).
-
-## Project access (teams + admin override)
-
-Studio uses multi-team sharing to refine access:
-
-- **Admins/owners** can access all projects.
-- If a project is shared with **no teams**, it is **org-wide** (all org members).
-- If a project is shared with **one or more teams**, it is visible to:
-  - admins/owners, and
-  - members of any linked team.
-
-## Current persistence (DB + GraphQL)
-
-- DB (Prisma): \`StudioProject\`, \`Team\`, \`TeamMember\`, \`StudioProjectTeam\`
-- GraphQL:
-  - \`myStudioProjects\`
-  - \`createStudioProject(input.teamIds?)\`
-  - \`myTeams\`
-  - \`projectTeams(projectId)\`
-  - \`setProjectTeams(projectId, teamIds)\`
-
-## UI shell behavior
-
-Studio and Sandbox both use a shared shell:
-
-- Project selector → Module navigation → Environment selector
-- Always-on Assistant button (floating)
-- Learning journey progress (Studio persists learning events; Sandbox stays local-only)
-
-## Routing
-
-- \`/studio/projects\`: create/select/delete projects (organization-first).
-- \`/studio/{projectSlug}/*\`: project modules (canvas/specs/deploy/integrations/evolution/learning).
-- \`/studio/learning\`: learning hub without selecting a project.
-`
-}];
-a(t$9);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/sandbox-unlogged.docblock.js
-const t$8 = [{
-	id: `docs.tech.studio.sandbox.unlogged`,
-	title: `Sandbox (unlogged) vs Studio (authenticated)`,
-	summary: `The sandbox is a lightweight, unlogged surface that mirrors Studio navigation without auth or analytics.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/sandbox-unlogged`,
-	tags: [
-		`studio`,
-		`sandbox`,
-		`privacy`,
-		`analytics`
-	],
-	body: `## Sandbox guarantees
-
-- Route: \`/sandbox\`
-- **No auth requirement**
-- **No PostHog init**
-- **No Vercel Analytics**
-- Local-only state (in-browser runtime + localStorage where needed)
-
-## What Sandbox is for
-
-- Try templates and feature modules safely
-- Preview specs/builder/evolution/learning
-- Produce copyable CLI commands (no side effects)
-
-## What Sandbox is *not* for
-
-- Persisted projects/workspaces
-- Real deployments
-- Organization-scoped integrations (unless explicitly enabled later)
-`
-}];
-a(t$8);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/workspace-ops.docblock.js
-const t$7 = [{
-	id: `docs.tech.studio.workspace_ops`,
-	title: `Workspace ops (repo-linked): list / validate / deps / diff`,
-	summary: `Read-only repo operations used by Studio to inspect and validate a linked ContractSpec workspace.`,
-	kind: `reference`,
-	visibility: `mixed`,
-	route: `/docs/tech/studio/workspace-ops`,
-	tags: [
-		`studio`,
-		`repo`,
-		`workspace`,
-		`validate`,
-		`diff`
-	],
-	body: "## API surface (api-contractspec)\n\nBase: `/api/workspace-ops`\n\nThese endpoints are **read-only** in v1 and never push to git:\n\n- `GET /api/workspace-ops/:integrationId/config?organizationId=`\n- `GET /api/workspace-ops/:integrationId/specs?organizationId=`\n- `POST /api/workspace-ops/:integrationId/validate` (body: organizationId, files?, pattern?)\n- `POST /api/workspace-ops/:integrationId/deps` (body: organizationId, pattern?)\n- `POST /api/workspace-ops/:integrationId/diff` (body: organizationId, specPath, baseline?, breakingOnly?)\n\n## Repo resolution\n\n- The repo root is resolved from the Studio Integration (`IntegrationProvider.GITHUB`) config:\n  - `config.repoCachePath` (preferred) or `config.localPath`\n- Resolution is constrained to `CONTRACTSPEC_REPO_CACHE_DIR` (default: `/tmp/contractspec-repos`)\n\n## Intended UX\n\n- Studio Assistant can run these checks and present results as suggestions.\n- Users can copy equivalent CLI commands for local runs:\n  - `contractspec validate`\n  - `contractspec deps`\n  - `contractspec diff --baseline <ref>`\n"
-}];
-a(t$7);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/project-routing.docblock.js
-const t$6 = [{
-	id: `docs.tech.studio.project-routing`,
-	title: `Studio Project Routing`,
-	summary: `Studio uses slugged, project-first routes: /studio/{projectSlug}/* with canonical slug redirects and soft-deleted projects hidden.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/project-routing`,
-	tags: [
-		`studio`,
-		`routing`,
-		`projects`,
-		`slug`,
-		`redirects`
-	],
-	body: "# Studio Project Routing\n\nContractSpec Studio uses a **project-first URL scheme**:\n\n- `/studio/projects` — create, select, and delete projects.\n- `/studio/{projectSlug}/*` — project modules (canvas/specs/deploy/integrations/evolution/learning).\n- `/studio/learning` — learning hub that does not require selecting a project.\n\n## Studio layout shell\n\nStudio routes are wrapped in a dedicated **Studio app shell** (header + footer) that provides in-app navigation (Projects/Learning/Teams), organization switching, and account actions.\n\nProject module routes (`/studio/{projectSlug}/*`) render their own module shell (`WorkspaceProjectShellLayout`). When combined with the global Studio header, the project shell uses a **sticky header offset** to avoid overlapping sticky headers.\n\n## Slug behavior (rename-safe)\n\n- Each project has a `slug` stored in the database (`StudioProject.slug`).\n- When a project name changes, Studio **updates the slug** and stores the previous slug as an alias (`StudioProjectSlugAlias`).\n- Requests to an alias slug are **redirected to the canonical slug**.\n\nGraphQL entrypoint:\n\n- `studioProjectBySlug(slug: String!)` returns:\n  - `project`\n  - `canonicalSlug`\n  - `wasRedirect`\n\n## Deletion behavior (soft delete)\n\nProjects are **soft-deleted**:\n\n- `deleteStudioProject(id: String!)` sets `StudioProject.deletedAt`.\n- All listings and access checks filter `deletedAt = null`.\n- Soft-deleted projects are treated as “not found” in Studio routes and GraphQL access checks.\n\n## Available modules for a selected project\n\nThe following project modules are expected under `/studio/{projectSlug}`:\n\n- `/canvas` — Visual builder canvas (stored via overlays and canvas versions).\n- `/specs` — Spec editor (stored as `StudioSpec`).\n- `/deploy` — Deployments history + triggers (stored as `StudioDeployment`).\n- `/integrations` — Integrations scoped to project (stored as `StudioIntegration`).\n- `/evolution` — Evolution sessions (stored as `EvolutionSession`).\n- `/learning` — Project learning activity.\n"
-}];
-a(t$6);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/platform-admin-panel.docblock.js
-const t$5 = [{
-	id: `docs.tech.studio.platform-admin-panel`,
-	title: `Studio Platform Admin Panel`,
-	summary: `How PLATFORM_ADMIN organizations manage tenant orgs and integration connections without session switching.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/platform-admin-panel`,
-	tags: [
-		`studio`,
-		`admin`,
-		`multi-tenancy`,
-		`integrations`,
-		`better-auth`
-	],
-	body: `# Studio Platform Admin Panel
-
-ContractSpec Studio exposes a dedicated **Platform Admin Panel** for users whose **active organization** has:
-
-- \`Organization.type = PLATFORM_ADMIN\`
-
-The UI route is:
-
-- \`/studio/admin\`
-
-## Authorization model (no org switching)
-
-Platform admins **remain in their own organization**. Cross-tenant actions are always explicit and scoped:
-
-- Admin operations require an explicit \`targetOrganizationId\`.
-- No session / activeOrganizationId switching is performed as part of admin operations.
-
-## Integrations management
-
-The admin panel manages the full ContractSpec Integrations system:
-
-- Lists all shipped \`IntegrationSpec\` entries (registry built via \`createDefaultIntegrationSpecRegistry()\`).
-- CRUD \`IntegrationConnection\` records for a selected tenant org.
-
-### Secrets (reference-only + write-only)
-
-The admin UI supports two modes:
-
-- **Reference-only (BYOK)**: store only \`secretProvider\` + \`secretRef\`.
-- **Write-only provisioning/rotation**: paste a raw secret payload; server writes to the selected backend and stores the resulting reference. The secret value is **never returned or displayed**.
-
-Supported backends:
-
-- Env overrides (\`env://...\`)
-- Google Cloud Secret Manager (\`gcp://...\`)
-- AWS Secrets Manager (\`aws://secretsmanager/...\`)
-- Scaleway Secret Manager (\`scw://secret-manager/...\`)
-
-## Better Auth Admin plugin
-
-The panel uses the Better Auth **Admin plugin** for user operations (list users, impersonation):
-
-- Client calls use \`authClient.admin.*\`.
-- Server-side, ContractSpec enforces that users in a PLATFORM_ADMIN active org have \`User.role\` containing \`admin\` so Better Auth Admin endpoints authorize.
-
-## GraphQL surface
-
-The platform-admin GraphQL operations are guarded by the active org type and include:
-
-- \`platformAdminOrganizations(search, limit, offset)\`
-- \`platformAdminIntegrationSpecs\`
-- \`platformAdminIntegrationConnections(input: { targetOrganizationId, category?, status? })\`
-- \`platformAdminIntegrationConnectionCreate(input)\`
-- \`platformAdminIntegrationConnectionUpdate(input)\`
-- \`platformAdminIntegrationConnectionDelete(targetOrganizationId, connectionId)\`
-
-## Key implementation files
-
-- Auth + role enforcement: \`packages/bundles/contractspec-studio/src/application/services/auth.ts\`
-- Admin GraphQL module: \`packages/bundles/contractspec-studio/src/infrastructure/graphql/modules/platform-admin.ts\`
-- Integrations admin service: \`packages/bundles/contractspec-studio/src/modules/platform-integrations/index.ts\`
-- Web route: \`packages/apps/web-landing/src/app/(app-customer)/studio/admin/*\`
-`
-}];
-a(t$5);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/learning-events.docblock.js
-const t$4 = [{
-	id: `docs.tech.studio.learning-events`,
-	title: `Studio Learning Events`,
-	summary: `Studio persists learning/activity events to the database; Sandbox keeps learning local-first and unlogged.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/learning-events`,
-	tags: [
-		`studio`,
-		`learning`,
-		`events`,
-		`analytics`,
-		`sandbox`
-	],
-	body: "# Studio Learning Events\n\nStudio emits lightweight **learning/activity events** to support onboarding, ambient coaching, and learning journeys.\n\n## Persistence model\n\n- **Studio**: events are persisted to the database in `StudioLearningEvent` and are organization-scoped (optionally project-scoped).\n- **Sandbox**: events remain **local-only** (unlogged); they must never be sent to backend services.\n\n## GraphQL API\n\n- `recordLearningEvent(input: { name, projectId?, payload? })`\n- `myLearningEvents(projectId?, limit?)`\n- `myOnboardingTracks(productId?, includeProgress?)`\n- `myOnboardingProgress(trackKey)`\n- `dismissOnboardingTrack(trackKey)`\n\n## Common event names (convention)\n\n- `module.navigated` — user navigated to a Studio module (payload at minimum: `{ moduleId }`).\n- `studio.template.instantiated` — created a new Studio project (starter template). Payload commonly includes `{ templateId, projectSlug }`.\n- `spec.changed` — created or updated a Studio spec. Payload may include `{ action: 'create' | 'update', specId?, specType? }`.\n- `regeneration.completed` — finished a “regen/deploy” action (currently emitted on successful Studio deploy actions).\n- `studio.evolution.applied` — completed an Evolution session (payload commonly includes `{ evolutionSessionId }`).\n\nThese events are intentionally minimal and must avoid PII/secrets in payloads.\n"
-}];
-a(t$4);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/learning-journeys.docblock.js
-const t$3 = [{
-	id: `docs.tech.studio.learning-journeys`,
-	title: `Studio learning journeys (onboarding + coach)`,
-	summary: `DB-backed learning journeys tracked per organization: seeded tracks/steps, event-driven progress, XP/streaks, and a Studio coach surface.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/learning-journeys`,
-	tags: [
-		`studio`,
-		`learning`,
-		`onboarding`,
-		`journey`,
-		`graphql`,
-		`database`
-	],
-	body: `# Studio learning journeys
-
-Studio supports **DB-backed learning journeys** (onboarding tracks + ambient coach tips) that are advanced by **recorded learning events**.
-
-> See also: \`/docs/tech/studio/learning-events\` for event naming + payload guardrails.
-
-## Scope (multi-tenancy)
-
-- Progress is tracked **per organization** (tenant/workspace), via a \`Learner\` record keyed by \`(userId, organizationId)\`.
-- Learning events are stored as \`StudioLearningEvent\` under the Studio DB schema, scoped to an organization (optionally a project).
-
-## Persistence model (Prisma)
-
-Learning journey progress lives in the \`lssm_learning\` schema:
-
-- \`Learner\` — one per \`(userId, organizationId)\`
-- \`OnboardingTrack\` — seeded track definitions (trackKey, name, metadata)
-- \`OnboardingStep\` — seeded step definitions (stepKey, completionCondition, xpReward, metadata)
-- \`OnboardingProgress\` — learner × track progress (progress %, xpEarned, completedAt, dismissedAt)
-- \`OnboardingStepCompletion\` — append-only completion records (stepKey, status, xpEarned, completedAt)
-
-## Track definition source (spec-first)
-
-- Canonical track specs live in \`@lssm/example.learning-journey-registry\`.
-- The Studio API seeds/updates the DB definitions via an idempotent “ensure tracks” routine.
-- The DB is kept aligned with track specs (stale steps are removed) to prevent drift and unblock completion.
-
-## Progress advancement (event-driven)
-
-1) UI records an event via GraphQL \`recordLearningEvent\`
-2) Backend creates \`StudioLearningEvent\`
-3) Backend advances onboarding by matching the new event against step completion conditions
-4) Backend persists step completions and recomputes:
-   - \`progress\` percentage
-   - \`xpEarned\` (including streak/completion bonuses when configured)
-   - track completion state (\`completedAt\`)
-
-## GraphQL API (Studio)
-
-- \`myOnboardingTracks(productId?, includeProgress?)\`
-  - returns all tracks + optional progress for the current learner
-- \`myOnboardingProgress(trackKey)\`
-  - returns progress + step completion list for a single track
-- \`dismissOnboardingTrack(trackKey)\`
-  - marks a track dismissed for the learner (prevents auto-coach)
-
-## UI routes/surfaces (web)
-
-- \`/studio/learning\` — learning hub (track list + progress widget)
-- \`/studio/learning/{trackKey}\` — track detail (steps + map)
-- Studio shell mounts a **coach sheet** that can auto-open for incomplete, non-dismissed onboarding.
-
-## Security + data hygiene
-
-- Do not put secrets/PII in \`payload\` fields of learning events.
-- Prefer shallow payload filters (small, stable keys).
-`
-}];
-a(t$3);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/project-access-teams.docblock.js
-const t$2 = [{
-	id: `docs.tech.studio.project-access-teams`,
-	title: `Studio Project Access via Teams`,
-	summary: `Projects live under organizations; team sharing refines access with an admin/owner override.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/project-access-teams`,
-	tags: [
-		`studio`,
-		`projects`,
-		`teams`,
-		`rbac`,
-		`access-control`
-	],
-	body: `# Studio Project Access via Teams
-
-Studio access control is **organization-first** with optional **team-based sharing**.
-
-## Data model
-
-- \`Team\` and \`TeamMember\` define team membership inside an organization.
-- \`StudioProject\` is owned by an organization.
-- \`StudioProjectTeam\` links projects to 0..N teams.
-
-## Access rules
-
-- **Admins/owners**: always have access to all projects in the organization.
-- **Org-wide projects**: if a project has **no team links**, all organization members can access it.
-- **Team-scoped projects**: if a project has **one or more team links**, a user must be a member of at least one linked team.
-
-## GraphQL surfaces
-
-- Read:
-  - \`myStudioProjects\` (returns only projects you can access)
-  - \`studioProjectBySlug(slug)\` (enforces the same access rules)
-  - \`myTeams\`
-  - \`projectTeams(projectId)\`
-
-- Write:
-  - \`createStudioProject(input.teamIds?)\` (teamIds optional)
-  - \`setProjectTeams(projectId, teamIds)\` (admin-only)
-
-## Related
-+
-+- Team administration + invitations: see \`/docs/tech/studio/team-invitations\`.
-+
-## Notes
-
-Payloads and events must avoid secrets/PII. For Sandbox, the model remains local-first and unlogged.
-`
-}];
-a(t$2);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/studio/team-invitations.docblock.js
-const t$1 = [{
-	id: `docs.tech.studio.team-invitations`,
-	title: `Studio Teams & Invitations`,
-	summary: `Admin-only team management and email invitation flow to join an organization and optionally a team.`,
-	kind: `reference`,
-	visibility: `public`,
-	route: `/docs/tech/studio/team-invitations`,
-	tags: [
-		`studio`,
-		`teams`,
-		`invitations`,
-		`access-control`,
-		`onboarding`
-	],
-	body: `# Studio Teams & Invitations
-
-Studio uses **organization membership** as the base access model. Teams are optional and used to refine access to projects.
-
-## Who can manage teams?
-
-- **Admins/owners only**: create, rename, delete teams; manage project team access; issue invitations.
-
-## Invitation data model
-
-- \`Invitation\` rows are stored under an organization and target an **email** address.
-
-- An invitation can optionally target a \`teamId\`, which will grant the user membership in that team upon acceptance.
-
-Key fields:
-- \`email\`: invited address (must match the accepting user's account email)
-
-- \`status\`: \`pending | accepted | declined | expired\`
-
-- \`teamId?\`: optional team to join
-
-- \`inviterId\`: user who issued the invitation
-
-## GraphQL surfaces
-
-- Team CRUD (admin-only):
-
-  - \`createTeam(name)\`
-
-  - \`renameTeam(teamId, name)\`
-
-  - \`deleteTeam(teamId)\`
-
-
-- Invitations (admin-only):
-
-  - \`organizationInvitations\`
-
-  - \`inviteToOrganization(email, role?, teamId?)\` → returns \`inviteUrl\` and whether an email was sent
-
-## Accepting an invitation
-
-The invite link is served as:
-
-- \`/invite/{invitationId}\`
-
-Acceptance rules:
-- The user must be authenticated.
-
-- The authenticated user’s email must match \`Invitation.email\`.
-
-- If not already a member, create \`Member(userId, organizationId, role)\`.
-
-- If \`teamId\` is present, ensure \`TeamMember(teamId, userId)\`.
-
-- Mark invitation \`status='accepted'\` and set \`acceptedAt\`.
-
-- Set \`activeOrganizationId\` for the session so \`/studio/*\` routes work immediately.
-
-## Email delivery
-
-- If \`RESEND_API_KEY\` is set, the system attempts to send an email.
-
-- Otherwise, the UI uses the returned \`inviteUrl\` for manual copy/share.
-`
-}];
-a(t$1);
-
-//#endregion
-//#region ../../libs/contracts/dist/docs/tech/llm/llm-integration.docblock.js
-const t = [
-	{
-		id: `docs.tech.llm.overview`,
-		title: `LLM Integration Overview`,
-		summary: `Export specs to LLM-friendly formats, generate implementation guides, and verify implementations.`,
-		kind: `reference`,
-		visibility: `public`,
-		route: `/docs/tech/llm/overview`,
-		tags: [
-			`llm`,
-			`ai`,
-			`export`,
-			`guide`,
-			`verify`
-		],
-		body: `# LLM Integration
-
-ContractSpec provides first-class LLM integration to bridge specifications and AI coding agents.
-
-## Core Features
-
-### 1. Multi-Format Export
-
-Export specs to markdown in formats optimized for LLM consumption:
-
-- **Context format**: Summary for understanding (goal, context, acceptance criteria)
-- **Full format**: Complete spec with all details (I/O schemas, policy, events)
-- **Prompt format**: Actionable prompt with implementation instructions
-
-### 2. Implementation Guidance
-
-Generate agent-specific implementation plans:
-
-- **Claude Code**: Extended thinking mode with structured prompts
-- **Cursor CLI**: Background/composer mode with .mdc rules generation
-- **Generic MCP**: Standard format for any MCP-compatible agent
-
-### 3. Tiered Verification
-
-Verify implementations against specs:
-
-- **Tier 1 (Structure)**: Types, exports, imports validation
-- **Tier 2 (Behavior)**: Scenario coverage, error handling, events
-- **Tier 3 (AI Review)**: Semantic compliance analysis via LLM
-
-## Access Points
-
-| Surface | Commands/Tools |
-|---------|---------------|
-| CLI | \`contractspec llm export\`, \`guide\`, \`verify\`, \`copy\` |
-| MCP | \`llm.export\`, \`llm.guide\`, \`llm.verify\` tools |
-| VSCode | Export to LLM, Generate Guide, Verify, Copy commands |
-
-## Quick Start
-
-### CLI Usage
-
-\`\`\`bash
-# Export spec as markdown
-contractspec llm export path/to/my.spec.ts --format full
-
-# Generate implementation guide
-contractspec llm guide path/to/my.spec.ts --agent claude-code
-
-# Verify implementation
-contractspec llm verify path/to/my.spec.ts path/to/impl.ts --tier 2
-
-# Copy spec to clipboard
-contractspec llm copy path/to/my.spec.ts --format context
-\`\`\`
-
-### MCP Usage
-
-\`\`\`
-# Export spec
-llm.export { specPath: "path/to/my.spec.ts", format: "full" }
-
-# Generate guide
-llm.guide { specPath: "path/to/my.spec.ts", agent: "cursor-cli" }
-
-# Verify implementation
-llm.verify { specPath: "path/to/my.spec.ts", implementationPath: "path/to/impl.ts", tier: "2" }
-\`\`\`
-
-### Programmatic Usage
-
-\`\`\`typescript
-import { specToFullMarkdown, specToAgentPrompt } from '@lssm/lib.contracts/llm';
-import { createAgentGuideService, createVerifyService } from '@lssm/bundle.contractspec-workspace';
-
-// Export
-const markdown = specToFullMarkdown(mySpec);
-
-// Generate guide
-const guideService = createAgentGuideService({ defaultAgent: 'claude-code' });
-const guide = guideService.generateGuide(mySpec);
-
-// Verify
-const verifyService = createVerifyService();
-const result = await verifyService.verify(mySpec, implementationCode, {
-  tiers: ['structure', 'behavior']
-});
-\`\`\`
-`
-	},
-	{
-		id: `docs.tech.llm.export-formats`,
-		title: `LLM Export Formats`,
-		summary: `Detailed explanation of the three export formats for LLM consumption.`,
-		kind: `reference`,
-		visibility: `public`,
-		route: `/docs/tech/llm/export-formats`,
-		tags: [
-			`llm`,
-			`export`,
-			`markdown`
-		],
-		body: `# LLM Export Formats
-
-ContractSpec provides three export formats optimized for different LLM use cases.
-
-## Context Format
-
-Best for: Understanding what a spec does, providing background to LLMs.
-
-Includes:
-- Spec name, version, type
-- Goal and context
-- Description
-- Acceptance scenarios
-
-Example:
-
-\`\`\`markdown
-# users.createUser (v1)
-
-> Create a new user account with email verification.
-
-**Type:** command | **Stability:** stable
-
-## Goal
-Create a new user in the system and trigger email verification.
-
-## Context
-Part of the user onboarding flow. Called after signup form submission.
-
-## Acceptance Criteria
-### Happy path
-**Given:** Valid email and password
-**When:** User submits registration
-**Then:** Account is created, verification email is sent
-\`\`\`
-
-## Full Format
-
-Best for: Complete documentation, implementation reference.
-
-Includes everything:
-- All metadata
-- JSON schemas for I/O
-- Error definitions
-- Policy (auth, rate limits, PII)
-- Events emitted
-- Examples
-- Transport configuration
-
-## Prompt Format
-
-Best for: Feeding directly to coding agents.
-
-Includes:
-- Task header with clear instructions
-- Full spec context
-- Implementation requirements
-- Task-specific guidance (implement/test/refactor/review)
-- Expected output format
-
-The prompt format adapts based on task type:
-- **implement**: Full implementation with tests
-- **test**: Test generation for existing code
-- **refactor**: Refactoring while maintaining behavior
-- **review**: Code review against spec
-`
-	},
-	{
-		id: `docs.tech.llm.agent-adapters`,
-		title: `Agent Adapters`,
-		summary: `Adapters for different AI coding agents (Claude, Cursor, MCP).`,
-		kind: `reference`,
-		visibility: `public`,
-		route: `/docs/tech/llm/agent-adapters`,
-		tags: [
-			`llm`,
-			`agents`,
-			`claude`,
-			`cursor`,
-			`mcp`
-		],
-		body: `# Agent Adapters
-
-ContractSpec provides specialized adapters for different AI coding agents.
-
-## Claude Code Adapter
-
-Optimized for Anthropic Claude's extended thinking and code generation.
-
-Features:
-- Structured markdown with clear sections
-- Checklists for steps and verification
-- Icons for file operations (📝 create, ✏️ modify)
-- System prompt for ContractSpec context
-
-Usage:
-\`\`\`typescript
-const guideService = createAgentGuideService({ defaultAgent: 'claude-code' });
-const result = guideService.generateGuide(spec, { agent: 'claude-code' });
-// result.prompt.systemPrompt - Claude system context
-// result.prompt.taskPrompt - Task-specific instructions
-\`\`\`
-
-## Cursor CLI Adapter
-
-Optimized for Cursor's background/composer mode.
-
-Features:
-- Compact format for context efficiency
-- .mdc cursor rules generation
-- Integration with Cursor's file system
-- Concise step lists
-
-Generate Cursor Rules:
-\`\`\`typescript
-const cursorRules = guideService.generateAgentConfig(spec, 'cursor-cli');
-// Save to .cursor/rules/my-spec.mdc
-\`\`\`
-
-## Generic MCP Adapter
-
-Works with any MCP-compatible agent (Cline, Aider, etc.).
-
-Features:
-- Standard markdown format
-- Table-based metadata
-- JSON resource format support
-- Prompt message format
-
-The generic adapter is the default and works across all agents.
-
-## Choosing an Adapter
-
-| Agent | Best For | Key Features |
-|-------|----------|--------------|
-| Claude Code | Complex implementations | Extended thinking, detailed steps |
-| Cursor CLI | IDE-integrated work | Cursor rules, compact format |
-| Generic MCP | Any MCP agent | Universal compatibility |
-`
-	},
-	{
-		id: `docs.tech.llm.verification`,
-		title: `Implementation Verification`,
-		summary: `Tiered verification of implementations against specifications.`,
-		kind: `reference`,
-		visibility: `public`,
-		route: `/docs/tech/llm/verification`,
-		tags: [
-			`llm`,
-			`verify`,
-			`validation`,
-			`testing`
-		],
-		body: `# Implementation Verification
-
-ContractSpec provides tiered verification to check if implementations comply with specs.
-
-## Verification Tiers
-
-### Tier 1: Structure (Fast)
-
-Checks TypeScript structure against spec requirements:
-
-| Check | What it validates |
-|-------|------------------|
-| Handler export | Function is properly exported |
-| Contracts import | Imports from @lssm/lib.contracts |
-| Schema import | Imports from @lssm/lib.schema |
-| No \`any\` type | TypeScript strict compliance |
-| Error handling | Error codes are referenced |
-| Event emission | Event patterns exist |
-| Input validation | Validation patterns used |
-| Async patterns | Async/await for commands |
-
-### Tier 2: Behavior (Comprehensive)
-
-Checks implementation coverage of spec behaviors:
-
-| Check | What it validates |
-|-------|------------------|
-| Scenario coverage | Acceptance scenarios implemented |
-| Example coverage | Example I/O values referenced |
-| Error cases | All error conditions handled |
-| Event conditions | Events emitted correctly |
-| Idempotency | Idempotent patterns (if required) |
-
-### Tier 3: AI Review (Deep)
-
-Uses LLM for semantic analysis:
-
-- Does the implementation fulfill the spec's intent?
-- Are edge cases properly handled?
-- Is the code quality acceptable?
-- Are there any subtle violations?
-
-Requires AI API key configuration.
-
-## Running Verification
-
-\`\`\`typescript
-const verifyService = createVerifyService({
-  aiApiKey: process.env.ANTHROPIC_API_KEY, // Optional, for Tier 3
-  aiProvider: 'anthropic',
-});
-
-const result = await verifyService.verify(spec, implementationCode, {
-  tiers: ['structure', 'behavior'],
-  failFast: false,
-  includeSuggestions: true,
-});
-
-console.log(result.passed);  // true/false
-console.log(result.score);   // 0-100
-console.log(result.summary); // Human-readable summary
-\`\`\`
-
-## Verification Report
-
-The report includes:
-
-- **passed**: Overall compliance
-- **score**: 0-100 score
-- **issues**: Array of problems found
-- **suggestions**: Recommended fixes
-- **coverage**: Metrics on scenario/error/field coverage
-
-Each issue has:
-- **severity**: error, warning, or info
-- **category**: type, export, import, scenario, error_handling, semantic
-- **message**: Description of the issue
-- **suggestion**: How to fix it
-`
-	}
-];
-a(t);
-
 //#endregion
 //#region src/docs/learning-journey-ui-onboarding.docblock.ts
-a([{
+registerDocBlocks([{
 	id: "docs.examples.learning-journey-ui-onboarding",
 	title: "Learning Journey UI — Onboarding",
 	summary: "UI mini-app components for onboarding: checklists, snippets, and journey mapping.",