@lssm/lib.contracts 0.0.0-canary-20251217083314 → 0.0.0-canary-20251219202229

package/dist/docs/tech/contracts/ops-to-presentation-linking.docblock.js

@@ -18,4 +18,5 @@ const tech_contracts_ops_to_presentation_linking_DocBlocks = [{
 registerDocBlocks(tech_contracts_ops_to_presentation_linking_DocBlocks);
 
 //#endregion
-export { tech_contracts_ops_to_presentation_linking_DocBlocks };
+export { tech_contracts_ops_to_presentation_linking_DocBlocks };
+//# sourceMappingURL=ops-to-presentation-linking.docblock.js.map

package/dist/docs/tech/contracts/ops-to-presentation-linking.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"ops-to-presentation-linking.docblock.js","names":["tech_contracts_ops_to_presentation_linking_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/contracts/ops-to-presentation-linking.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_contracts_ops_to_presentation_linking_DocBlocks: DocBlock[] =\n  [\n    {\n      id: 'docs.tech.contracts.ops-to-presentation-linking',\n      title: 'Ops \\u2194 Presentation linking (V2)',\n      summary:\n        'This document explains how operations (ContractSpec) are linked to Presentations (PresentationDescriptorV2) via Feature modules.',\n      kind: 'reference',\n      visibility: 'public',\n      route: '/docs/tech/contracts/ops-to-presentation-linking',\n      tags: ['tech', 'contracts', 'ops-to-presentation-linking'],\n      body: \"### Ops \\u2194 Presentation linking (V2)\\n\\nThis document explains how operations (ContractSpec) are linked to Presentations (PresentationDescriptorV2) via Feature modules.\\n\\n- Location: `@lssm/lib.contracts/src/features.ts`\\n- Field: `FeatureModuleSpec.opToPresentation?: { op: { name; version }; pres: { name; version } }[]`\\n- Validation: `installFeature()` validates that linked ops exist in `SpecRegistry` and linked presentations exist in the registry, and that declared targets are present.\\n\\nExample:\\n\\n```ts\\nimport type { SpecRegistry } from '@lssm/lib.contracts/src/registry';\\nimport { FeatureRegistry, createFeatureModule } from '@lssm/lib.contracts';\\n\\nexport function buildFeaturesWithOps(ops: SpecRegistry) {\\n  const features = new FeatureRegistry();\\n  features.register(\\n    createFeatureModule(\\n      {\\n        key: 'myapp.widgets.linkage',\\n        title: 'Widgets (linked)',\\n        description: 'Links create/update ops to UI presentations',\\n        domain: 'widgets',\\n        tags: ['widgets', 'linkage'],\\n        stability: 'beta',\\n      },\\n      {\\n        operations: [\\n          { name: 'widgets.create', version: 1 },\\n          { name: 'widgets.update', version: 1 },\\n        ],\\n        presentations: [{ name: 'myapp.widgets.editor.page', version: 1 }],\\n        opToPresentation: [\\n          {\\n            op: { name: 'widgets.create', version: 1 },\\n            pres: { name: 'myapp.widgets.editor.page', version: 1 },\\n          },\\n          {\\n            op: { name: 'widgets.update', version: 1 },\\n            pres: { name: 'myapp.widgets.editor.page', version: 1 },\\n          },\\n        ],\\n        presentationsTargets: [\\n          {\\n            name: 'myapp.widgets.editor.page',\\n            version: 1,\\n            targets: ['react', 'markdown'],\\n          },\\n        ],\\n      }\\n    )\\n  );\\n  return { features };\\n}\\n```\\n\\nNotes\\n\\n- This enables traceability: the UI flow that realizes an op is discoverable via the feature catalog.\\n- Presentations can target multiple outputs (`react`, `markdown`, `application/json`, `application/xml`).\\n- Use `renderFeaturePresentation()` to render a descriptor to a given target with a component map.\\n\",\n    },\n  ];\nregisterDocBlocks(tech_contracts_ops_to_presentation_linking_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,uDACX,CACE;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAa;EAA8B;CAC1D,MAAM;CACP,CACF;AACH,kBAAkB,qDAAqD"}

package/dist/docs/tech/contracts/overlays.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/contracts/overlays.docblock.d.ts
 declare const tech_contracts_overlays_DocBlocks: DocBlock[];
 //#endregion
-export { tech_contracts_overlays_DocBlocks };
+export { tech_contracts_overlays_DocBlocks };
+//# sourceMappingURL=overlays.docblock.d.ts.map

package/dist/docs/tech/contracts/overlays.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"overlays.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/contracts/overlays.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,mCAAmC"}

package/dist/docs/tech/contracts/overlays.docblock.js

@@ -18,4 +18,5 @@ const tech_contracts_overlays_DocBlocks = [{
 registerDocBlocks(tech_contracts_overlays_DocBlocks);
 
 //#endregion
-export { tech_contracts_overlays_DocBlocks };
+export { tech_contracts_overlays_DocBlocks };
+//# sourceMappingURL=overlays.docblock.js.map

package/dist/docs/tech/contracts/overlays.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"overlays.docblock.js","names":["tech_contracts_overlays_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/contracts/overlays.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_contracts_overlays_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.contracts.overlays',\n    title: 'OverlaySpec Implementation',\n    summary:\n      'OverlaySpecs allow tenants/users to adapt presentation without duplicating code. Implementation lives in `@lssm/lib.overlay-engine`.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/contracts/overlays',\n    tags: ['tech', 'contracts', 'overlays'],\n    body: \"# OverlaySpec Implementation\\n\\nOverlaySpecs allow tenants/users to adapt presentation without duplicating code. Implementation lives in `@lssm/lib.overlay-engine`.\\n\\n## Structure\\n\\n```ts\\ninterface OverlaySpec {\\n  overlayId: string;\\n  version: string;\\n  appliesTo: {\\n    capability?: string;\\n    workflow?: string;\\n    dataView?: string;\\n    presentation?: string;\\n    tenantId?: string;\\n    userId?: string;\\n    role?: string;\\n    device?: string;\\n  };\\n  modifications: OverlayModification[];\\n}\\n```\\n\\nSupported modifications:\\n\\n- `hideField`\\n- `renameLabel`\\n- `reorderFields`\\n- `setDefault`\\n- `addHelpText`\\n- `makeRequired`\\n\\n## Signing\\n\\nOverlays must be signed. Use the signer helper:\\n\\n```ts\\nimport { signOverlay } from '@lssm/lib.overlay-engine/signer';\\n\\nconst signed = await signOverlay(overlay, privateKeyPem);\\nregistry.register(signed);\\n```\\n\\nKeys are stored in `OverlaySigningKey` (Prisma) and referenced by the `Overlay` model for auditing.\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\\n\",\n  },\n];\nregisterDocBlocks(tech_contracts_overlays_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,oCAAgD,CAC3D;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAa;EAAW;CACvC,MAAM;CACP,CACF;AACD,kBAAkB,kCAAkC"}

package/dist/docs/tech/contracts/tests.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/contracts/tests.docblock.d.ts
 declare const tech_contracts_tests_DocBlocks: DocBlock[];
 //#endregion
-export { tech_contracts_tests_DocBlocks };
+export { tech_contracts_tests_DocBlocks };
+//# sourceMappingURL=tests.docblock.d.ts.map

package/dist/docs/tech/contracts/tests.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"tests.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/contracts/tests.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,gCAAgC"}

package/dist/docs/tech/contracts/tests.docblock.js

@@ -18,4 +18,5 @@ const tech_contracts_tests_DocBlocks = [{
 registerDocBlocks(tech_contracts_tests_DocBlocks);
 
 //#endregion
-export { tech_contracts_tests_DocBlocks };
+export { tech_contracts_tests_DocBlocks };
+//# sourceMappingURL=tests.docblock.js.map

package/dist/docs/tech/contracts/tests.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tests.docblock.js","names":["tech_contracts_tests_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/contracts/tests.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_contracts_tests_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.contracts.tests',\n    title: 'TestSpec & TestRunner',\n    summary:\n      'Use `TestSpec` to describe end-to-end scenarios for contracts and workflows. Specs live alongside your contracts and exercise the same SpecRegistry handlers the app uses.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/contracts/tests',\n    tags: ['tech', 'contracts', 'tests'],\n    body: \"## TestSpec & TestRunner\\n\\nUse `TestSpec` to describe end-to-end scenarios for contracts and workflows. Specs live alongside your contracts and exercise the same SpecRegistry handlers the app uses.\\n\\n- Types & registry: `packages/libs/contracts/src/tests/spec.ts`\\n- Runtime runner: `packages/libs/contracts/src/tests/runner.ts`\\n- CLI: `contractspec test`\\n\\n### Structure\\n\\n```ts\\nexport interface TestSpec {\\n  meta: TestSpecMeta;\\n  target: TestTarget;  // contract or workflow\\n  fixtures?: Fixture[]; // optional shared setup before each scenario\\n  scenarios: TestScenario[];\\n  coverage?: CoverageRequirement;\\n}\\n```\\n\\n- `Fixture`: run an operation before the scenario (`operation`, optional `input`)\\n- `Action`: operation input that the scenario exercises\\n- `Assertion`:\\n  - `expectOutput` `{ match }` deep-equals the handler output\\n  - `expectError` `{ messageIncludes? }` ensures an error was thrown\\n  - `expectEvents` `{ events: [{ name, version, min?, max? }] }` checks emitted events\\n\\n### Example\\n\\n```ts\\nimport { defineCommand, type TestSpec } from '@lssm/lib.contracts';\\n\\nexport const AddNumbersSpec = defineCommand({\\n  meta: { name: 'math.add', version: 1, /* \\u2026 */ },\\n  io: {\\n    input: AddNumbersInput,\\n    output: AddNumbersOutput,\\n  },\\n  policy: { auth: 'user' },\\n});\\n\\nexport const MathAddTests: TestSpec = {\\n  meta: {\\n    name: 'math.add.tests',\\n    version: 1,\\n    title: 'Math add scenarios',\\n    owners: ['@team.math'],\\n    tags: ['math'],\\n    stability: StabilityEnum.Experimental,\\n  },\\n  target: { type: 'contract', operation: { name: 'math.add' } },\\n  scenarios: [\\n    {\\n      name: 'adds positive numbers',\\n      when: {\\n        operation: { name: 'math.add' },\\n        input: { a: 2, b: 3 },\\n      },\\n      then: [\\n        { type: 'expectOutput', match: { sum: 5 } },\\n        {\\n          type: 'expectEvents',\\n          events: [{ name: 'math.sum_calculated', version: 1, min: 1 }],\\n        },\\n      ],\\n    },\\n  ],\\n};\\n```\\n\\n### Running tests\\n\\n1. Register the contract handlers in a `SpecRegistry`:\\n\\n```ts\\nexport function createRegistry() {\\n  const registry = new SpecRegistry();\\n  registry.register(AddNumbersSpec);\\n  registry.bind(AddNumbersSpec, addNumbersHandler);\\n  return registry;\\n}\\n```\\n\\n2. Run the CLI:\\n\\n```\\ncontractspec test apps/math/tests/math.add.tests.ts \\\\\\n  --registry apps/math/tests/registry.ts\\n```\\n\\n- The CLI loads the TestSpec, instantiates the registry (via the provided module), and executes each scenario via `TestRunner`.\\n- `--json` outputs machine-readable results.\\n\\n### Programmatic usage\\n\\n```ts\\nconst runner = new TestRunner({\\n  registry,\\n  createContext: () => ({ actor: 'user', organizationId: 'tenant-1' }),\\n});\\n\\nconst result = await runner.run(MathAddTests);\\nconsole.log(result.passed, result.failed);\\n```\\n\\n- `createContext` can supply default `HandlerCtx` values.\\n- `beforeEach` / `afterEach` hooks let you seed databases or reset state.\\n\\n### Best practices\\n\\n- Keep fixtures idempotent so scenarios can run in parallel in the future.\\n- Use `expectEvents` to guard analytics/telemetry expectations.\\n- Add specs to `TestRegistry` for discovery and documentation.\\n- `coverage` captures desired coverage metrics (enforced by future tooling).\\n- Pair TestSpec files with CI using `contractspec test --json` and fail builds when `failed > 0`.\\n\\n### Mocking with Bun's `vi`\\n\\n- Pass a single function type to `vi.fn<TFunction>()` so calls retain typed arguments:\\n\\n```ts\\nconst handler = vi.fn<typeof fetch>();\\nconst fetchImpl: typeof fetch = ((...args) => handler(...args)) as typeof fetch;\\nObject.defineProperty(fetchImpl, 'preconnect', {\\n  value: vi.fn<typeof fetch.preconnect>(),\\n});\\n```\\n\\n- When you need to inspect calls, use the typed mock (`handler.mock.calls`) rather than casting to `any`.\\n- Narrow optional request data defensively (e.g., check for headers before reading them) so tests remain type-safe under strict `tsconfig` settings.\\n\\n\",\n  },\n];\nregisterDocBlocks(tech_contracts_tests_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,iCAA6C,CACxD;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAa;EAAQ;CACpC,MAAM;CACP,CACF;AACD,kBAAkB,+BAA+B"}

package/dist/docs/tech/contracts/themes.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/contracts/themes.docblock.d.ts
 declare const tech_contracts_themes_DocBlocks: DocBlock[];
 //#endregion
-export { tech_contracts_themes_DocBlocks };
+export { tech_contracts_themes_DocBlocks };
+//# sourceMappingURL=themes.docblock.d.ts.map

package/dist/docs/tech/contracts/themes.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"themes.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/contracts/themes.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,iCAAiC"}

package/dist/docs/tech/contracts/themes.docblock.js

@@ -18,4 +18,5 @@ const tech_contracts_themes_DocBlocks = [{
 registerDocBlocks(tech_contracts_themes_DocBlocks);
 
 //#endregion
-export { tech_contracts_themes_DocBlocks };
+export { tech_contracts_themes_DocBlocks };
+//# sourceMappingURL=themes.docblock.js.map

package/dist/docs/tech/contracts/themes.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"themes.docblock.js","names":["tech_contracts_themes_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/contracts/themes.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_contracts_themes_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.contracts.themes',\n    title: 'ThemeSpec Overview',\n    summary:\n      '`ThemeSpec` defines a structured, versioned source of truth for design tokens, component variants, and scoped overrides. Use it to describe how tenants or individual users should experience the design system without hand-maintaining ad-hoc theme files. Specs live in `@lssm/lib.contracts`, making them accessible to generators, docs, and runtime tooling.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/contracts/themes',\n    tags: ['tech', 'contracts', 'themes'],\n    body: \"# ThemeSpec Overview\\n\\n## Purpose\\n\\n`ThemeSpec` defines a structured, versioned source of truth for design tokens, component variants, and scoped overrides. Use it to describe how tenants or individual users should experience the design system without hand-maintaining ad-hoc theme files. Specs live in `@lssm/lib.contracts`, making them accessible to generators, docs, and runtime tooling.\\n\\n## Location\\n\\n- Types & registry: `packages/libs/contracts/src/themes.ts`\\n- Design tokens bridge: `packages/libs/design-system/src/theme/*`\\n\\n## Schema\\n\\n```ts\\nexport interface ThemeSpec {\\n  meta: ThemeMeta;            // ownership metadata + { name, version, extends?, scopes? }\\n  tokens: ThemeTokens;        // design tokens grouped by colors, radii, space, etc.\\n  components?: ComponentVariantSpec[]; // per-component variant configuration\\n  overrides?: ThemeOverride[];         // scoped tenant/user overrides\\n}\\n```\\n\\n- **ThemeMeta**\\n  - `name`: fully-qualified identifier (e.g., `design.pastel`)\\n  - `version`: increment when tokens/variants change in a breaking way\\n  - `extends?`: optional `{ name, version }` pointer to a base theme\\n  - `scopes?`: default scopes where the theme applies (`global`, `tenant`, `user`)\\n- **ThemeTokens**\\n  - `colors`, `radii`, `space`, `typography`, `shadows`, `motion`\\n  - Each entry is a map of `{ value: T; description?: string }`\\n- **ComponentVariantSpec**\\n  - `component`: design-system component key (e.g., `Button`, `NavMain`)\\n  - `variants`: map of variant names \\u2192 `{ props?, tokens? }`\\n- **ThemeOverride**\\n  - `scope`: `'global' | 'tenant' | 'user'`\\n  - `target`: identifier (e.g., `tenant:artisanos`, `user:123`)\\n  - `tokens?` / `components?`: partial token/variant overrides for the target\\n\\n## Registry Usage\\n\\n```ts\\nimport { ThemeRegistry } from '@lssm/lib.contracts/themes';\\nimport { PastelTheme } from './themes/design.pastel';\\n\\nconst themes = new ThemeRegistry();\\nthemes.register(PastelTheme);\\n\\nconst theme = themes.get('design.pastel');\\nconst tenantVariant = themes\\n  .get('design.pastel')\\n  ?.overrides?.find((o) => o.target === 'tenant:artisanos');\\n```\\n\\nThe registry guarantees `name + version` uniqueness and exposes `list()` for discovery tooling.\\n\\n## Rendering\\n\\nThe design system consumes specs (via adapters you provide) to build runtime tokens. A simple adapter might:\\n\\n1. Resolve the base theme + applicable overrides.\\n2. Merge token maps using `ThemeTokens`.\\n3. Feed the result into `mapTokensForPlatform` in `@lssm/lib.design-system`.\\n\\n```ts\\nimport { ThemeRegistry } from '@lssm/lib.contracts/themes';\\nimport { mapTokensForPlatform } from '@lssm/lib.design-system';\\n\\nfunction resolveTokens(registry: ThemeRegistry, ref: ThemeRef, ctx: { tenant?: string; user?: string }) {\\n  const spec = registry.get(ref.name, ref.version);\\n  if (!spec) throw new Error('Theme not found');\\n\\n  const tokens = deepMerge(spec.tokens, collectOverrides(spec.overrides, ctx));\\n  return mapTokensForPlatform(tokens);\\n}\\n```\\n\\n## Authoring Guidelines\\n\\n1. Keep token names aligned with the design-system defaults (`background`, `mutedForeground`, etc.).\\n2. Use `extends` to create layered themes (base brand \\u2192 tenant tweaks \\u2192 user-level overrides).\\n3. Document variants with `description` to help designers and automation understand intent.\\n4. Prefer scoped overrides (`tenant:foo`) instead of duplicating the entire theme per tenant.\\n5. When tokens influence multiple components, capture them in `tokens` and keep `components` for API-level variant wiring.\\n\\n## CLI (Future Work)\\n\\nThe `contractspec` CLI does not yet scaffold theme specs. Planned additions:\\n\\n- `contractspec create --type theme`\\n- `contractspec build <theme.theme.ts>` \\u2192 generate design-system adapters\\n\\nFor now, author specs manually and register them alongside contract bundles.\\n\\n\",\n  },\n];\nregisterDocBlocks(tech_contracts_themes_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,kCAA8C,CACzD;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAa;EAAS;CACrC,MAAM;CACP,CACF;AACD,kBAAkB,gCAAgC"}

package/dist/docs/tech/contracts/vertical-pocket-family-office.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/contracts/vertical-pocket-family-office.docblock.d.ts
 declare const tech_contracts_vertical_pocket_family_office_DocBlocks: DocBlock[];
 //#endregion
-export { tech_contracts_vertical_pocket_family_office_DocBlocks };
+export { tech_contracts_vertical_pocket_family_office_DocBlocks };
+//# sourceMappingURL=vertical-pocket-family-office.docblock.d.ts.map

package/dist/docs/tech/contracts/vertical-pocket-family-office.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"vertical-pocket-family-office.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/contracts/vertical-pocket-family-office.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,wDAAwD"}

package/dist/docs/tech/contracts/vertical-pocket-family-office.docblock.js

@@ -18,4 +18,5 @@ const tech_contracts_vertical_pocket_family_office_DocBlocks = [{
 registerDocBlocks(tech_contracts_vertical_pocket_family_office_DocBlocks);
 
 //#endregion
-export { tech_contracts_vertical_pocket_family_office_DocBlocks };
+export { tech_contracts_vertical_pocket_family_office_DocBlocks };
+//# sourceMappingURL=vertical-pocket-family-office.docblock.js.map

package/dist/docs/tech/contracts/vertical-pocket-family-office.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"vertical-pocket-family-office.docblock.js","names":["tech_contracts_vertical_pocket_family_office_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/contracts/vertical-pocket-family-office.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_contracts_vertical_pocket_family_office_DocBlocks: DocBlock[] =\n  [\n    {\n      id: 'docs.tech.contracts.vertical-pocket-family-office',\n      title: 'Pocket Family Office Vertical',\n      summary: 'Pocket Family Office is a ContractSpec reference vertical that',\n      kind: 'reference',\n      visibility: 'public',\n      route: '/docs/tech/contracts/vertical-pocket-family-office',\n      tags: ['tech', 'contracts', 'vertical-pocket-family-office'],\n      body: '# Pocket Family Office Vertical\\n\\nPocket Family Office is a ContractSpec reference vertical that\\ndemonstrates finance automation atop the integration and knowledge\\nlayers. It is optimised for the hackathon stack (Google Cloud, Mistral,\\nQdrant, ElevenLabs) while remaining provider-agnostic.\\n\\n## Goals\\n\\n- Ingest household financial documents (uploads + Gmail threads).\\n- Generate AI summaries and optionally deliver them as voice notes.\\n- Schedule multi-channel reminders for upcoming bills.\\n- Showcase spec-first composition of integrations, knowledge spaces, and\\n  workflows.\\n\\n## Blueprint Overview\\n\\nSource: `packages/verticals/pocket-family-office/blueprint.ts`\\n\\n- **Integration slots**\\n  - `primaryLLM` \\u2192 Mistral chat/embeddings\\n  - `primaryVectorDb` \\u2192 Qdrant\\n  - `primaryStorage` \\u2192 Google Cloud Storage\\n  - `primaryOpenBanking` \\u2192 Powens BYOK project for account aggregation\\n  - `emailInbound` / `emailOutbound` \\u2192 Gmail + Postmark\\n  - `calendarScheduling` \\u2192 Google Calendar\\n  - `voicePlayback` \\u2192 ElevenLabs (optional)\\n  - `smsNotifications` \\u2192 Twilio (optional)\\n  - `paymentsProcessing` \\u2192 Stripe (optional)\\n- **Workflows**\\n  - `process-uploaded-document`\\n  - `upcoming-payments-reminder`\\n  - `generate-financial-summary`\\n  - `ingest-email-threads`\\n  - `sync-openbanking-accounts`\\n  - `sync-openbanking-transactions`\\n  - `refresh-openbanking-balances`\\n  - `generate-openbanking-overview`\\n- **Policies/Telemetry** \\u2013 references tenant policy specs and\\n  `pfo.telemetry` for observability.\\n\\n## Tenant Sample\\n\\n`tenant.sample.ts` binds each slot to sample connections defined in\\n`connections/samples.ts`. Key details:\\n\\n- Uses Google Cloud Secret Manager URIs for all credentials.\\n- Enables knowledge spaces `knowledge.financial-docs` and\\n  `knowledge.email-threads`, plus the derived summaries space\\n  `knowledge.financial-overview` populated by open banking workflows.\\n- Keeps `voicePlayback` and `paymentsProcessing` optional so tenants can\\n  enable them incrementally.\\n\\n## Contracts\\n\\n`contracts/index.ts` defines command/query specs that power the\\nworkflows:\\n\\n- `pfo.documents.upload` \\u2013 store object + enqueue ingestion.\\n- `pfo.reminders.schedule-payment` \\u2013 send email/SMS/calendar reminders.\\n- `pfo.summary.generate` \\u2013 run RAG over knowledge spaces.\\n- `pfo.summary.dispatch` \\u2013 deliver summaries via email / voice.\\n- `pfo.email.sync-threads` \\u2013 ingest Gmail threads.\\n\\n## Workflows\\n\\n- **Process Uploaded Document**\\n  1. Upload to storage / queue ingestion.\\n  2. Optional human review step.\\n- **Upcoming Payments Reminder**\\n  1. Human review (confirm due date / channel).\\n  2. Automation schedules reminders (email/SMS/calendar).\\n- **Generate Financial Summary**\\n  1. Run RAG to produce Markdown summary.\\n  2. Dispatch summary (email + optional ElevenLabs voice note).\\n- **Ingest Email Threads**\\n  1. Sync Gmail threads into knowledge space.\\n  2. Triage step for operators when nothing new is ingested.\\n\\n## Knowledge & Jobs\\n\\n- Knowledge spaces registered via\\n  `registerFinancialDocsKnowledgeSpace` and\\n  `registerEmailThreadsKnowledgeSpace`.\\n- Ingestion adapters (`GmailIngestionAdapter`, `StorageIngestionAdapter`)\\n  and job handlers (`createGmailSyncHandler`,\\n  `createStorageDocumentHandler`) wire Gmail labels & GCS prefixes into\\n  Qdrant.\\n- `KnowledgeQueryService` provides summarisation + references for the\\n  summary generation workflow.\\n\\n## Tests & Usage\\n\\n`tests/pocket-family-office.test.ts` exercises:\\n\\n- Blueprint validation + config composition.\\n- In-memory ingestion of a sample invoice.\\n- Retrieval augmented generation producing a summary with references.\\n\\nUse these files as scaffolding for new tenants or as a template for the\\nhackathon deliverable. Replace the sample connection metadata with\\ntenant-specific IDs/secret references before deploying.\\n\\n\\n\\n',\n    },\n  ];\nregisterDocBlocks(tech_contracts_vertical_pocket_family_office_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,yDACX,CACE;CACE,IAAI;CACJ,OAAO;CACP,SAAS;CACT,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAa;EAAgC;CAC5D,MAAM;CACP,CACF;AACH,kBAAkB,uDAAuD"}

package/dist/docs/tech/lifecycle-stage-system.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/lifecycle-stage-system.docblock.d.ts
 declare const tech_lifecycle_stage_system_DocBlocks: DocBlock[];
 //#endregion
-export { tech_lifecycle_stage_system_DocBlocks };
+export { tech_lifecycle_stage_system_DocBlocks };
+//# sourceMappingURL=lifecycle-stage-system.docblock.d.ts.map

package/dist/docs/tech/lifecycle-stage-system.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"lifecycle-stage-system.docblock.d.ts","names":[],"sources":["../../../src/docs/tech/lifecycle-stage-system.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,uCAAuC"}

package/dist/docs/tech/lifecycle-stage-system.docblock.js

@@ -14,4 +14,5 @@ const tech_lifecycle_stage_system_DocBlocks = [{
 registerDocBlocks(tech_lifecycle_stage_system_DocBlocks);
 
 //#endregion
-export { tech_lifecycle_stage_system_DocBlocks };
+export { tech_lifecycle_stage_system_DocBlocks };
+//# sourceMappingURL=lifecycle-stage-system.docblock.js.map

package/dist/docs/tech/lifecycle-stage-system.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"lifecycle-stage-system.docblock.js","names":["tech_lifecycle_stage_system_DocBlocks: DocBlock[]"],"sources":["../../../src/docs/tech/lifecycle-stage-system.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../registry';\n\nexport const tech_lifecycle_stage_system_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.lifecycle-stage-system',\n    title: 'ContractSpec Lifecycle Stage System \\u2013 Technical Design',\n    summary:\n      '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.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/lifecycle-stage-system',\n    tags: ['tech', 'lifecycle-stage-system'],\n    body: '## ContractSpec Lifecycle Stage System \\u2013 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\\u250c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2510\\n\\u2502 @lssm/lib.lifecycle  \\u2502  Types, enums, helpers (pure data)\\n\\u2514\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u252c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2518\\n            \\u2502\\n\\u250c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u25bc\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2510    \\u250c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2510\\n\\u2502 modules/lifecycle-   \\u2502    \\u2502 modules/lifecycle-advisor  \\u2502\\n\\u2502 core (detection)     \\u2502    \\u2502 (guidance & ceremonies)    \\u2502\\n\\u2514\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u252c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2518    \\u2514\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u252c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2518\\n            \\u2502                           \\u2502\\n            \\u251c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u252c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2524\\n            \\u25bc            \\u25bc              \\u25bc\\n  Adapters: analytics, intent, questionnaires\\n            \\u2502\\n\\u250c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u25bc\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2510\\n\\u2502 bundles/lifecycle-   \\u2502  Managed service for Studio\\n\\u2502 managed              \\u2502  (REST handlers, AI agent)     \\u2502\\n\\u2514\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u252c\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2500\\u2518\\n            \\u2502\\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\\u20136) 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 \\u2192 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',\n  },\n];\nregisterDocBlocks(tech_lifecycle_stage_system_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,wCAAoD,CAC/D;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM,CAAC,QAAQ,yBAAyB;CACxC,MAAM;CACP,CACF;AACD,kBAAkB,sCAAsC"}

package/dist/docs/tech/llm/llm-integration.docblock.d.ts

@@ -4,4 +4,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 
 declare const tech_llm_integration_DocBlocks: DocBlock[];
 //#endregion
-export { tech_llm_integration_DocBlocks };
+export { tech_llm_integration_DocBlocks };
+//# sourceMappingURL=llm-integration.docblock.d.ts.map

package/dist/docs/tech/llm/llm-integration.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"llm-integration.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/llm/llm-integration.docblock.ts"],"sourcesContent":[],"mappings":";;;;cASa,gCAAgC"}

package/dist/docs/tech/llm/llm-integration.docblock.js

@@ -355,4 +355,5 @@ Each issue has:
 registerDocBlocks(tech_llm_integration_DocBlocks);
 
 //#endregion
-export { tech_llm_integration_DocBlocks };
+export { tech_llm_integration_DocBlocks };
+//# sourceMappingURL=llm-integration.docblock.js.map

package/dist/docs/tech/llm/llm-integration.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"llm-integration.docblock.js","names":["tech_llm_integration_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/llm/llm-integration.docblock.ts"],"sourcesContent":["/**\n * DocBlock: LLM Integration\n *\n * Documentation for ContractSpec's LLM integration features.\n */\n\nimport type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_llm_integration_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.llm.overview',\n    title: 'LLM Integration Overview',\n    summary:\n      'Export specs to LLM-friendly formats, generate implementation guides, and verify implementations.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/llm/overview',\n    tags: ['llm', 'ai', 'export', 'guide', 'verify'],\n    body: `# LLM Integration\n\nContractSpec provides first-class LLM integration to bridge specifications and AI coding agents.\n\n## Core Features\n\n### 1. Multi-Format Export\n\nExport specs to markdown in formats optimized for LLM consumption:\n\n- **Context format**: Summary for understanding (goal, context, acceptance criteria)\n- **Full format**: Complete spec with all details (I/O schemas, policy, events)\n- **Prompt format**: Actionable prompt with implementation instructions\n\n### 2. Implementation Guidance\n\nGenerate agent-specific implementation plans:\n\n- **Claude Code**: Extended thinking mode with structured prompts\n- **Cursor CLI**: Background/composer mode with .mdc rules generation\n- **Generic MCP**: Standard format for any MCP-compatible agent\n\n### 3. Tiered Verification\n\nVerify implementations against specs:\n\n- **Tier 1 (Structure)**: Types, exports, imports validation\n- **Tier 2 (Behavior)**: Scenario coverage, error handling, events\n- **Tier 3 (AI Review)**: Semantic compliance analysis via LLM\n\n## Access Points\n\n| Surface | Commands/Tools |\n|---------|---------------|\n| CLI | \\`contractspec llm export\\`, \\`guide\\`, \\`verify\\`, \\`copy\\` |\n| MCP | \\`llm.export\\`, \\`llm.guide\\`, \\`llm.verify\\` tools |\n| VSCode | Export to LLM, Generate Guide, Verify, Copy commands |\n\n## Quick Start\n\n### CLI Usage\n\n\\`\\`\\`bash\n# Export spec as markdown\ncontractspec llm export path/to/my.spec.ts --format full\n\n# Generate implementation guide\ncontractspec llm guide path/to/my.spec.ts --agent claude-code\n\n# Verify implementation\ncontractspec llm verify path/to/my.spec.ts path/to/impl.ts --tier 2\n\n# Copy spec to clipboard\ncontractspec llm copy path/to/my.spec.ts --format context\n\\`\\`\\`\n\n### MCP Usage\n\n\\`\\`\\`\n# Export spec\nllm.export { specPath: \"path/to/my.spec.ts\", format: \"full\" }\n\n# Generate guide\nllm.guide { specPath: \"path/to/my.spec.ts\", agent: \"cursor-cli\" }\n\n# Verify implementation\nllm.verify { specPath: \"path/to/my.spec.ts\", implementationPath: \"path/to/impl.ts\", tier: \"2\" }\n\\`\\`\\`\n\n### Programmatic Usage\n\n\\`\\`\\`typescript\nimport { specToFullMarkdown, specToAgentPrompt } from '@lssm/lib.contracts/llm';\nimport { createAgentGuideService, createVerifyService } from '@lssm/bundle.contractspec-workspace';\n\n// Export\nconst markdown = specToFullMarkdown(mySpec);\n\n// Generate guide\nconst guideService = createAgentGuideService({ defaultAgent: 'claude-code' });\nconst guide = guideService.generateGuide(mySpec);\n\n// Verify\nconst verifyService = createVerifyService();\nconst result = await verifyService.verify(mySpec, implementationCode, {\n  tiers: ['structure', 'behavior']\n});\n\\`\\`\\`\n`,\n  },\n  {\n    id: 'docs.tech.llm.export-formats',\n    title: 'LLM Export Formats',\n    summary:\n      'Detailed explanation of the three export formats for LLM consumption.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/llm/export-formats',\n    tags: ['llm', 'export', 'markdown'],\n    body: `# LLM Export Formats\n\nContractSpec provides three export formats optimized for different LLM use cases.\n\n## Context Format\n\nBest for: Understanding what a spec does, providing background to LLMs.\n\nIncludes:\n- Spec name, version, type\n- Goal and context\n- Description\n- Acceptance scenarios\n\nExample:\n\n\\`\\`\\`markdown\n# users.createUser (v1)\n\n> Create a new user account with email verification.\n\n**Type:** command | **Stability:** stable\n\n## Goal\nCreate a new user in the system and trigger email verification.\n\n## Context\nPart of the user onboarding flow. Called after signup form submission.\n\n## Acceptance Criteria\n### Happy path\n**Given:** Valid email and password\n**When:** User submits registration\n**Then:** Account is created, verification email is sent\n\\`\\`\\`\n\n## Full Format\n\nBest for: Complete documentation, implementation reference.\n\nIncludes everything:\n- All metadata\n- JSON schemas for I/O\n- Error definitions\n- Policy (auth, rate limits, PII)\n- Events emitted\n- Examples\n- Transport configuration\n\n## Prompt Format\n\nBest for: Feeding directly to coding agents.\n\nIncludes:\n- Task header with clear instructions\n- Full spec context\n- Implementation requirements\n- Task-specific guidance (implement/test/refactor/review)\n- Expected output format\n\nThe prompt format adapts based on task type:\n- **implement**: Full implementation with tests\n- **test**: Test generation for existing code\n- **refactor**: Refactoring while maintaining behavior\n- **review**: Code review against spec\n`,\n  },\n  {\n    id: 'docs.tech.llm.agent-adapters',\n    title: 'Agent Adapters',\n    summary: 'Adapters for different AI coding agents (Claude, Cursor, MCP).',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/llm/agent-adapters',\n    tags: ['llm', 'agents', 'claude', 'cursor', 'mcp'],\n    body: `# Agent Adapters\n\nContractSpec provides specialized adapters for different AI coding agents.\n\n## Claude Code Adapter\n\nOptimized for Anthropic Claude's extended thinking and code generation.\n\nFeatures:\n- Structured markdown with clear sections\n- Checklists for steps and verification\n- Icons for file operations (📝 create, ✏️ modify)\n- System prompt for ContractSpec context\n\nUsage:\n\\`\\`\\`typescript\nconst guideService = createAgentGuideService({ defaultAgent: 'claude-code' });\nconst result = guideService.generateGuide(spec, { agent: 'claude-code' });\n// result.prompt.systemPrompt - Claude system context\n// result.prompt.taskPrompt - Task-specific instructions\n\\`\\`\\`\n\n## Cursor CLI Adapter\n\nOptimized for Cursor's background/composer mode.\n\nFeatures:\n- Compact format for context efficiency\n- .mdc cursor rules generation\n- Integration with Cursor's file system\n- Concise step lists\n\nGenerate Cursor Rules:\n\\`\\`\\`typescript\nconst cursorRules = guideService.generateAgentConfig(spec, 'cursor-cli');\n// Save to .cursor/rules/my-spec.mdc\n\\`\\`\\`\n\n## Generic MCP Adapter\n\nWorks with any MCP-compatible agent (Cline, Aider, etc.).\n\nFeatures:\n- Standard markdown format\n- Table-based metadata\n- JSON resource format support\n- Prompt message format\n\nThe generic adapter is the default and works across all agents.\n\n## Choosing an Adapter\n\n| Agent | Best For | Key Features |\n|-------|----------|--------------|\n| Claude Code | Complex implementations | Extended thinking, detailed steps |\n| Cursor CLI | IDE-integrated work | Cursor rules, compact format |\n| Generic MCP | Any MCP agent | Universal compatibility |\n`,\n  },\n  {\n    id: 'docs.tech.llm.verification',\n    title: 'Implementation Verification',\n    summary: 'Tiered verification of implementations against specifications.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/llm/verification',\n    tags: ['llm', 'verify', 'validation', 'testing'],\n    body: `# Implementation Verification\n\nContractSpec provides tiered verification to check if implementations comply with specs.\n\n## Verification Tiers\n\n### Tier 1: Structure (Fast)\n\nChecks TypeScript structure against spec requirements:\n\n| Check | What it validates |\n|-------|------------------|\n| Handler export | Function is properly exported |\n| Contracts import | Imports from @lssm/lib.contracts |\n| Schema import | Imports from @lssm/lib.schema |\n| No \\`any\\` type | TypeScript strict compliance |\n| Error handling | Error codes are referenced |\n| Event emission | Event patterns exist |\n| Input validation | Validation patterns used |\n| Async patterns | Async/await for commands |\n\n### Tier 2: Behavior (Comprehensive)\n\nChecks implementation coverage of spec behaviors:\n\n| Check | What it validates |\n|-------|------------------|\n| Scenario coverage | Acceptance scenarios implemented |\n| Example coverage | Example I/O values referenced |\n| Error cases | All error conditions handled |\n| Event conditions | Events emitted correctly |\n| Idempotency | Idempotent patterns (if required) |\n\n### Tier 3: AI Review (Deep)\n\nUses LLM for semantic analysis:\n\n- Does the implementation fulfill the spec's intent?\n- Are edge cases properly handled?\n- Is the code quality acceptable?\n- Are there any subtle violations?\n\nRequires AI API key configuration.\n\n## Running Verification\n\n\\`\\`\\`typescript\nconst verifyService = createVerifyService({\n  aiApiKey: process.env.ANTHROPIC_API_KEY, // Optional, for Tier 3\n  aiProvider: 'anthropic',\n});\n\nconst result = await verifyService.verify(spec, implementationCode, {\n  tiers: ['structure', 'behavior'],\n  failFast: false,\n  includeSuggestions: true,\n});\n\nconsole.log(result.passed);  // true/false\nconsole.log(result.score);   // 0-100\nconsole.log(result.summary); // Human-readable summary\n\\`\\`\\`\n\n## Verification Report\n\nThe report includes:\n\n- **passed**: Overall compliance\n- **score**: 0-100 score\n- **issues**: Array of problems found\n- **suggestions**: Recommended fixes\n- **coverage**: Metrics on scenario/error/field coverage\n\nEach issue has:\n- **severity**: error, warning, or info\n- **category**: type, export, import, scenario, error_handling, semantic\n- **message**: Description of the issue\n- **suggestion**: How to fix it\n`,\n  },\n];\n\nregisterDocBlocks(tech_llm_integration_DocBlocks);\n"],"mappings":";;;AASA,MAAaA,iCAA6C;CACxD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAM;GAAU;GAAS;GAAS;EAChD,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAyFP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SACE;EACF,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAU;GAAW;EACnC,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAkEP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SAAS;EACT,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAU;GAAU;GAAU;GAAM;EAClD,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA0DP;CACD;EACE,IAAI;EACJ,OAAO;EACP,SAAS;EACT,MAAM;EACN,YAAY;EACZ,OAAO;EACP,MAAM;GAAC;GAAO;GAAU;GAAc;GAAU;EAChD,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EA+EP;CACF;AAED,kBAAkB,+BAA+B"}

package/dist/docs/tech/mcp-endpoints.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/mcp-endpoints.docblock.d.ts
 declare const tech_mcp_endpoints_DocBlocks: DocBlock[];
 //#endregion
-export { tech_mcp_endpoints_DocBlocks };
+export { tech_mcp_endpoints_DocBlocks };
+//# sourceMappingURL=mcp-endpoints.docblock.d.ts.map

package/dist/docs/tech/mcp-endpoints.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-endpoints.docblock.d.ts","names":[],"sources":["../../../src/docs/tech/mcp-endpoints.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,8BAA8B"}

package/dist/docs/tech/mcp-endpoints.docblock.js

@@ -35,4 +35,5 @@ Three dedicated MCP servers keep AI agents efficient and scoped:
 registerDocBlocks(tech_mcp_endpoints_DocBlocks);
 
 //#endregion
-export { tech_mcp_endpoints_DocBlocks };
+export { tech_mcp_endpoints_DocBlocks };
+//# sourceMappingURL=mcp-endpoints.docblock.js.map

package/dist/docs/tech/mcp-endpoints.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"mcp-endpoints.docblock.js","names":["tech_mcp_endpoints_DocBlocks: DocBlock[]"],"sources":["../../../src/docs/tech/mcp-endpoints.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../registry';\n\nexport const tech_mcp_endpoints_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.mcp.endpoints',\n    title: 'ContractSpec MCP endpoints',\n    summary:\n      'Dedicated MCP servers for docs, CLI usage, and internal development.',\n    kind: 'reference',\n    visibility: 'mixed',\n    route: '/docs/tech/mcp/endpoints',\n    tags: ['mcp', 'docs', 'cli', 'internal'],\n    body: `# ContractSpec MCP endpoints\n\nThree dedicated MCP servers keep AI agents efficient and scoped:\n\n- **Docs MCP**: \\`/api/mcp/docs\\` — exposes DocBlocks as resources + presentations. Tool: \\`docs.search\\`.\n- **CLI MCP**: \\`/api/mcp/cli\\` — surfaces CLI quickstart/reference/README and suggests commands. Tool: \\`cli.suggestCommand\\`.\n- **Internal MCP**: \\`/api/mcp/internal\\` — internal routing hints, playbook, and example registry access. Tool: \\`internal.describe\\`.\n\n### Usage notes\n- Transports are HTTP POST (streamable HTTP); SSE is disabled.\n- Resources are namespaced (\\`docs://*\\`, \\`cli://*\\`, \\`internal://*\\`) and are read-only.\n- Internal MCP also exposes the examples registry via \\`examples://*\\` resources:\n  - \\`examples://list?q=<query>\\`\n  - \\`examples://example/<id>\\`\n- Prompts mirror each surface (navigator, usage, bootstrap) for quick agent onboarding.\n- GraphQL remains at \\`/graphql\\`; health at \\`/health\\`.\n`,\n  },\n];\n\nregisterDocBlocks(tech_mcp_endpoints_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,+BAA2C,CACtD;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAO;EAAQ;EAAO;EAAW;CACxC,MAAM;;;;;;;;;;;;;;;;;CAiBP,CACF;AAED,kBAAkB,6BAA6B"}

package/dist/docs/tech/presentation-runtime.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/presentation-runtime.docblock.d.ts
 declare const tech_presentation_runtime_DocBlocks: DocBlock[];
 //#endregion
-export { tech_presentation_runtime_DocBlocks };
+export { tech_presentation_runtime_DocBlocks };
+//# sourceMappingURL=presentation-runtime.docblock.d.ts.map

package/dist/docs/tech/presentation-runtime.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"presentation-runtime.docblock.d.ts","names":[],"sources":["../../../src/docs/tech/presentation-runtime.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,qCAAqC"}

package/dist/docs/tech/presentation-runtime.docblock.js

@@ -14,4 +14,5 @@ const tech_presentation_runtime_DocBlocks = [{
 registerDocBlocks(tech_presentation_runtime_DocBlocks);
 
 //#endregion
-export { tech_presentation_runtime_DocBlocks };
+export { tech_presentation_runtime_DocBlocks };
+//# sourceMappingURL=presentation-runtime.docblock.js.map

package/dist/docs/tech/presentation-runtime.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"presentation-runtime.docblock.js","names":["tech_presentation_runtime_DocBlocks: DocBlock[]"],"sources":["../../../src/docs/tech/presentation-runtime.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../registry';\n\nexport const tech_presentation_runtime_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.presentation-runtime',\n    title: 'Presentation Runtime',\n    summary: 'Cross-platform runtime for list pages and presentation flows.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/presentation-runtime',\n    tags: ['tech', 'presentation-runtime'],\n    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\\u2011all 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\\u2011page companion convention: add `app/<route>/ai.ts` exporting a `PresentationDescriptorV2`.\\n- Build\\u2011time 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\",\n  },\n];\nregisterDocBlocks(tech_presentation_runtime_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,sCAAkD,CAC7D;CACE,IAAI;CACJ,OAAO;CACP,SAAS;CACT,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM,CAAC,QAAQ,uBAAuB;CACtC,MAAM;CACP,CACF;AACD,kBAAkB,oCAAoC"}

package/dist/docs/tech/schema/README.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/schema/README.docblock.d.ts
 declare const tech_schema_README_DocBlocks: DocBlock[];
 //#endregion
-export { tech_schema_README_DocBlocks };
+export { tech_schema_README_DocBlocks };
+//# sourceMappingURL=README.docblock.d.ts.map

package/dist/docs/tech/schema/README.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"README.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/schema/README.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,8BAA8B"}

package/dist/docs/tech/schema/README.docblock.js

@@ -18,4 +18,5 @@ const tech_schema_README_DocBlocks = [{
 registerDocBlocks(tech_schema_README_DocBlocks);
 
 //#endregion
-export { tech_schema_README_DocBlocks };
+export { tech_schema_README_DocBlocks };
+//# sourceMappingURL=README.docblock.js.map

package/dist/docs/tech/schema/README.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"README.docblock.js","names":["tech_schema_README_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/schema/README.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_schema_README_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.schema.README',\n    title: 'Multi\\u2011File Prisma Schema Conventions (per database)',\n    summary:\n      'We adopt Prisma multi\\u2011file schema (GA \\u2265 v6.7) to organize each database\\u2019s models by domain and to import core LSSM module schemas locally.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/schema/README',\n    tags: ['tech', 'schema', 'README'],\n    body: \"# Multi\\u2011File Prisma Schema Conventions (per database)\\n\\nWe adopt Prisma multi\\u2011file schema (GA \\u2265 v6.7) to organize each database\\u2019s 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\\u2011specific models split by bounded context\\n```\\n\\nNotes:\\n\\n- Imported files contain only `model` and `enum` blocks (strip `datasource`/`generator`).\\n- Preserve `@@schema(\\\"\\u2026\\\")` 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 \\u2013 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) \\u2013 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` \\u2013 core identity with email, optional phone, role, passkeys, apiKeys\\n- `Session` \\u2013 session tokens and metadata; includes `activeOrganizationId`\\n- `Account` \\u2013 external providers (password, OAuth)\\n- `Organization` \\u2013 tenant boundary; includes `type` additional field\\n- `Member`, `Invitation`, `Team`, `TeamMember` \\u2013 org/teams\\n- `Role`, `Permission`, `PolicyBinding` \\u2013 RBAC\\n- `ApiKey`, `Passkey` \\u2013 programmable access and WebAuthn\\n- `SsoProvider` \\u2013 OIDC/SAML provider configuration (org- or user-scoped)\\n- `OAuthApplication`, `OAuthAccessToken`, `OAuthConsent` \\u2013 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*\\u2026 but STRIT*\\u2026 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` \\u2013 base URL for Better Auth server\\n- `BETTER_AUTH_SECRET` \\u2013 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`\\u2192Organization, `uploadedBy`\\u2192User)\\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 \\u2192 GraphQL `String`\\n- Numbers \\u2192 `Int` if safe 32-bit integer else `Float`\\n- Booleans \\u2192 `Boolean`\\n- Dates \\u2192 custom `Date` scalar\\n- Arrays<T> \\u2192 list of mapped T (set `isArray: true` on the field)\\n- Top-level arrays \\u2192 set `isArray: true` on the model config\\n- Objects \\u2192 input/output object types with stable field order\\n- Unions \\u2192 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\",\n  },\n];\nregisterDocBlocks(tech_schema_README_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,+BAA2C,CACtD;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAQ;EAAU;EAAS;CAClC,MAAM;CACP,CACF;AACD,kBAAkB,6BAA6B"}

package/dist/docs/tech/studio/learning-events.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/learning-events.docblock.d.ts
 declare const tech_studio_learning_events_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_learning_events_DocBlocks };
+export { tech_studio_learning_events_DocBlocks };
+//# sourceMappingURL=learning-events.docblock.d.ts.map

package/dist/docs/tech/studio/learning-events.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"learning-events.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/learning-events.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,uCAAuC"}

package/dist/docs/tech/studio/learning-events.docblock.js

@@ -46,4 +46,5 @@ These events are intentionally minimal and must avoid PII/secrets in payloads.
 registerDocBlocks(tech_studio_learning_events_DocBlocks);
 
 //#endregion
-export { tech_studio_learning_events_DocBlocks };
+export { tech_studio_learning_events_DocBlocks };
+//# sourceMappingURL=learning-events.docblock.js.map

package/dist/docs/tech/studio/learning-events.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"learning-events.docblock.js","names":["tech_studio_learning_events_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/learning-events.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_learning_events_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.learning-events',\n    title: 'Studio Learning Events',\n    summary:\n      'Studio persists learning/activity events to the database; Sandbox keeps learning local-first and unlogged.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/learning-events',\n    tags: ['studio', 'learning', 'events', 'analytics', 'sandbox'],\n    body: `# Studio Learning Events\n\nStudio emits lightweight **learning/activity events** to support onboarding, ambient coaching, and learning journeys.\n\n## Persistence model\n\n- **Studio**: events are persisted to the database in \\`StudioLearningEvent\\` and are organization-scoped (optionally project-scoped).\n- **Sandbox**: events remain **local-only** (unlogged); they must never be sent to backend services.\n\n## GraphQL API\n\n- \\`recordLearningEvent(input: { name, projectId?, payload? })\\`\n- \\`myLearningEvents(projectId?, limit?)\\`\n- \\`myOnboardingTracks(productId?, includeProgress?)\\`\n- \\`myOnboardingProgress(trackKey)\\`\n- \\`dismissOnboardingTrack(trackKey)\\`\n\n## Common event names (convention)\n\n- \\`module.navigated\\` — user navigated to a Studio module (payload at minimum: \\`{ moduleId }\\`).\n- \\`studio.template.instantiated\\` — created a new Studio project (starter template). Payload commonly includes \\`{ templateId, projectSlug }\\`.\n- \\`spec.changed\\` — created or updated a Studio spec. Payload may include \\`{ action: 'create' | 'update', specId?, specType? }\\`.\n- \\`regeneration.completed\\` — finished a “regen/deploy” action (currently emitted on successful Studio deploy actions).\n- \\`studio.evolution.applied\\` — completed an Evolution session (payload commonly includes \\`{ evolutionSessionId }\\`).\n\nThese events are intentionally minimal and must avoid PII/secrets in payloads.\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_learning_events_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,wCAAoD,CAC/D;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAU;EAAY;EAAU;EAAa;EAAU;CAC9D,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2BP,CACF;AAED,kBAAkB,sCAAsC"}

package/dist/docs/tech/studio/learning-journeys.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/learning-journeys.docblock.d.ts
 declare const tech_studio_learning_journeys_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_learning_journeys_DocBlocks };
+export { tech_studio_learning_journeys_DocBlocks };
+//# sourceMappingURL=learning-journeys.docblock.d.ts.map

package/dist/docs/tech/studio/learning-journeys.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"learning-journeys.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/learning-journeys.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,yCAAyC"}

package/dist/docs/tech/studio/learning-journeys.docblock.js

@@ -77,4 +77,5 @@ Learning journey progress lives in the \`lssm_learning\` schema:
 registerDocBlocks(tech_studio_learning_journeys_DocBlocks);
 
 //#endregion
-export { tech_studio_learning_journeys_DocBlocks };
+export { tech_studio_learning_journeys_DocBlocks };
+//# sourceMappingURL=learning-journeys.docblock.js.map

package/dist/docs/tech/studio/learning-journeys.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"learning-journeys.docblock.js","names":["tech_studio_learning_journeys_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/learning-journeys.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_learning_journeys_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.learning-journeys',\n    title: 'Studio learning journeys (onboarding + coach)',\n    summary:\n      'DB-backed learning journeys tracked per organization: seeded tracks/steps, event-driven progress, XP/streaks, and a Studio coach surface.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/learning-journeys',\n    tags: [\n      'studio',\n      'learning',\n      'onboarding',\n      'journey',\n      'graphql',\n      'database',\n    ],\n    body: `# Studio learning journeys\n\nStudio supports **DB-backed learning journeys** (onboarding tracks + ambient coach tips) that are advanced by **recorded learning events**.\n\n> See also: \\`/docs/tech/studio/learning-events\\` for event naming + payload guardrails.\n\n## Scope (multi-tenancy)\n\n- Progress is tracked **per organization** (tenant/workspace), via a \\`Learner\\` record keyed by \\`(userId, organizationId)\\`.\n- Learning events are stored as \\`StudioLearningEvent\\` under the Studio DB schema, scoped to an organization (optionally a project).\n\n## Persistence model (Prisma)\n\nLearning journey progress lives in the \\`lssm_learning\\` schema:\n\n- \\`Learner\\` — one per \\`(userId, organizationId)\\`\n- \\`OnboardingTrack\\` — seeded track definitions (trackKey, name, metadata)\n- \\`OnboardingStep\\` — seeded step definitions (stepKey, completionCondition, xpReward, metadata)\n- \\`OnboardingProgress\\` — learner × track progress (progress %, xpEarned, completedAt, dismissedAt)\n- \\`OnboardingStepCompletion\\` — append-only completion records (stepKey, status, xpEarned, completedAt)\n\n## Track definition source (spec-first)\n\n- Canonical track specs live in \\`@lssm/example.learning-journey-registry\\`.\n- The Studio API seeds/updates the DB definitions via an idempotent “ensure tracks” routine.\n- The DB is kept aligned with track specs (stale steps are removed) to prevent drift and unblock completion.\n\n## Progress advancement (event-driven)\n\n1) UI records an event via GraphQL \\`recordLearningEvent\\`\n2) Backend creates \\`StudioLearningEvent\\`\n3) Backend advances onboarding by matching the new event against step completion conditions\n4) Backend persists step completions and recomputes:\n   - \\`progress\\` percentage\n   - \\`xpEarned\\` (including streak/completion bonuses when configured)\n   - track completion state (\\`completedAt\\`)\n\n## GraphQL API (Studio)\n\n- \\`myOnboardingTracks(productId?, includeProgress?)\\`\n  - returns all tracks + optional progress for the current learner\n- \\`myOnboardingProgress(trackKey)\\`\n  - returns progress + step completion list for a single track\n- \\`dismissOnboardingTrack(trackKey)\\`\n  - marks a track dismissed for the learner (prevents auto-coach)\n\n## UI routes/surfaces (web)\n\n- \\`/studio/learning\\` — learning hub (track list + progress widget)\n- \\`/studio/learning/{trackKey}\\` — track detail (steps + map)\n- Studio shell mounts a **coach sheet** that can auto-open for incomplete, non-dismissed onboarding.\n\n## Security + data hygiene\n\n- Do not put secrets/PII in \\`payload\\` fields of learning events.\n- Prefer shallow payload filters (small, stable keys).\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_learning_journeys_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,0CAAsD,CACjE;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EACJ;EACA;EACA;EACA;EACA;EACA;EACD;CACD,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyDP,CACF;AAED,kBAAkB,wCAAwC"}

package/dist/docs/tech/studio/platform-admin-panel.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/platform-admin-panel.docblock.d.ts
 declare const tech_studio_platform_admin_panel_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_platform_admin_panel_DocBlocks };
+export { tech_studio_platform_admin_panel_DocBlocks };
+//# sourceMappingURL=platform-admin-panel.docblock.d.ts.map

package/dist/docs/tech/studio/platform-admin-panel.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"platform-admin-panel.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/platform-admin-panel.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,4CAA4C"}

package/dist/docs/tech/studio/platform-admin-panel.docblock.js

@@ -82,4 +82,5 @@ The platform-admin GraphQL operations are guarded by the active org type and inc
 registerDocBlocks(tech_studio_platform_admin_panel_DocBlocks);
 
 //#endregion
-export { tech_studio_platform_admin_panel_DocBlocks };
+export { tech_studio_platform_admin_panel_DocBlocks };
+//# sourceMappingURL=platform-admin-panel.docblock.js.map

package/dist/docs/tech/studio/platform-admin-panel.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"platform-admin-panel.docblock.js","names":["tech_studio_platform_admin_panel_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/platform-admin-panel.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_platform_admin_panel_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.platform-admin-panel',\n    title: 'Studio Platform Admin Panel',\n    summary:\n      'How PLATFORM_ADMIN organizations manage tenant orgs and integration connections without session switching.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/platform-admin-panel',\n    tags: ['studio', 'admin', 'multi-tenancy', 'integrations', 'better-auth'],\n    body: `# Studio Platform Admin Panel\n\nContractSpec Studio exposes a dedicated **Platform Admin Panel** for users whose **active organization** has:\n\n- \\`Organization.type = PLATFORM_ADMIN\\`\n\nThe UI route is:\n\n- \\`/studio/admin\\`\n\n## Authorization model (no org switching)\n\nPlatform admins **remain in their own organization**. Cross-tenant actions are always explicit and scoped:\n\n- Admin operations require an explicit \\`targetOrganizationId\\`.\n- No session / activeOrganizationId switching is performed as part of admin operations.\n\n## Integrations management\n\nThe admin panel manages the full ContractSpec Integrations system:\n\n- Lists all shipped \\`IntegrationSpec\\` entries (registry built via \\`createDefaultIntegrationSpecRegistry()\\`).\n- CRUD \\`IntegrationConnection\\` records for a selected tenant org.\n\n### Secrets (reference-only + write-only)\n\nThe admin UI supports two modes:\n\n- **Reference-only (BYOK)**: store only \\`secretProvider\\` + \\`secretRef\\`.\n- **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**.\n\nSupported backends:\n\n- Env overrides (\\`env://...\\`)\n- Google Cloud Secret Manager (\\`gcp://...\\`)\n- AWS Secrets Manager (\\`aws://secretsmanager/...\\`)\n- Scaleway Secret Manager (\\`scw://secret-manager/...\\`)\n\n## Better Auth Admin plugin\n\nThe panel uses the Better Auth **Admin plugin** for user operations (list users, impersonation):\n\n- Client calls use \\`authClient.admin.*\\`.\n- Server-side, ContractSpec enforces that users in a PLATFORM_ADMIN active org have \\`User.role\\` containing \\`admin\\` so Better Auth Admin endpoints authorize.\n\n## GraphQL surface\n\nThe platform-admin GraphQL operations are guarded by the active org type and include:\n\n- \\`platformAdminOrganizations(search, limit, offset)\\`\n- \\`platformAdminIntegrationSpecs\\`\n- \\`platformAdminIntegrationConnections(input: { targetOrganizationId, category?, status? })\\`\n- \\`platformAdminIntegrationConnectionCreate(input)\\`\n- \\`platformAdminIntegrationConnectionUpdate(input)\\`\n- \\`platformAdminIntegrationConnectionDelete(targetOrganizationId, connectionId)\\`\n\n## Key implementation files\n\n- Auth + role enforcement: \\`packages/bundles/contractspec-studio/src/application/services/auth.ts\\`\n- Admin GraphQL module: \\`packages/bundles/contractspec-studio/src/infrastructure/graphql/modules/platform-admin.ts\\`\n- Integrations admin service: \\`packages/bundles/contractspec-studio/src/modules/platform-integrations/index.ts\\`\n- Web route: \\`packages/apps/web-landing/src/app/(app-customer)/studio/admin/*\\`\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_platform_admin_panel_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,6CAAyD,CACpE;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAU;EAAS;EAAiB;EAAgB;EAAc;CACzE,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+DP,CACF;AAED,kBAAkB,2CAA2C"}

package/dist/docs/tech/studio/project-access-teams.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/project-access-teams.docblock.d.ts
 declare const tech_studio_project_access_teams_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_project_access_teams_DocBlocks };
