@lssm/example.learning-journey-registry 0.0.0-canary-20251217083314 → 1.41.0

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/telemetry-ingest.docblock.js

@@ -1,154 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/telemetry-ingest.docblock.js
-registerDocBlocks([{
-	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.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/templates/runtime.docblock.js

@@ -1,19 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/templates/runtime.docblock.js
-registerDocBlocks([{
-	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"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/vscode-extension.docblock.js

@@ -1,100 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/vscode-extension.docblock.js
-registerDocBlocks([{
-	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.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/workflows/overview.docblock.js

@@ -1,19 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/contracts/dist/docs/tech/workflows/overview.docblock.js
-registerDocBlocks([{
-	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"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/_virtual/rolldown_runtime.js

@@ -1,5 +0,0 @@
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/_virtual/rolldown_runtime.js
-var __esmMin = (fn, res) => () => (fn && (res = fn(fn = 0)), res);
-
-//#endregion
-export { __esmMin };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/components/atoms/Button.js

@@ -1,33 +0,0 @@
-import { Button } from "../../ui-kit-web/dist/ui/button.js";
-import "react";
-import { Fragment, jsx, jsxs } from "react/jsx-runtime";
-import { Loader2 } from "lucide-react";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/components/atoms/Button.js
-function Button$1({ children, loading, spinnerPlacement = "start", onPress, onPressIn, onPressOut, onLongPress, onTouchStart, onTouchEnd, onTouchCancel, onMouseDown, onMouseUp, onClick, className, disabled, ...rest }) {
-	const isDisabled = Boolean(disabled || loading);
-	const content = !rest.asChild ? /* @__PURE__ */ jsxs(Fragment, { children: [
-		loading && spinnerPlacement === "start" ? /* @__PURE__ */ jsx(Loader2, { className: "h-4 w-4 animate-spin" }) : null,
-		children,
-		loading && spinnerPlacement === "end" ? /* @__PURE__ */ jsx(Loader2, { className: "h-4 w-4 animate-spin" }) : null
-	] }) : children;
-	return /* @__PURE__ */ jsx(Button, {
-		...rest,
-		className,
-		disabled: isDisabled,
-		"aria-busy": loading ? true : void 0,
-		"aria-disabled": isDisabled ? true : void 0,
-		onPress: onPress || onClick,
-		onClick: onPress || onClick,
-		onMouseDown: onMouseDown || onPressIn,
-		onMouseUp: onMouseUp || onPressOut,
-		onTouchStart,
-		onTouchEnd: onTouchEnd || onPressOut,
-		onTouchCancel: onTouchCancel || onPressOut,
-		type: rest?.type ?? "button",
-		children: content
-	});
-}
-
-//#endregion
-export { Button$1 };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/ui-kit-web/dist/ui/button.js

@@ -1,55 +0,0 @@
-import { cn, init_utils } from "../ui-kit-core/dist/utils.js";
-import * as React$1 from "react";
-import { jsx } from "react/jsx-runtime";
-import { cva } from "class-variance-authority";
-import { Slot } from "@radix-ui/react-slot";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/ui-kit-web/dist/ui/button.js
-init_utils();
-const buttonVariants = cva("inline-flex items-center justify-center gap-2 whitespace-nowrap rounded-md text-sm font-medium transition-all disabled:pointer-events-none disabled:opacity-50 [&_svg]:pointer-events-none [&_svg:not([class*='size-'])]:size-4 shrink-0 [&_svg]:shrink-0 outline-hidden focus-visible:border-ring focus-visible:ring-ring/50 focus-visible:ring-[3px] aria-invalid:ring-destructive/20 dark:aria-invalid:ring-destructive/40 aria-invalid:border-destructive", {
-	variants: {
-		variant: {
-			default: "bg-primary text-primary-foreground hover:bg-primary/90",
-			destructive: "bg-destructive text-white hover:bg-destructive/90 focus-visible:ring-destructive/20 dark:focus-visible:ring-destructive/40 dark:bg-destructive/60",
-			outline: "border bg-background shadow-2xs hover:bg-accent hover:text-accent-foreground dark:bg-input/30 dark:border-input dark:hover:bg-input/50",
-			secondary: "bg-secondary text-secondary-foreground hover:bg-secondary/80",
-			ghost: "hover:bg-accent hover:text-accent-foreground dark:hover:bg-accent/50",
-			link: "text-primary underline-offset-4 hover:underline"
-		},
-		size: {
-			default: "h-9 px-4 py-2 has-[>svg]:px-3",
-			sm: "h-8 rounded-md gap-1.5 px-3 has-[>svg]:px-2.5",
-			lg: "h-10 rounded-md px-6 has-[>svg]:px-4",
-			icon: "size-9"
-		}
-	},
-	defaultVariants: {
-		variant: "default",
-		size: "default"
-	}
-});
-const Button = React$1.forwardRef(({ className, variant, size, asChild = false, ...props }, ref) => {
-	if (asChild) return /* @__PURE__ */ jsx(Slot, {
-		"data-slot": "button",
-		className: cn(buttonVariants({
-			variant,
-			size,
-			className
-		})),
-		...props
-	});
-	return /* @__PURE__ */ jsx("button", {
-		ref,
-		"data-slot": "button",
-		className: cn(buttonVariants({
-			variant,
-			size,
-			className
-		})),
-		...props
-	});
-});
-Button.displayName = "Button";
-
-//#endregion
-export { Button };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/ui-kit-web/dist/ui-kit-core/dist/utils.js

@@ -1,13 +0,0 @@
-import { __esmMin } from "../../../../_virtual/rolldown_runtime.js";
-import { clsx } from "clsx";
-import { twMerge } from "tailwind-merge";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/design-system/dist/ui-kit-web/dist/ui-kit-core/dist/utils.js
-function cn(...inputs) {
-	return twMerge(clsx(inputs));
-}
-var init_utils = __esmMin((() => {}));
-init_utils();
-
-//#endregion
-export { cn, init_utils };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui/progress.js

@@ -1,23 +0,0 @@
-'use client';
-
-import { cn } from "../ui-kit-core/dist/utils.js";
-import "react";
-import { jsx } from "react/jsx-runtime";
-import * as ProgressPrimitive from "@radix-ui/react-progress";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui/progress.js
-function Progress({ className, value, ...props }) {
-	return /* @__PURE__ */ jsx(ProgressPrimitive.Root, {
-		"data-slot": "progress",
-		className: cn("bg-primary/20 relative h-2 w-full overflow-hidden rounded-full", className),
-		...props,
-		children: /* @__PURE__ */ jsx(ProgressPrimitive.Indicator, {
-			"data-slot": "progress-indicator",
-			className: "bg-primary h-full w-full flex-1 transition-all",
-			style: { transform: `translateX(-${100 - (value || 0)}%)` }
-		})
-	});
-}
-
-//#endregion
-export { Progress };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui/utils.js

@@ -1,10 +0,0 @@
-import { clsx } from "clsx";
-import { twMerge } from "tailwind-merge";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui/utils.js
-function cn(...inputs) {
-	return twMerge(clsx(inputs));
-}
-
-//#endregion
-export { cn };

package/dist/examples/learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui-kit-core/dist/utils.js

@@ -1,10 +0,0 @@
-import { clsx } from "clsx";
-import { twMerge } from "tailwind-merge";
-
-//#region ../learning-journey-ui-onboarding/dist/examples/learning-journey-ui-shared/dist/libs/ui-kit-web/dist/ui-kit-core/dist/utils.js
-function cn(...inputs) {
-	return twMerge(clsx(inputs));
-}
-
-//#endregion
-export { cn };

package/dist/examples/learning-journey-ui-onboarding/dist/index.js

@@ -1,11 +0,0 @@
-import { Overview } from "./views/Overview.js";
-import { StepChecklist } from "./components/StepChecklist.js";
-import { Steps } from "./views/Steps.js";
-import { ProgressView } from "./views/Progress.js";
-import { JourneyMap } from "./components/JourneyMap.js";
-import { Timeline } from "./views/Timeline.js";
-import { OnboardingMiniApp } from "./OnboardingMiniApp.js";
-import "./views/index.js";
-import "./components/CodeSnippet.js";
-import "./components/index.js";
-import "./docs/index.js";

package/dist/examples/learning-journey-ui-onboarding/dist/libs/contracts/dist/docs/PUBLISHING.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "./registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/libs/contracts/dist/docs/PUBLISHING.docblock.js
-registerDocBlocks([{
-	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\n\nThis guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).\n\n## Release Tracks\n\n| Track | Branch | npm Tag | Frequency | Versioning | Use Case |\n|-------|--------|---------|-----------|------------|----------|\n| **Stable** | `release` | `latest` | Manual | SemVer (e.g., `1.7.4`) | Production, external users |\n| **Canary** | `main` | `canary` | Every Push | Snapshot (e.g., `1.7.4-canary...`) | Dev, internal testing |\n\n## Prerequisites\n\n- ✅ `NPM_TOKEN` secret is configured in GitHub (owner or automation token with _publish_ scope).\n- ✅ `GITHUB_TOKEN` (built-in) has permissions to create PRs (enabled by default in new repos).\n- ✅ For stable releases: `release` branch exists and is protected.\n\n## Canary Workflow (Automatic)\n\nEvery commit pushed to `main` triggers the `.github/workflows/publish-canary.yml` workflow.\n\n1. **Trigger**: Push to `main`.\n2. **Versioning**: Runs `changeset version --snapshot canary` to generate a temporary snapshot version.\n3. **Publish**: Packages are published to npm with the `canary` tag using `changeset publish --tag canary`.\n\n### Consuming Canary Builds\n\nTo install the latest bleeding-edge version:\n\n```bash\nnpm install @lssm/lib.contracts@canary\n# or\nbun add @lssm/lib.contracts@canary\n```\n\n## Stable Release Workflow (Manual)\n\nStable releases are managed via the `release` branch using the standard [Changesets Action](https://github.com/changesets/action).\n\n1. **Develop on `main`**: Create features and fixes.\n2. **Add Changesets**: Run `bun changeset` to document changes and impact (major/minor/patch).\n3. **Merge to `release`**: When ready to ship, open a PR from `main` to `release` or merge manually.\n4. **\"Version Packages\" PR**:\n   - The GitHub Action detects new changesets and automatically creates a Pull Request titled **\"Version Packages\"**.\n   - This PR contains the version bumps and updated `CHANGELOG.md` files.\n5. **Merge & Publish**:\n   - Review and merge the \"Version Packages\" PR.\n   - The Action runs again, detects the versions have been bumped, builds the libraries, and publishes them to npm with the `latest` tag.\n\n### Publishing Steps\n\n1. Ensure all changesets are present on `main`.\n2. Merge `main` into `release`:\n   ```bash\n   git checkout release\n   git pull origin release\n   git merge main\n   git push origin release\n   ```\n3. Go to GitHub Pull Requests. You will see a **\"Version Packages\"** PR created by the bot.\n4. Merge that PR.\n5. The release is now live on npm!\n\n## Manual Verification (Optional)\n\nBefore publishing a new version you can run:\n\n```bash\nbun run build:not-apps\nnpx npm-packlist --json packages/libs/contracts\n```\n\n## Rollback\n\nIf 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.\n"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/libs/contracts/dist/docs/accessibility_wcag_compliance_specs.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "./registry.js";
-
-//#region ../learning-journey-ui-onboarding/dist/libs/contracts/dist/docs/accessibility_wcag_compliance_specs.docblock.js
-registerDocBlocks([{
-	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**\n\n> **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)**.\n\n---\n\n## 0) Scope & Principles\n\n- **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.\n- **Principles:** Perceivable, Operable, Understandable, Robust (POUR).\n- **Rule of ARIA:** “No ARIA is better than bad ARIA.” Prefer native elements.\n- **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.\n- **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.\n\n---\n\n## 1) Design Requirements (Design System & Tokens)\n\n**1.1 Color & Contrast**\n\n- Body text, icons essential to meaning: **≥\xA04.5:1**; large text (≥\xA018.66px regular / 14px bold): **≥\xA03:1**.\n- Interactive states (default/hover/active/disabled/focus) must maintain contrast **≥\xA03:1** against adjacent colors; text within components follows text ratios.\n- Provide light & dark themes with tokens that guarantee minimums. **Never rely solely on color** to convey meaning; pair with text, shape, or icon.\n\n**1.2 Focus Indicators (WCAG\xA02.4.11/12)**\n\n- Every interactive element has a **visible focus** with clear offset; indicator contrast **≥\xA03:1** vs adjacent colors and indicator **area ≥\xA02\xA0CSS\xA0px** thick.\n- Focus **must not be obscured** by sticky headers/footers or scroll containers.\n\n**1.3 Motion & Preferences**\n\n- Respect `prefers-reduced-motion`: suppress large parallax, auto‑animations; provide instant alternatives.\n- Avoid motion that could trigger vestibular issues; under PRM, use fade/scale under **150ms**.\n\n**1.4 Target Size (2.5.8)**\n\n- Hit areas **≥\xA024×24\xA0CSS\xA0px** (web) and **≥\xA044×44\xA0dp** (mobile) unless exempt.\n\n**1.5 Typography & Layout**\n\n- Support zoom to **400%** without loss of content/functionality; responsive reflow at **320\xA0CSS\xA0px** width.\n- Maintain clear heading hierarchy (h1…h6), one **h1** per view.\n\n- 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`.\n- 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.\n- When increasing font size, ensure line height supports readability. Prefer Tailwind defaults or `leading-relaxed`/`leading-7` for body text where dense blocks appear.\n\n**1.6 Iconography & Imagery**\n\n- Decorative images: `alt=\"\"` or `aria-hidden=\"true\"`.\n- Informative images: concise, specific **alt**; complex charts require a **data table or long description**.\n\n---\n\n## 2) Content Requirements (UX Writing)\n\n- Links say **what happens** (avoid “click here”).\n- Buttons start with verbs; avoid ambiguous labels.\n- Form labels are **visible**; placeholders are **not labels**.\n- Error messages: human + programmatic association; avoid color‑only.\n- Authentication: allow **copy/paste**, password managers, and avoid cognitive tests alone (**3.3.7/3.3.8/3.3.9**).\n- Avoid CAPTCHAs that block users; if unavoidable, provide **multiple alternatives** (logic-free).\n\n---\n\n## 3) Engineering Requirements (Web — Next.js/React)\n\n> 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.\n\n**3.1 Semantics & Landmarks**\n\n- Use native elements: `<button>`, `<a href>`, `<label for>`, `<fieldset>`, `<legend>`, `<table>`, etc.\n- Landmarks per page: `header`, `nav`, `main`, `aside`, `footer`. Provide a **Skip to main content** link.\n- Provide a **Route Announcer** (`aria-live=\"polite\"`) and move focus to page **h1** after navigation.\n\n**3.2 Keyboard**\n\n- All functionality available with keyboard alone. Tab order follows DOM/visual order; **no keyboard traps**.\n- Common bindings:\n  - Space/Enter → activate button; Enter on link;\n  - Esc closes dialogs/menus;\n  - Arrow keys for lists/menus/tablists with **roving tabindex**.\n\n**3.3 Focus Management**\n\n- On route change (Next.js), move focus to the page `<h1>` or container and announce via a live region.\n- Dialogs/menus: **trap focus** inside; return focus to invoking control on close.\n- Don’t steal focus except after explicit user action.\n\n**3.4 Forms**\n\n- Each input has a `<label>` or `aria-label`. Group related inputs with `<fieldset><legend>`.\n- Associate errors via `aria-describedby` or inline IDs; announce with `role=\"alert\"` (assertive only for critical).\n- Provide **autocomplete** tokens for known fields; show **inline validation** and do not block on **onBlur** alone.\n\n**3.5 ARIA Usage**\n\n- Only when needed; match patterns (dialog, menu, combobox, tablist, listbox) per ARIA Authoring Practices.\n- Ensure **name/role/value** are programmatically determinable.\n\n**3.6 Media**\n\n- Videos: **captions**; provide **transcripts** for audio; audio descriptions for essential visual info.\n- No auto‑playing audio. Auto‑playing video must be muted and pausable; provide controls.\n\n**3.7 Tables & Data**\n\n- Use `<th scope>` for headers; captions via `<caption>`; announce sorting via `aria-sort`.\n- Provide CSV/JSON export where charts are primary.\n\n**3.8 Performance & Robustness**\n\n- Avoid content shifts that move focus; reserve space or use skeletons.\n- Maintain accessible names through hydration/SSR; avoid `dangerouslySetInnerHTML` where possible.\n\n**3.9 Next.js specifics**\n\n- Use `next/link` for navigation; ensure links are **links**, not buttons.\n- `next/image` must include **alt** (empty if decorative).\n- Announce route changes with a **global live region** and shift focus to the new view.\n\n**3.10 Accessibility library integration**\n\n- 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:\n\n```tsx\n// app/layout.tsx\nimport '@lssm/lib.accessibility'; // includes tokens and provider exports\n// or if needed: import '@lssm/lib.accessibility/src/styles.css';\n```\n\n- Wrap the app with `AccessibilityProvider` and include an element with `id=\"main\"` for the skip link target.\n\n---\n\n## 3b) lssm/ui-kit-web — Component Patterns & Defaults\n\n> Source: `packages/lssm/libs/ui-kit-web/ui/*`\n\n- **Button/Input/Textarea**: Built‑in `focus-visible` rings; ensure visible labels via `FormLabel` or `aria-label`.\n- **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.\n- **Dialog/Sheet/Dropdown**: Use Radix wrappers for focus‑trap and return‑focus. Provide `DialogTitle` + `DialogDescription` for name/description.\n- **Select/Combobox**: Prefer `SelectTrigger` with visible label; for icon‑only triggers, supply `aria-label`. Document examples in each app.\n- **Tabs**: Use `TabsList`, `TabsTrigger`, `TabsContent`; names are programmatically determinable.\n- **Toast/Toaster**: Prefer non‑blocking announcements; map critical to assertive region; include action buttons with clear labels.\n- **Table**: Use `TableCaption`; ensure `TableHead` cells use proper `scope`. Provide `aria-sort` on sortable headers.\n- **Utilities to add (repo action)**:\n  - `SkipLink` component and pattern in layouts.\n  - `RouteAnnouncer` (`aria-live=\"polite\"`) and **FocusOnRouteChange** helper.\n  - `VisuallyHidden` wrapper (Radix visually-hidden or minimal utility).\n  - `useReducedMotion` helper; honor in animated components.\n  - Touch‑size variants (≥44×44) for interactive atoms.\n\n---\n\n## 4) Engineering Requirements (Mobile — Expo/React\xA0Native)\n\n- Set `accessibilityLabel`, `accessibilityHint`, and `accessibilityRole` on touchables.\n- Ensure **hit slop** / min size **≥\xA044×44\xA0dp**.\n- Support Dynamic Type / font scaling; no clipped text at **200%**.\n- Respect **Invert Colors** and **Reduce Motion**; avoid flashing.\n- Group related items with `accessibilityElements` ordering; hide decoration with `accessible={false}` or `importantForAccessibility=\"no-hide-descendants\"` when appropriate.\n- Test with **VoiceOver (iOS)** and **TalkBack (Android)**.\n\n---\n\n## 5) Component Patterns (Acceptance Rules)\n\n**Buttons & Links**\n\n- Use `<button>` for actions, `<a href>` for navigation. Provide disabled states that are perceivable beyond color.\n\n**Navigation**\n\n- Provide **Skip link**. One primary nav landmark. Indicate current page (`aria-current=\"page\"`).\n\n**Menus/Combobox/Autocomplete**\n\n- Follow ARIA patterns: focus moves into list; `aria-expanded`, `aria-controls`, `aria-activedescendant` when applicable; Esc closes; typing filters.\n\n**Modals/Dialogs**\n\n- `role=\"dialog\"` or `alertdialog` with **label**; focus trapped; background inert; Esc closes; return focus to trigger.\n\n**Tabs**\n\n- `role=\"tablist\"`; tabs are in the tab order; arrow keys switch focus; content is `role=\"tabpanel\"` with `aria-labelledby`.\n\n**Toasts/Notifications**\n\n- Non-critical: `aria-live=\"polite\"`; critical: `role=\"alert\"` sparingly.\n\n**Infinite Scroll / “Load More”**\n\n- Provide **Load more** control; announce new content to SR; preserve keyboard position.\n\n**Drag & Drop (2.5.7)**\n\n- Provide **non‑drag** alternative (e.g., move up/down buttons).\n\n**Charts & Maps**\n\n- Provide **table alternative** or textual summary; keyboard access to datapoints where interactive.\n\n---\n\n## 6) Testing & CI (Blocking Gates)\n\n**Static & Unit**\n\n- `eslint-plugin-jsx-a11y` — error on violations.\n- `jest-axe` — unit tests for components.\n\n**Automated Integration**\n\n- `axe-core` via Playwright or Cypress on critical flows.\n- `pa11y-ci` on key routes; threshold: **0 Critical / 0 Serious** to merge.\n- Lighthouse CI a11y score **≥\xA095** on target pages.\n\n**Manual QA (per release)**\n\n- **Keyboard patrol:** navigate primary flows without mouse.\n- **Screen reader smoke:** NVDA (Windows) or VoiceOver (macOS/iOS) across login, navigation, forms, dialogs.\n- **Zoom & Reflow:** 200–400% & 320\xA0px width.\n- **Color/Contrast check:** tokens in both themes.\n\n**Reporting**\n\n- A11y issues labeled: `a11y-blocker`, `a11y-bug`, `a11y-enhancement` with WCAG ref.\n\n---\n\n## 7) Repository‑Specific Adoption Plan\n\n- Centralize UI usage on `packages/lssm/libs/ui-kit-web` and de‑duplicate per‑app `components/ui` where feasible.\n- Introduce `SkipLink`, `RouteAnnouncer`, `FocusOnRouteChange`, and `VisuallyHidden` in `ui-kit-web`. Adopt in app layouts (`app/layout.tsx`) first.\n- Add `useReducedMotion` and wire into animated components (e.g., `drawer`, `tooltip`, `carousel`).\n- Add touch‑size variants to `Button`, `IconButton`, `TabsTrigger`, toggles.\n- Document Select label patterns and error association in Forms.\n\n---\n\n## 8) Code Snippets\n\n**Skip Link**\n\n```html\n<a\n  class=\"sr-only focus:not-sr-only focus-visible:outline focus-visible:ring-4 focus-visible:ring-offset-2\"\n  href=\"#main\"\n  >Skip to main content</a\n>\n<main id=\"main\">…</main>\n```\n\n**Dialog (Radix + shadcn/ui) — essentials**\n\n```tsx\n// Ensure label, description, focus trap, and return focus on close remain intact\n<Dialog>\n  <DialogTrigger asChild>\n    <button aria-haspopup=\"dialog\">Open settings</button>\n  </DialogTrigger>\n  <DialogContent aria-describedby=\"settings-desc\">\n    <DialogTitle>Settings</DialogTitle>\n    <p id=\"settings-desc\">Update your preferences.</p>\n    <DialogClose asChild>\n      <button>Close</button>\n    </DialogClose>\n  </DialogContent>\n</Dialog>\n```\n\n**Form error association**\n\n```tsx\n<label htmlFor=\"email\">Email</label>\n<input id=\"email\" name=\"email\" type=\"email\" aria-describedby=\"email-err\" />\n<p id=\"email-err\" role=\"alert\">Enter a valid email.</p>\n```\n\n**Route change announcement (Next.js)**\n\n```tsx\n// Add once at app root\n<div\n  aria-live=\"polite\"\n  aria-atomic=\"true\"\n  id=\"route-announcer\"\n  className=\"sr-only\"\n/>\n```\n\n---\n\n## 9) Exceptions & Waivers\n\n- If a criterion cannot be met, file an issue with: context, attempted alternatives, WCAG reference, impact assessment, and a remediation date. **Temporary waivers only.**\n\n---\n\n## 10) Ownership\n\n- **Design:** maintains token contrast, component specs.\n- **Engineering:** enforces CI gates, implements patterns.\n- **QA:** runs manual checks per release.\n- **PM:** blocks release if AA not met on user‑visible flows.\n\n---\n\n## 11) References (internalize; no external dependency at runtime)\n\n- WCAG\xA02.2 (AA), EN\xA0301\xA0549. ARIA Authoring Practices. Platform HIG (Apple, Material).\n- `packages/lssm/libs/ui-kit-web` as the canonical UI source for web.\n\n> **Bottom line:** Shipping means **accessible by default**. We don’t trade a11y for speed; we bake it into speed.\n\n---\n\n## 12) Adoption Status (2025-09-23)\n\n- web-artisan: AccessibilityProvider integrated; sr-only/forced-colors applied; 44x44 targets; forms announce errors; jest-axe and cypress-axe in place.\n- 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.\n- 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.\n\n> CI gates: run eslint a11y, jest-axe on components, and cypress-axe on critical flows per app.\n\n---\n\n## 13) CI Hardening & Visual QA\n\n- Linting: Run eslint with jsx-a11y rules across all web apps; block on violations.\n- Unit: Run jest-axe for ui-kit-web and app-level components.\n- Integration: cypress-axe on key flows (auth, forms, dialogs, tables).\n- Synthetic scans: pa11y-ci on critical pages (0 Critical/Serious policy).\n- Performance/A11y audit: Lighthouse CI with a11y score >= 95 on target routes.\n- Artifacts: Upload pa11y and Lighthouse reports per PR; annotate failures.\n\n### Recent additions (2025-09-26)\n\n- AutocompleteInput (groceries): Upgraded to ARIA combobox pattern with `aria-controls`, `aria-activedescendant`, `Escape`/`Tab` handling, and labelled listbox.\n- Cypress a11y tests added for furniture and incidents modules on `/modules` and operators flows; checks run axe with critical/serious impacts.\n\n## 14) Accessibility Telemetry (PostHog)\n\n- Events (anonymized): a11y_pref_changed (text_scale, contrast_mode, reduce_motion), a11y_panel_opened.\n- Properties: app, route, previous_value, new_value, timestamp.\n- Dashboards: Adoption over time, per app/route; correlation with reduced bounce on forms.\n- Privacy: No PII; aggregate only.\n"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-onboarding/dist/libs/contracts/dist/docs/index.js

@@ -1,28 +0,0 @@
-import "./registry.js";
-import "./PUBLISHING.docblock.js";
-import "./accessibility_wcag_compliance_specs.docblock.js";
-import "./tech/PHASE_1_QUICKSTART.docblock.js";
-import "./tech/PHASE_2_AI_NATIVE_OPERATIONS.docblock.js";
-import "./tech/PHASE_3_AUTO_EVOLUTION.docblock.js";
-import "./tech/PHASE_4_PERSONALIZATION_ENGINE.docblock.js";
-import "./tech/PHASE_5_ZERO_TOUCH_OPERATIONS.docblock.js";
-import "./tech/lifecycle-stage-system.docblock.js";
-import "./tech/presentation-runtime.docblock.js";
-import "./tech/auth/better-auth-nextjs.docblock.js";
-import "./tech/schema/README.docblock.js";
-import "./tech/templates/runtime.docblock.js";
-import "./tech/workflows/overview.docblock.js";
-import "./tech/mcp-endpoints.docblock.js";
-import "./tech/vscode-extension.docblock.js";
-import "./tech/telemetry-ingest.docblock.js";
-import "./tech/contracts/openapi-export.docblock.js";
-import "./tech/studio/workspaces.docblock.js";
-import "./tech/studio/sandbox-unlogged.docblock.js";
-import "./tech/studio/workspace-ops.docblock.js";
-import "./tech/studio/project-routing.docblock.js";
-import "./tech/studio/platform-admin-panel.docblock.js";
-import "./tech/studio/learning-events.docblock.js";
-import "./tech/studio/learning-journeys.docblock.js";
-import "./tech/studio/project-access-teams.docblock.js";
-import "./tech/studio/team-invitations.docblock.js";
-import "./tech/llm/llm-integration.docblock.js";