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

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS.docblock.js

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

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/auth/better-auth-nextjs.docblock.js

@@ -1,79 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/auth/better-auth-nextjs.docblock.js
-registerDocBlocks([{
-	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.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/lifecycle-stage-system.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/lifecycle-stage-system.docblock.js
-registerDocBlocks([{
-	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\n\nThis 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.\n\n---\n\n### 1. Architecture Overview\n\n```\n┌──────────────────────┐\n│ @lssm/lib.lifecycle  │  Types, enums, helpers (pure data)\n└───────────┬──────────┘\n            │\n┌───────────▼──────────┐    ┌───────────────────────────┐\n│ modules/lifecycle-   │    │ modules/lifecycle-advisor  │\n│ core (detection)     │    │ (guidance & ceremonies)    │\n└───────────┬──────────┘    └───────────┬───────────────┘\n            │                           │\n            ├────────────┬──────────────┤\n            ▼            ▼              ▼\n  Adapters: analytics, intent, questionnaires\n            │\n┌───────────▼──────────┐\n│ bundles/lifecycle-   │  Managed service for Studio\n│ managed              │  (REST handlers, AI agent)     │\n└───────────┬──────────┘\n            │\n  ContractSpec Studio surfaces\n  (web/mobile APIs, CLI, docs)\n```\n\n- **Libraries** provide shared vocabulary.\n- **Modules** encapsulate logic, accepting adapters to avoid environment-specific code.\n- **Bundles** compose modules, register agents/events, and expose APIs for Studio.\n- **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.\n\n---\n\n### 2. Core Library (`@lssm/lib.lifecycle`)\n\n- Stage enum (0–6) with metadata (`question`, `signals`, `traps`).\n- Axes types (`ProductPhase`, `CompanyPhase`, `CapitalPhase`).\n- `LifecycleSignal` (source, metric, value, timestamp).\n- `LifecycleMetricSnapshot` (aggregated numbers).\n- `LifecycleMilestone`, `LifecycleAction`, `LifecycleAssessment` interfaces.\n- Utility helpers:\n  - `formatStageSummary(stage, assessment)`\n  - `rankStageCandidates(scores)`\n\nThe library exports **no runtime dependencies** so it can be imported from apps, modules, and bundles alike.\n\n---\n\n### 3. Lifecycle Core Module\n\n**Location:** `packages/modules/lifecycle-core/`\n\n#### Components\n1. **StageSignalCollector**\n   - Accepts adapter interfaces:\n     - `AnalyticsAdapter` (pulls metrics from `@lssm/lib.analytics` or fixture streams).\n     - `IntentAdapter` (hooks into `@lssm/lib.observability` intent detectors or logs).\n     - `QuestionnaireAdapter` (loads JSON questionnaires and responses).\n   - Produces normalized `LifecycleSignal[]`.\n\n2. **StageScorer**\n   - Weighted scoring model:\n     - Base weight per stage (reflecting expected maturity).\n     - Feature weights (retention, revenue, team size, qualitative feedback).\n     - Confidence computed via variance of contributing signals.\n   - Supports pluggable scoring matrices via JSON config.\n   - Accepts sparse metric snapshots; the orchestrator sanitizes metrics to numeric-only records before persisting assessments so downstream analytics stay consistent.\n\n3. **LifecycleOrchestrator**\n   - Coordinates collectors + scorer.\n   - Returns `LifecycleAssessment` with:\n     - `stage`, `confidence`, `axisSnapshot`, `signalsUsed`.\n     - Recommended focus areas (high-level categories only).\n   - Emits events (internally) when stage confidence crosses thresholds (consumed later by bundle).\n\n4. **LifecycleMilestonePlanner**\n   - Loads `milestones-catalog.json` (no DB).\n   - Filters upcoming milestones per stage + axis.\n   - Tracks completion using provided IDs (caller persists).\n\n#### Data Files\n- `configs/stage-weights.json`\n- `configs/milestones-catalog.json`\n- `questionnaires/stage-readiness.json`\n\n#### Extension Hooks\n- All adapters exported as TypeScript interfaces.\n- Implementations for analytics/intent can live in bundles or apps without modifying module code.\n\n---\n\n### 4. Lifecycle Advisor Module\n\n**Location:** `packages/modules/lifecycle-advisor/`\n\n#### Components\n1. **LifecycleRecommendationEngine**\n   - Consumes `LifecycleAssessment`.\n   - Maps gaps to `LifecycleAction[]` using rule tables (`stage-playbooks.ts`).\n   - Supports override hooks for customer-specific rules.\n\n2. **ContractSpecLibraryRecommender**\n   - Maintains mapping from stage → recommended libraries/modules/bundles.\n   - Returns prioritized list with rationale and adoption prerequisites.\n\n3. **LifecycleCeremonyDesigner**\n   - Provides textual/structural data for ceremonies (title, copy, animation cues, soundtrack references).\n   - Ensures low-tech friendly instructions (clear copy, undo guidance).\n\n4. **AI Hooks**\n   - Defines prompt templates and tool manifests for lifecycle advisor agents (consumed by bundles).\n   - Keeps actual LLM integration outside module.\n\n---\n\n### 5. Managed Bundle (`lifecycle-managed`)\n\n**Responsibilities**\n- Wire modules together.\n- Provide HTTP/GraphQL handlers (exact transport optional).\n- Register LifecycleAdvisorAgent via `@lssm/lib.ai-agent`.\n- LifecycleAdvisorAgent meta: domain `operations`, owners `team-lifecycle`, stability `experimental`, tags `guide/lifecycle/ops` so ops tooling can route incidents quickly.\n- Emit lifecycle events through `@lssm/lib.bus` + `@lssm/lib.analytics`.\n- Integrate with `contractspec-studio` packages:\n  - Use Studio contracts for authentication/tenant context (without accessing tenant DBs).\n  - Store assessments in Studio-managed storage abstractions (in-memory or file-based for now).\n\n**APIs**\n- `POST /lifecycle/assessments`: Accepts metrics + optional questionnaire answers. Returns `LifecycleAssessment`.\n- `GET /lifecycle/playbooks/:stage`: Returns stage playbook + ceremonies.\n- `POST /lifecycle/advise`: Invokes LifecycleAdvisorAgent with context.\n\n**Events**\n- `LifecycleAssessmentCreated`\n- `LifecycleStageChanged`\n- `LifecycleGuidanceConsumed`\n\n---\n\n### 6. Library Enhancements\n\n| Library | Enhancement |\n| --- | --- |\n| `@lssm/lib.analytics` | Lifecycle metric collectors, helper to emit stage events, adapter implementation used by `StageSignalCollector`. |\n| `@lssm/lib.evolution` | Accepts `LifecycleContext` when ranking spec anomalies/suggestions. |\n| `@lssm/lib.growth` | Stage-specific experiment templates + guardrails referencing lifecycle enums. |\n| `@lssm/lib.observability` | Lifecycle KPI pipeline definitions (drift detection, regression alerts). |\n\nEach enhancement must import stage types from `@lssm/lib.lifecycle`.\n\n---\n\n### 7. Feature Flags & Progressive Delivery\n\n- Add new flags in progressive-delivery library:\n  - `LIFECYCLE_DETECTION_ALPHA`\n  - `LIFECYCLE_ADVISOR_ALPHA`\n  - `LIFECYCLE_MANAGED_SERVICE`\n- Bundles/modules should check flags before enabling workflows.\n- Flags referenced in docs + Studio UI to avoid accidental exposure.\n\n---\n\n### 8. Analytics & Telemetry\n\n- Events defined in analytics library; consumed by bundle/app:\n  - `lifecycle_assessment_run`\n  - `lifecycle_stage_changed`\n  - `lifecycle_guidance_consumed`\n- Observability pipeline includes:\n  - Composite lifecycle health metric (weighted sum of KPIs).\n  - Drift detection comparing stage predictions over time.\n  - Alert manager recipes for regression (e.g., PMF drop).\n\n---\n\n### 9. Testing Strategy\n\n1. **Unit**\n   - StageScorer weight matrix.\n   - RecommendationEngine mapping.\n   - Library recommender stage coverage.\n\n2. **Contract**\n   - Adapters: ensure mock adapters satisfy interfaces.\n   - Bundles: ensure HTTP handlers respect request/response contracts even without persistence.\n\n3. **Integration**\n   - CLI example runs detection + guidance end-to-end on fixture data.\n   - Dashboard example renders assessments, verifying JSON structures remain stable.\n\n---\n\n### 10. Implementation Checklist\n\n- [ ] Documentation (product, tech, ops, user).\n- [ ] Library creation (`@lssm/lib.lifecycle`).\n- [ ] Modules (`lifecycle-core`, `lifecycle-advisor`).\n- [ ] Bundle (`lifecycle-managed`) + Studio wiring.\n- [ ] Library enhancements (analytics/evolution/growth/observability).\n- [ ] Examples (CLI + dashboard).\n- [ ] Feature flags + telemetry.\n- [ ] Automated tests + fixtures.\n\nKeep 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\n\n\n"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/mcp-endpoints.docblock.js

@@ -1,36 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/mcp-endpoints.docblock.js
-registerDocBlocks([{
-	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
-
-Three dedicated MCP servers keep AI agents efficient and scoped:
-
-- **Docs MCP**: \`/api/mcp/docs\` — exposes DocBlocks as resources + presentations. Tool: \`docs.search\`.
-- **CLI MCP**: \`/api/mcp/cli\` — surfaces CLI quickstart/reference/README and suggests commands. Tool: \`cli.suggestCommand\`.
-- **Internal MCP**: \`/api/mcp/internal\` — internal routing hints, playbook, and example registry access. Tool: \`internal.describe\`.
-
-### Usage notes
-- Transports are HTTP POST (streamable HTTP); SSE is disabled.
-- Resources are namespaced (\`docs://*\`, \`cli://*\`, \`internal://*\`) and are read-only.
-- Internal MCP also exposes the examples registry via \`examples://*\` resources:
-  - \`examples://list?q=<query>\`
-  - \`examples://example/<id>\`
-- Prompts mirror each surface (navigator, usage, bootstrap) for quick agent onboarding.
-- GraphQL remains at \`/graphql\`; health at \`/health\`.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/presentation-runtime.docblock.js

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

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/schema/README.docblock.js

@@ -1,19 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/schema/README.docblock.js
-registerDocBlocks([{
-	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)\n\nWe adopt Prisma multi‑file schema (GA ≥ v6.7) to organize each database’s models by domain and to import core LSSM module schemas locally.\n\nCanonical layout per DB:\n\n```\nprisma/\n  schema/\n    main.prisma             # datasource + generators only\n    imported/\n      lssm_sigil/*.prisma   # imported models/enums only (no datasource/generator)\n      lssm_content/*.prisma # idem\n    <domain>/*.prisma       # vertical‑specific models split by bounded context\n```\n\nNotes:\n\n- Imported files contain only `model` and `enum` blocks (strip `datasource`/`generator`).\n- 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\"]`.\n- Use `@lssm/app.cli-database` CLI: `database import|check|generate|migrate:*|seed` to manage a single DB; `@lssm/app.cli-databases` orchestrates multiple DBs.\n\n## Typed merger config\n\n- Define imported module list once per DB with a typed config:\n\n```ts\n// prisma-merger.config.ts\nimport { defineMergedPrismaConfig } from '@lssm/app.cli-database';\n\nexport default defineMergedPrismaConfig({\n  modules: [\n    '@lssm/app.cli-database-sigil',\n    '@lssm/app.cli-database-content',\n    // ...\n  ],\n});\n```\n\n- Then run `database import --target .` (no need to pass `--modules`).\n\n## Prisma Config (prisma.config.ts)\n\nWe use Prisma Config per official docs to point Prisma to the multi-file schema folder and migrations:\n\n```ts\n// prisma.config.ts\nimport path from 'node:path';\nimport { defineConfig } from 'prisma/config';\n\nexport default defineConfig({\n  schema: path.join('prisma', 'schema'),\n  migrations: { path: path.join('prisma', 'migrations') },\n});\n```\n\nReference: Prisma blog – Organize Your Prisma Schema into Multiple Files: https://www.prisma.io/blog/organize-your-prisma-schema-with-multi-file-support\n\n---\n\n# LSSM Auth (Sigil) – Models & Integration\n\nThis document tracks the identity models and integration points used by the LSSM Sigil module.\n\n## Models (Prisma `lssm_sigil`)\n\n- `User` – core identity with email, optional phone, role, passkeys, apiKeys\n- `Session` – session tokens and metadata; includes `activeOrganizationId`\n- `Account` – external providers (password, OAuth)\n- `Organization` – tenant boundary; includes `type` additional field\n- `Member`, `Invitation`, `Team`, `TeamMember` – org/teams\n- `Role`, `Permission`, `PolicyBinding` – RBAC\n- `ApiKey`, `Passkey` – programmable access and WebAuthn\n- `SsoProvider` – OIDC/SAML provider configuration (org- or user-scoped)\n- `OAuthApplication`, `OAuthAccessToken`, `OAuthConsent` – first/third-party OAuth\n\nThese mirror STRIT additions so Better Auth advanced plugins (admin, organization, apiKey, passkey, genericOAuth) work uniformly across apps.\n\n## Better Auth (server)\n\nEnabled methods:\n\n- Email & password\n- Phone OTP (Telnyx)\n- Passkey (WebAuthn)\n- API keys\n- Organizations & Teams\n- Generic OAuth (FranceConnect+ via OIDC with JWE/JWS using JOSE)\n\nServer config lives at `packages/lssm/modules/sigil/src/application/services/auth.ts`.\n\n## Clients (Expo / React)\n\nClient config lives at `packages/lssm/modules/sigil/src/presentation/providers/auth/expo.ts` with plugins for admin, passkey, apiKey, organization, phone, genericOAuth.\n\n## Environment Variables\n\nTelnyx (phone OTP):\n\n- `TELNYX_API_KEY`\n- `TELNYX_MESSAGING_PROFILE_ID`\n- `TELNYX_FROM_NUMBER`\n\nFranceConnect+ (prefer LSSM*… but STRIT*… fallbacks are supported):\n\n- `LSSM_FRANCECONNECTPLUS_DISCOVERY_URL`\n- `LSSM_FRANCECONNECTPLUS_CLIENT_ID`\n- `LSSM_FRANCECONNECTPLUS_CLIENT_SECRET`\n- `LSSM_FRANCECONNECTPLUS_ENC_PRIVATE_KEY_PEM` (PKCS8; RSA-OAEP-256)\n\nGeneric:\n\n- `API_URL_IDENTITIES` – base URL for Better Auth server\n- `BETTER_AUTH_SECRET` – server secret\n\nKeep this in sync with code changes to avoid drift.\n\n## HCircle domain splits and auth removal\n\n- Auth/identity models are not defined locally anymore. They come from `@lssm/app.cli-database-sigil` under the `lssm_sigil` schema.\n- `packages/hcircle/libs/database-coliving/prisma/schema/domain/` is split by domain; newsletter/waiting list lives in `newsletter.prisma` and uses `@@map(\"waiting_list\")`.\n- To avoid collisions with module names, the local event models were renamed to `SocialEvent`, `SocialEventAttendee`, and `SocialEventRecurrence` with `@@map` pointing to existing table names.\n\n---\n\n## Vertical profiles (current)\n\n### STRIT\n\n- prisma-merger modules:\n  - `@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`\n- main.prisma schemas:\n  - `schemas = [\"public\",\"lssm_sigil\",\"lssm_content\",\"lssm_ops\",\"lssm_planning\",\"lssm_quill\",\"lssm_geoterro\"]`\n- domain splits (`packages/strit/libs/database/prisma/schema/domain/`):\n  - `bookings.prisma` (Booking, StritDocument + links to Content `File` and Sigil `Organization`)\n  - `commerce.prisma` (Wholesale models; `sellerId` linked to Sigil `Organization`)\n  - `files.prisma` (PublicFile, PublicFileAccessLog; `ownerId`→Organization, `uploadedBy`→User)\n  - `geo.prisma` (PublicCountry, PublicAddress, City; links to Spots/Series)\n  - `spots.prisma`, `urbanism.prisma`, `analytics.prisma`, `onboarding.prisma`, `referrals.prisma`, `subscriptions.prisma`, `content.prisma`\n- auth models are imported from Sigil (no local auth tables).\n- Back-relations for `Organization` (e.g., `files`, seller relations) are declared in the Sigil module to avoid scattering.\n\n### ARTISANOS\n\n- prisma-merger modules:\n  - `@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`\n- main.prisma schemas:\n  - `schemas = [\"public\",\"lssm_sigil\",\"lssm_content\",\"lssm_featureflags\",\"lssm_ops\",\"lssm_planning\",\"lssm_quill\",\"lssm_geoterro\"]`\n- domain splits (`packages/artisanos/libs/database-artisan/prisma/schema/domain/`):\n  - `sales.prisma` (Client, Quote, QuoteTemplate, Invoice, FollowUps)\n  - `subsidies.prisma` (SubsidyProgram, AidApplication, SupportingDocument)\n  - `projects.prisma` (Project, ProjectPlanningSettings)\n  - `crm.prisma` (OrganizationProfessionalProfile, OrganizationCertification)\n  - `professions.prisma`, `products.prisma`, `templates.prisma`, `analytics.prisma`, `onboarding.prisma`, `referrals.prisma`, `subscriptions.prisma`, `files.prisma`\n- auth/organization/team models are provided by Sigil; local legacy copies were removed.\n- Where names collide with Content, local models are prefixed (e.g., `PublicFile`) and use `@@map` to keep existing table names where applicable.\n\n## Schema Dictionary: `@lssm/lib.schema`\n\n### Purpose\n\nDescribe operation I/O once and generate:\n\n- zod (runtime validation)\n- GraphQL (Pothos types/refs)\n- JSON Schema (via `zod-to-json-schema` or native descriptors)\n\n### Primitives\n\n- **FieldType<T>**: describes a scalar or composite field and carries:\n  - `zod` schema for validation\n  - optional JSON Schema descriptor\n  - optional GraphQL scalar reference/name\n- **SchemaModel**: named object model composed of fields. Exposes helpers:\n  - `getZod(): z.ZodObject<ZodShapeFromFields<Fields>> | z.ZodArray<z.ZodObject<...>>`\n    - Preserves each field's schema, optionality, and array-ness\n    - Top-level lists are supported via `config.isArray: true`\n  - `getJsonSchema(): JSONSchema7` (export for docs, MCP, forms)\n  - `getPothosInput()` (GraphQL input object name)\n\n### Conventions\n\n- Name models with PascalCase; suffix with `Input`/`Result` when ambiguous.\n- Use explicit enums for multi-value constants; reuse the same enum across input/output.\n- Define domain enums via `defineEnum('Name', [...])` in the relevant domain package (e.g., `packages/strit/libs/contracts-strit/src/enums/`), not in `ScalarTypeEnum`.\n- Reference those enums in `SchemaModel` fields directly (they expose `getZod`, `getPothos`, `getJsonSchema`).\n\n#### Example (STRIT)\n\n```ts\n// packages/strit/libs/contracts-strit/src/enums/recurrence.ts\nimport { defineEnum } from '@lssm/lib.schema';\nexport const SpotEnum = {\n  Weekday: () =>\n    defineEnum('Weekday', ['MO', 'TU', 'WE', 'TH', 'FR', 'SA', 'SU'] as const),\n  RecurrenceFrequency: () =>\n    defineEnum('RecurrenceFrequency', [\n      'DAILY',\n      'WEEKLY',\n      'MONTHLY',\n      'YEARLY',\n    ] as const),\n} as const;\n```\n\n```ts\n// usage in contracts\nfrequency: { type: SpotEnum.RecurrenceFrequency(), isOptional: false },\nbyWeekday: { type: SpotEnum.Weekday(), isOptional: true, isArray: true },\n```\n\n- Use `Date` type for temporal values and ensure ISO strings in JSON transports where needed.\n\n### Mapping rules (summary)\n\n- Strings → GraphQL `String`\n- Numbers → `Int` if safe 32-bit integer else `Float`\n- Booleans → `Boolean`\n- Dates → custom `Date` scalar\n- Arrays<T> → list of mapped T (set `isArray: true` on the field)\n- Top-level arrays → set `isArray: true` on the model config\n- Objects → input/output object types with stable field order\n- Unions → supported for output; input unions map to JSON (structural input is not supported by GraphQL)\n\n### JSON Schema export\n\nPrefer `getZod()` + `zod-to-json-schema` for consistency. For advanced cases, provide a custom `getJsonSchema()` on the model.\n\n### Example\n\n```ts\nimport { ScalarTypeEnum, SchemaModel } from '@lssm/lib.schema';\n\n// Nested model\nconst Weekday = new SchemaModel({\n  name: 'Weekday',\n  fields: {\n    value: { type: ScalarTypeEnum.String_unsecure(), isOptional: false },\n  },\n});\n\n// Parent model with array field and nested object\nconst Rule = new SchemaModel({\n  name: 'Rule',\n  fields: {\n    timezone: { type: ScalarTypeEnum.TimeZone(), isOptional: false },\n    byWeekday: { type: Weekday, isOptional: true, isArray: true },\n  },\n});\n\nconst CreateThingInput = new SchemaModel({\n  name: 'CreateThingInput',\n  fields: {\n    name: { type: ScalarTypeEnum.NonEmptyString(), isOptional: false },\n    rule: { type: Rule, isOptional: false },\n  },\n});\n\n// zod\nconst z = CreateThingInput.getZod();\n```\n"
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/learning-events.docblock.js

@@ -1,47 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/learning-events.docblock.js
-registerDocBlocks([{
-	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
-
-Studio emits lightweight **learning/activity events** to support onboarding, ambient coaching, and learning journeys.
-
-## Persistence model
-
-- **Studio**: events are persisted to the database in \`StudioLearningEvent\` and are organization-scoped (optionally project-scoped).
-- **Sandbox**: events remain **local-only** (unlogged); they must never be sent to backend services.
-
-## GraphQL API
-
-- \`recordLearningEvent(input: { name, projectId?, payload? })\`
-- \`myLearningEvents(projectId?, limit?)\`
-- \`myOnboardingTracks(productId?, includeProgress?)\`
-- \`myOnboardingProgress(trackKey)\`
-- \`dismissOnboardingTrack(trackKey)\`
-
-## Common event names (convention)
-
-- \`module.navigated\` — user navigated to a Studio module (payload at minimum: \`{ moduleId }\`).
-- \`studio.template.instantiated\` — created a new Studio project (starter template). Payload commonly includes \`{ templateId, projectSlug }\`.
-- \`spec.changed\` — created or updated a Studio spec. Payload may include \`{ action: 'create' | 'update', specId?, specType? }\`.
-- \`regeneration.completed\` — finished a “regen/deploy” action (currently emitted on successful Studio deploy actions).
-- \`studio.evolution.applied\` — completed an Evolution session (payload commonly includes \`{ evolutionSessionId }\`).
-
-These events are intentionally minimal and must avoid PII/secrets in payloads.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/platform-admin-panel.docblock.js

@@ -1,83 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/platform-admin-panel.docblock.js
-registerDocBlocks([{
-	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/*\`
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/project-access-teams.docblock.js

@@ -1,44 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/project-access-teams.docblock.js
-registerDocBlocks([{
-	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:\n  - \`myStudioProjects\` (returns only projects you can access)\n  - \`studioProjectBySlug(slug)\` (enforces the same access rules)\n  - \`myTeams\`\n  - \`projectTeams(projectId)\`\n\n- Write:\n  - \`createStudioProject(input.teamIds?)\` (teamIds optional)\n  - \`setProjectTeams(projectId, teamIds)\` (admin-only)\n
-## Related\n+\n+- Team administration + invitations: see \`/docs/tech/studio/team-invitations\`.\n+
-## Notes
-
-Payloads and events must avoid secrets/PII. For Sandbox, the model remains local-first and unlogged.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/project-routing.docblock.js

@@ -1,66 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/project-routing.docblock.js
-registerDocBlocks([{
-	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
-
-ContractSpec Studio uses a **project-first URL scheme**:
-
-- \`/studio/projects\` — create, select, and delete projects.
-- \`/studio/{projectSlug}/*\` — project modules (canvas/specs/deploy/integrations/evolution/learning).
-- \`/studio/learning\` — learning hub that does not require selecting a project.
-
-## Studio layout shell
-
-Studio routes are wrapped in a dedicated **Studio app shell** (header + footer) that provides in-app navigation (Projects/Learning/Teams), organization switching, and account actions.
-
-Project 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.
-
-## Slug behavior (rename-safe)
-
-- Each project has a \`slug\` stored in the database (\`StudioProject.slug\`).
-- When a project name changes, Studio **updates the slug** and stores the previous slug as an alias (\`StudioProjectSlugAlias\`).
-- Requests to an alias slug are **redirected to the canonical slug**.
-
-GraphQL entrypoint:
-
-- \`studioProjectBySlug(slug: String!)\` returns:
-  - \`project\`
-  - \`canonicalSlug\`
-  - \`wasRedirect\`
-
-## Deletion behavior (soft delete)
-
-Projects are **soft-deleted**:
-
-- \`deleteStudioProject(id: String!)\` sets \`StudioProject.deletedAt\`.
-- All listings and access checks filter \`deletedAt = null\`.
-- Soft-deleted projects are treated as “not found” in Studio routes and GraphQL access checks.
-
-## Available modules for a selected project
-
-The following project modules are expected under \`/studio/{projectSlug}\`:
-
-- \`/canvas\` — Visual builder canvas (stored via overlays and canvas versions).
-- \`/specs\` — Spec editor (stored as \`StudioSpec\`).
-- \`/deploy\` — Deployments history + triggers (stored as \`StudioDeployment\`).
-- \`/integrations\` — Integrations scoped to project (stored as \`StudioIntegration\`).
-- \`/evolution\` — Evolution sessions (stored as \`EvolutionSession\`).
-- \`/learning\` — Project learning activity.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/sandbox-unlogged.docblock.js

@@ -1,39 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/sandbox-unlogged.docblock.js
-registerDocBlocks([{
-	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)
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/team-invitations.docblock.js

@@ -1,68 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/team-invitations.docblock.js
-registerDocBlocks([{
-	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.\n
-- 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)\n
-- \`status\`: \`pending | accepted | declined | expired\`\n
-- \`teamId?\`: optional team to join\n
-- \`inviterId\`: user who issued the invitation
-
-## GraphQL surfaces
-
-- Team CRUD (admin-only):\n
-  - \`createTeam(name)\`\n
-  - \`renameTeam(teamId, name)\`\n
-  - \`deleteTeam(teamId)\`\n
-
-- Invitations (admin-only):\n
-  - \`organizationInvitations\`\n
-  - \`inviteToOrganization(email, role?, teamId?)\` → returns \`inviteUrl\` and whether an email was sent
-
-## Accepting an invitation
-
-The invite link is served as:\n
-- \`/invite/{invitationId}\`
-
-Acceptance rules:
-- The user must be authenticated.\n
-- The authenticated user’s email must match \`Invitation.email\`.\n
-- If not already a member, create \`Member(userId, organizationId, role)\`.\n
-- If \`teamId\` is present, ensure \`TeamMember(teamId, userId)\`.\n
-- Mark invitation \`status='accepted'\` and set \`acceptedAt\`.\n
-- 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.\n
-- Otherwise, the UI uses the returned \`inviteUrl\` for manual copy/share.
-`
-}]);
-
-//#endregion

package/dist/examples/learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/workspace-ops.docblock.js

@@ -1,46 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../learning-journey-ui-gamified/dist/libs/contracts/dist/docs/tech/studio/workspace-ops.docblock.js
-registerDocBlocks([{
-	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)
-
-Base: \`/api/workspace-ops\`
-
-These endpoints are **read-only** in v1 and never push to git:
-
-- \`GET /api/workspace-ops/:integrationId/config?organizationId=\`
-- \`GET /api/workspace-ops/:integrationId/specs?organizationId=\`
-- \`POST /api/workspace-ops/:integrationId/validate\` (body: organizationId, files?, pattern?)
-- \`POST /api/workspace-ops/:integrationId/deps\` (body: organizationId, pattern?)
-- \`POST /api/workspace-ops/:integrationId/diff\` (body: organizationId, specPath, baseline?, breakingOnly?)
-
-## Repo resolution
-
-- The repo root is resolved from the Studio Integration (\`IntegrationProvider.GITHUB\`) config:
-  - \`config.repoCachePath\` (preferred) or \`config.localPath\`
-- Resolution is constrained to \`CONTRACTSPEC_REPO_CACHE_DIR\` (default: \`/tmp/contractspec-repos\`)
-
-## Intended UX
-
-- Studio Assistant can run these checks and present results as suggestions.
-- Users can copy equivalent CLI commands for local runs:
-  - \`contractspec validate\`
-  - \`contractspec deps\`
-  - \`contractspec diff --baseline <ref>\`
-`
-}]);
-
-//#endregion