+export { tech_studio_project_access_teams_DocBlocks };
+//# sourceMappingURL=project-access-teams.docblock.d.ts.map

package/dist/docs/tech/studio/project-access-teams.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-access-teams.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/project-access-teams.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,4CAA4C"}

package/dist/docs/tech/studio/project-access-teams.docblock.js

@@ -43,4 +43,5 @@ Payloads and events must avoid secrets/PII. For Sandbox, the model remains local
 registerDocBlocks(tech_studio_project_access_teams_DocBlocks);
 
 //#endregion
-export { tech_studio_project_access_teams_DocBlocks };
+export { tech_studio_project_access_teams_DocBlocks };
+//# sourceMappingURL=project-access-teams.docblock.js.map

package/dist/docs/tech/studio/project-access-teams.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-access-teams.docblock.js","names":["tech_studio_project_access_teams_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/project-access-teams.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_project_access_teams_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.project-access-teams',\n    title: 'Studio Project Access via Teams',\n    summary:\n      'Projects live under organizations; team sharing refines access with an admin/owner override.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/project-access-teams',\n    tags: ['studio', 'projects', 'teams', 'rbac', 'access-control'],\n    body: `# Studio Project Access via Teams\n\nStudio access control is **organization-first** with optional **team-based sharing**.\n\n## Data model\n\n- \\`Team\\` and \\`TeamMember\\` define team membership inside an organization.\n- \\`StudioProject\\` is owned by an organization.\n- \\`StudioProjectTeam\\` links projects to 0..N teams.\n\n## Access rules\n\n- **Admins/owners**: always have access to all projects in the organization.\n- **Org-wide projects**: if a project has **no team links**, all organization members can access it.\n- **Team-scoped projects**: if a project has **one or more team links**, a user must be a member of at least one linked team.\n\n## GraphQL surfaces\n\n- 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\n## Related\\n+\\n+- Team administration + invitations: see \\`/docs/tech/studio/team-invitations\\`.\\n+\n## Notes\n\nPayloads and events must avoid secrets/PII. For Sandbox, the model remains local-first and unlogged.\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_project_access_teams_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,6CAAyD,CACpE;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAU;EAAY;EAAS;EAAQ;EAAiB;CAC/D,MAAM;;;;;;;;;;;;;;;;;;;;;;;;CAwBP,CACF;AAED,kBAAkB,2CAA2C"}

package/dist/docs/tech/studio/project-routing.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/project-routing.docblock.d.ts
 declare const tech_studio_project_routing_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_project_routing_DocBlocks };
+export { tech_studio_project_routing_DocBlocks };
+//# sourceMappingURL=project-routing.docblock.d.ts.map

package/dist/docs/tech/studio/project-routing.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-routing.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/project-routing.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,uCAAuC"}

package/dist/docs/tech/studio/project-routing.docblock.js

@@ -65,4 +65,5 @@ The following project modules are expected under \`/studio/{projectSlug}\`:
 registerDocBlocks(tech_studio_project_routing_DocBlocks);
 
 //#endregion
-export { tech_studio_project_routing_DocBlocks };
+export { tech_studio_project_routing_DocBlocks };
+//# sourceMappingURL=project-routing.docblock.js.map

package/dist/docs/tech/studio/project-routing.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-routing.docblock.js","names":["tech_studio_project_routing_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/project-routing.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_project_routing_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.project-routing',\n    title: 'Studio Project Routing',\n    summary:\n      'Studio uses slugged, project-first routes: /studio/{projectSlug}/* with canonical slug redirects and soft-deleted projects hidden.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/project-routing',\n    tags: ['studio', 'routing', 'projects', 'slug', 'redirects'],\n    body: `# Studio Project Routing\n\nContractSpec Studio uses a **project-first URL scheme**:\n\n- \\`/studio/projects\\` — create, select, and delete projects.\n- \\`/studio/{projectSlug}/*\\` — project modules (canvas/specs/deploy/integrations/evolution/learning).\n- \\`/studio/learning\\` — learning hub that does not require selecting a project.\n\n## Studio layout shell\n\nStudio routes are wrapped in a dedicated **Studio app shell** (header + footer) that provides in-app navigation (Projects/Learning/Teams), organization switching, and account actions.\n\nProject module routes (\\`/studio/{projectSlug}/*\\`) render their own module shell (\\`WorkspaceProjectShellLayout\\`). When combined with the global Studio header, the project shell uses a **sticky header offset** to avoid overlapping sticky headers.\n\n## Slug behavior (rename-safe)\n\n- Each project has a \\`slug\\` stored in the database (\\`StudioProject.slug\\`).\n- When a project name changes, Studio **updates the slug** and stores the previous slug as an alias (\\`StudioProjectSlugAlias\\`).\n- Requests to an alias slug are **redirected to the canonical slug**.\n\nGraphQL entrypoint:\n\n- \\`studioProjectBySlug(slug: String!)\\` returns:\n  - \\`project\\`\n  - \\`canonicalSlug\\`\n  - \\`wasRedirect\\`\n\n## Deletion behavior (soft delete)\n\nProjects are **soft-deleted**:\n\n- \\`deleteStudioProject(id: String!)\\` sets \\`StudioProject.deletedAt\\`.\n- All listings and access checks filter \\`deletedAt = null\\`.\n- Soft-deleted projects are treated as “not found” in Studio routes and GraphQL access checks.\n\n## Available modules for a selected project\n\nThe following project modules are expected under \\`/studio/{projectSlug}\\`:\n\n- \\`/canvas\\` — Visual builder canvas (stored via overlays and canvas versions).\n- \\`/specs\\` — Spec editor (stored as \\`StudioSpec\\`).\n- \\`/deploy\\` — Deployments history + triggers (stored as \\`StudioDeployment\\`).\n- \\`/integrations\\` — Integrations scoped to project (stored as \\`StudioIntegration\\`).\n- \\`/evolution\\` — Evolution sessions (stored as \\`EvolutionSession\\`).\n- \\`/learning\\` — Project learning activity.\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_project_routing_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,wCAAoD,CAC/D;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAU;EAAW;EAAY;EAAQ;EAAY;CAC5D,MAAM;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8CP,CACF;AAED,kBAAkB,sCAAsC"}

package/dist/docs/tech/studio/sandbox-unlogged.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/sandbox-unlogged.docblock.d.ts
 declare const tech_studio_sandbox_unlogged_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_sandbox_unlogged_DocBlocks };
+export { tech_studio_sandbox_unlogged_DocBlocks };
+//# sourceMappingURL=sandbox-unlogged.docblock.d.ts.map

package/dist/docs/tech/studio/sandbox-unlogged.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sandbox-unlogged.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/sandbox-unlogged.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,wCAAwC"}

package/dist/docs/tech/studio/sandbox-unlogged.docblock.js

@@ -38,4 +38,5 @@ const tech_studio_sandbox_unlogged_DocBlocks = [{
 registerDocBlocks(tech_studio_sandbox_unlogged_DocBlocks);
 
 //#endregion
-export { tech_studio_sandbox_unlogged_DocBlocks };
+export { tech_studio_sandbox_unlogged_DocBlocks };
+//# sourceMappingURL=sandbox-unlogged.docblock.js.map

package/dist/docs/tech/studio/sandbox-unlogged.docblock.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"sandbox-unlogged.docblock.js","names":["tech_studio_sandbox_unlogged_DocBlocks: DocBlock[]"],"sources":["../../../../src/docs/tech/studio/sandbox-unlogged.docblock.ts"],"sourcesContent":["import type { DocBlock } from '@lssm/lib.contracts/docs';\nimport { registerDocBlocks } from '../../registry';\n\nexport const tech_studio_sandbox_unlogged_DocBlocks: DocBlock[] = [\n  {\n    id: 'docs.tech.studio.sandbox.unlogged',\n    title: 'Sandbox (unlogged) vs Studio (authenticated)',\n    summary:\n      'The sandbox is a lightweight, unlogged surface that mirrors Studio navigation without auth or analytics.',\n    kind: 'reference',\n    visibility: 'public',\n    route: '/docs/tech/studio/sandbox-unlogged',\n    tags: ['studio', 'sandbox', 'privacy', 'analytics'],\n    body: `## Sandbox guarantees\n\n- Route: \\`/sandbox\\`\n- **No auth requirement**\n- **No PostHog init**\n- **No Vercel Analytics**\n- Local-only state (in-browser runtime + localStorage where needed)\n\n## What Sandbox is for\n\n- Try templates and feature modules safely\n- Preview specs/builder/evolution/learning\n- Produce copyable CLI commands (no side effects)\n\n## What Sandbox is *not* for\n\n- Persisted projects/workspaces\n- Real deployments\n- Organization-scoped integrations (unless explicitly enabled later)\n`,\n  },\n];\n\nregisterDocBlocks(tech_studio_sandbox_unlogged_DocBlocks);\n"],"mappings":";;;AAGA,MAAaA,yCAAqD,CAChE;CACE,IAAI;CACJ,OAAO;CACP,SACE;CACF,MAAM;CACN,YAAY;CACZ,OAAO;CACP,MAAM;EAAC;EAAU;EAAW;EAAW;EAAY;CACnD,MAAM;;;;;;;;;;;;;;;;;;;;CAoBP,CACF;AAED,kBAAkB,uCAAuC"}

package/dist/docs/tech/studio/team-invitations.docblock.d.ts

@@ -3,4 +3,5 @@ import { DocBlock } from "@lssm/lib.contracts/docs";
 //#region src/docs/tech/studio/team-invitations.docblock.d.ts
 declare const tech_studio_team_invitations_DocBlocks: DocBlock[];
 //#endregion
-export { tech_studio_team_invitations_DocBlocks };
+export { tech_studio_team_invitations_DocBlocks };
+//# sourceMappingURL=team-invitations.docblock.d.ts.map

package/dist/docs/tech/studio/team-invitations.docblock.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"team-invitations.docblock.d.ts","names":[],"sources":["../../../../src/docs/tech/studio/team-invitations.docblock.ts"],"sourcesContent":[],"mappings":";;;cAGa,wCAAwC"}

package/dist/docs/tech/studio/team-invitations.docblock.js

@@ -67,4 +67,5 @@ Acceptance rules:
 registerDocBlocks(tech_studio_team_invitations_DocBlocks);
 
 //#endregion
-export { tech_studio_team_invitations_DocBlocks };
+export { tech_studio_team_invitations_DocBlocks };
+//# sourceMappingURL=team-invitations.docblock.js.map