@lssm/example.crm-pipeline 0.0.0-canary-20251217083314 → 1.41.0

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/index.js

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

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/presentations.js

@@ -1,71 +0,0 @@
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/presentations.js
-const DEFAULT_TARGETS = [
-	"markdown",
-	"application/json",
-	"application/xml",
-	"react"
-];
-function normalizeRoute(route) {
-	if (!route.length) return "/";
-	const withLeading = route.startsWith("/") ? route : `/${route}`;
-	return withLeading === "/" ? "/" : withLeading.replace(/\/+$/, "");
-}
-function deriveRoute(block, routePrefix) {
-	if (block.route) return normalizeRoute(block.route);
-	const prefix = routePrefix ?? "/docs";
-	const slug = block.id.replace(/^docs\.?/, "").replace(/\./g, "/").replace(/\/+/g, "/");
-	return normalizeRoute(slug.startsWith("/") ? slug : `${prefix}/${slug}`);
-}
-function buildName(block, namespace) {
-	return namespace ? `${namespace}.${block.id}` : block.id;
-}
-function docBlockToPresentationV2(block, options) {
-	const targets = options?.defaultTargets ?? DEFAULT_TARGETS;
-	const version = block.version ?? options?.defaultVersion ?? 1;
-	const stability = block.stability ?? options?.defaultStability ?? "stable";
-	return {
-		meta: {
-			name: buildName(block, options?.namespace),
-			version,
-			description: block.summary ?? block.title,
-			tags: block.tags,
-			owners: block.owners,
-			domain: block.domain,
-			stability
-		},
-		policy: block.visibility && block.visibility !== "public" ? { flags: [block.visibility] } : void 0,
-		source: {
-			type: "blocknotejs",
-			docJson: block.body
-		},
-		targets
-	};
-}
-function docBlockToPresentationSpec(block, options) {
-	const version = block.version ?? options?.defaultVersion ?? 1;
-	const stability = block.stability ?? options?.defaultStability ?? "stable";
-	return {
-		meta: {
-			name: buildName(block, options?.namespace),
-			version,
-			stability,
-			tags: block.tags,
-			owners: block.owners,
-			description: block.summary ?? block.title
-		},
-		content: {
-			kind: "markdown",
-			content: block.body
-		}
-	};
-}
-function docBlocksToPresentationRoutes(blocks, options) {
-	return blocks.map((block) => ({
-		block,
-		route: deriveRoute(block, options?.routePrefix),
-		descriptor: docBlockToPresentationV2(block, options)
-	}));
-}
-
-//#endregion
-export { docBlockToPresentationSpec, docBlocksToPresentationRoutes };

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/registry.js

@@ -1,44 +0,0 @@
-import { docBlockToPresentationSpec, docBlocksToPresentationRoutes } from "./presentations.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/registry.js
-var DocRegistry = class {
-	routes = /* @__PURE__ */ new Map();
-	constructor(blocks = [], options) {
-		blocks.forEach((block) => this.register(block, options));
-	}
-	register(block, options) {
-		const [route] = docBlocksToPresentationRoutes([block], options);
-		if (route) this.routes.set(block.id, route);
-		return this;
-	}
-	list() {
-		return [...this.routes.values()];
-	}
-	get(id) {
-		return this.routes.get(id);
-	}
-	toRouteTuples() {
-		return this.list().map(({ route, descriptor }) => [route, descriptor]);
-	}
-	toPresentationSpecs(options) {
-		return this.list().map(({ block }) => docBlockToPresentationSpec(block, options));
-	}
-};
-const requiredFields = [
-	"id",
-	"title",
-	"body",
-	"kind",
-	"visibility",
-	"route"
-];
-const defaultDocRegistry = new DocRegistry();
-function registerDocBlocks(blocks) {
-	for (const block of blocks) {
-		for (const field of requiredFields) if (!block[field]) throw new Error(`DocBlock ${block.id ?? "<missing id>"} missing field ${String(field)}`);
-		defaultDocRegistry.register(block);
-	}
-}
-
-//#endregion
-export { registerDocBlocks };

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_1_QUICKSTART.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_1_QUICKSTART.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.PHASE_1_QUICKSTART",
-	title: "Phase 1: API Reference Index",
-	summary: "Quick reference for all new Phase 1 APIs.",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/PHASE_1_QUICKSTART",
-	tags: ["tech", "PHASE_1_QUICKSTART"],
-	body: "# Phase 1: API Reference Index\n\nQuick reference for all new Phase 1 APIs.\n\n---\n\n## @lssm/lib.multi-tenancy\n\n### RLS\n```typescript\nimport { createRlsMiddleware, type TenantIdProvider } from '@lssm/lib.multi-tenancy/rls';\n```\n\n### Provisioning\n```typescript\nimport { \n  TenantProvisioningService,\n  type CreateTenantInput,\n  type TenantProvisioningConfig \n} from '@lssm/lib.multi-tenancy/provisioning';\n```\n\n### Isolation\n```typescript\nimport { IsolationValidator } from '@lssm/lib.multi-tenancy/isolation';\n```\n\n---\n\n## @lssm/lib.observability\n\n### Tracing\n```typescript\nimport { \n  getTracer,\n  traceAsync,\n  traceSync,\n  createTracingMiddleware \n} from '@lssm/lib.observability/tracing';\n```\n\n### Metrics\n```typescript\nimport {\n  getMeter,\n  createCounter,\n  createUpDownCounter,\n  createHistogram,\n  standardMetrics\n} from '@lssm/lib.observability/metrics';\n```\n\n### Logging\n```typescript\nimport {\n  Logger,\n  logger,\n  type LogLevel,\n  type LogEntry\n} from '@lssm/lib.observability/logging';\n```\n\n---\n\n## @lssm/lib.resilience\n\n### Circuit Breaker\n```typescript\nimport {\n  CircuitBreaker,\n  type CircuitState,\n  type CircuitBreakerConfig\n} from '@lssm/lib.resilience/circuit-breaker';\n```\n\n### Retry\n```typescript\nimport { retry } from '@lssm/lib.resilience/retry';\n```\n\n### Timeout\n```typescript\nimport { timeout } from '@lssm/lib.resilience/timeout';\n```\n\n### Fallback\n```typescript\nimport { fallback } from '@lssm/lib.resilience/fallback';\n```\n\n---\n\n## Enhanced: @lssm/lib.contracts\n\n### DataViews\n```typescript\nimport { DataViewQueryGenerator } from '@lssm/lib.contracts/data-views/query-generator';\nimport { DataViewRuntime } from '@lssm/lib.contracts/data-views/runtime';\n```\n\n### Workflows\n```typescript\nimport { SLAMonitor, type SLABreachEvent } from '@lssm/lib.contracts/workflow/sla-monitor';\nimport { PrismaStateStore } from '@lssm/lib.contracts/workflow/adapters/db-adapter';\n```\n\n---\n\n## Enhanced: @lssm/lib.design-system\n\n### DataView Components\n```typescript\nimport { DataViewRenderer } from '@lssm/lib.design-system/components/data-view/DataViewRenderer';\n// Also available: DataViewList, DataViewTable, DataViewDetail\n```\n\n---\n\n## Usage Examples\n\n### Complete Workflow with All Features\n\n```typescript\nimport { WorkflowRunner } from '@lssm/lib.contracts/workflow/runner';\nimport { PrismaStateStore } from '@lssm/lib.contracts/workflow/adapters/db-adapter';\nimport { SLAMonitor } from '@lssm/lib.contracts/workflow/sla-monitor';\nimport { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';\nimport { traceAsync } from '@lssm/lib.observability/tracing';\n\nconst runner = new WorkflowRunner({\n  registry,\n  stateStore: new PrismaStateStore(db),\n  opExecutor: async (op, input, ctx) => {\n    return traceAsync(`op.${op.name}`, async (span) => {\n      span.setAttribute('operation', op.name);\n      const breaker = getCircuitBreaker(op.name);\n      return breaker.execute(() => executeOperation(op, input, ctx));\n    });\n  },\n  eventEmitter: (event, payload) => {\n    if (event.startsWith('workflow.')) {\n      logger.info(event, payload);\n    }\n  },\n});\n\nconst monitor = new SLAMonitor((event, payload) => {\n  logger.warn('SLA_BREACH', payload);\n  alertOps(payload);\n});\n\n// Start workflow\nconst workflowId = await runner.start('payment.flow', 1);\n\n// Monitor SLA\nconst state = await runner.getState(workflowId);\nconst spec = registry.get('payment.flow', 1);\nmonitor.check(state, spec!);\n```\n\n### Complete DataView with Observability\n\n```typescript\nimport { DataViewRenderer } from '@lssm/lib.design-system';\nimport { DataViewQueryGenerator } from '@lssm/lib.contracts/data-views/query-generator';\nimport { traceAsync } from '@lssm/lib.observability/tracing';\nimport { MyDataView } from './specs/users.data-view';\n\nexport function UserListPage() {\n  const [page, setPage] = useState(1);\n  const [users, setUsers] = useState([]);\n\n  const loadUsers = async () => {\n    return traceAsync('load_users', async (span) => {\n      const generator = new DataViewQueryGenerator(MyDataView);\n      const query = generator.generate({ pagination: { page, pageSize: 20 } });\n      \n      span.setAttribute('page', page);\n      const result = await api.execute(query);\n      setUsers(result.data);\n    });\n  };\n\n  return (\n    <DataViewRenderer\n      spec={MyDataView}\n      items={users}\n      pagination={{ page, pageSize: 20, total: users.length }}\n      onPageChange={setPage}\n    />\n  );\n}\n```\n\n### Complete Multi-Tenant Setup\n\n```typescript\n// 1. RLS Middleware\nimport { createRlsMiddleware } from '@lssm/lib.multi-tenancy/rls';\ndb.$use(createRlsMiddleware(() => req.tenantId));\n\n// 2. Tenant Provisioning\nimport { TenantProvisioningService } from '@lssm/lib.multi-tenancy/provisioning';\nconst service = new TenantProvisioningService({ db });\n\n// 3. Create new tenant\nawait service.provision({\n  id: 'acme',\n  name: 'Acme Corp',\n  slug: 'acme',\n  ownerEmail: 'admin@acme.com',\n});\n\n// 4. Validate isolation in tests\nimport { IsolationValidator } from '@lssm/lib.multi-tenancy/isolation';\n\ntest('queries are isolated', () => {\n  const isValid = IsolationValidator.validateQuery(\n    'User',\n    'findMany',\n    { where: { tenantId: 'acme' } },\n    'acme'\n  );\n  expect(isValid).toBe(true);\n});\n```\n\n---\n\n## Testing\n\n### Test Circuit Breakers\n\n```typescript\nimport { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';\n\ntest('circuit opens after threshold', async () => {\n  const breaker = new CircuitBreaker({\n    failureThreshold: 3,\n    resetTimeoutMs: 5000,\n  });\n\n  // Trigger failures\n  for (let i = 0; i < 3; i++) {\n    await expect(\n      breaker.execute(() => Promise.reject('error'))\n    ).rejects.toThrow();\n  }\n\n  // Circuit should be open\n  await expect(\n    breaker.execute(() => Promise.resolve('ok'))\n  ).rejects.toThrow('CircuitBreaker is OPEN');\n});\n```\n\n### Test Workflow Retry\n\n```typescript\ntest('workflow retries on failure', async () => {\n  let attempts = 0;\n  const opExecutor = async () => {\n    attempts++;\n    if (attempts < 3) throw new Error('fail');\n    return 'success';\n  };\n\n  const runner = new WorkflowRunner({ /* ... */ opExecutor });\n  await runner.executeStep(workflowId);\n  \n  expect(attempts).toBe(3);\n});\n```\n\n---\n\n## Common Patterns\n\n### Pattern: Resilient External Call\n\n```typescript\nimport { CircuitBreaker } from '@lssm/lib.resilience/circuit-breaker';\nimport { retry } from '@lssm/lib.resilience/retry';\nimport { timeout } from '@lssm/lib.resilience/timeout';\nimport { traceAsync } from '@lssm/lib.observability/tracing';\n\nconst breaker = new CircuitBreaker({ failureThreshold: 5, resetTimeoutMs: 30000 });\n\nexport async function callExternalAPI(input: any) {\n  return traceAsync('external_api_call', async (span) => {\n    span.setAttribute('service', 'stripe');\n    \n    return breaker.execute(() =>\n      retry(\n        () => timeout(() => stripe.api.call(input), 5000),\n        3,\n        1000,\n        true\n      )\n    );\n  });\n}\n```\n\n**Benefits**: Circuit breaker + retry + timeout + tracing in one place.\n\n---\n\n### Pattern: Tenant-Aware Operation\n\n```typescript\nimport { traceAsync } from '@lssm/lib.observability/tracing';\n\nexport async function listUsers(tenantId: string) {\n  return traceAsync('list_users', async (span) => {\n    span.setAttribute('tenant_id', tenantId);\n    \n    // RLS middleware will inject WHERE tenantId = ?\n    return db.user.findMany();\n  });\n}\n```\n\n---\n\n### Pattern: Monitored Workflow\n\n```typescript\nimport { WorkflowRunner } from '@lssm/lib.contracts/workflow/runner';\nimport { SLAMonitor } from '@lssm/lib.contracts/workflow/sla-monitor';\nimport { logger } from '@lssm/lib.observability/logging';\n\nconst monitor = new SLAMonitor((event, payload) => {\n  logger.warn('workflow.sla_breach', payload);\n});\n\n// In workflow poller\nconst state = await runner.getState(workflowId);\nconst spec = registry.get(state.workflowName, state.workflowVersion);\nif (spec) {\n  monitor.check(state, spec);\n}\n```\n\n---\n\n## Next Steps\n\n1. **Implement one quick win** (30 minutes)\n2. **Add tests for new functionality** (1 hour)\n3. **Deploy to staging and verify observability** (1 hour)\n4. **Roll out to production** (monitor closely)\n5. **Read full documentation** at https://contractspec.lssm.tech/docs\n\n---\n\n**Questions?** See `/docs/guides/phase-1-migration` or reach out via https://contractspec.lssm.tech/contact\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\n"
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_2_AI_NATIVE_OPERATIONS.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_2_AI_NATIVE_OPERATIONS.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.PHASE_2_AI_NATIVE_OPERATIONS",
-	title: "Phase 2: AI-Native Operations",
-	summary: "_Last updated: 2025-11-20_",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/PHASE_2_AI_NATIVE_OPERATIONS",
-	tags: ["tech", "PHASE_2_AI_NATIVE_OPERATIONS"],
-	body: "# Phase 2: AI-Native Operations\n\n_Last updated: 2025-11-20_\n\nPhase 2 turns ContractSpec into an AI-first operations stack. The new libraries below are the building blocks used by support bots, growth agents, and human-in-the-loop flows.\n\n## Libraries\n\n### @lssm/lib.ai-agent\n\n- **Spec + Registry**: `defineAgent`, `AgentRegistry` keep agent definitions type-safe.\n- **Runner**: `AgentRunner` drives LLM conversations, tool calls, retries, escalation, and telemetry hooks.\n- **Tools**: `ToolExecutor` standardizes schema validation + timeouts.\n- **Memory**: `InMemoryAgentMemory` + interfaces for plugging persistent stores.\n- **Approvals**: new `ApprovalWorkflow` + `InMemoryApprovalStore` capture low-confidence decisions and surface them to reviewers.\n\n### @lssm/lib.support-bot\n\nComposable support automation primitives:\n\n- `TicketClassifier` → heuristics + optional LLM validation for category, priority, sentiment.\n- `TicketResolver` → RAG pipeline backed by knowledge spaces.\n- `AutoResponder` → tone-aware drafts with citations.\n- `SupportFeedbackLoop` → tracks resolution rates.\n- `createSupportTools` → ready-made tool definitions for AgentRunner.\n\n### @lssm/lib.content-gen\n\nContent generators that consume a `ContentBrief` and output production-ready assets:\n\n- `BlogGenerator`, `LandingPageGenerator`, `EmailCampaignGenerator`, `SocialPostGenerator`.\n- `SeoOptimizer` builds metadata + schema markup.\n\n### @lssm/lib.analytics\n\nQueryless analytics helpers:\n\n- `FunnelAnalyzer` – conversion/drop-off per step.\n- `CohortTracker` – retention + LTV per cohort.\n- `ChurnPredictor` – recency/frequency/error scoring.\n- `GrowthHypothesisGenerator` – surfaces experiment ideas from metric trends.\n\n### @lssm/lib.growth\n\nA/B testing toolkit:\n\n- `ExperimentRegistry` + `ExperimentRunner` – deterministic bucketing.\n- `ExperimentTracker` – persist exposures + metrics.\n- `StatsEngine` – Welch’s t-test + improvement calculations.\n\n### Human-in-the-loop UI\n\n`@lssm/lib.design-system` now exposes:\n\n- `ApprovalQueue` – list + act on pending approvals.\n- `AgentMonitor` – live view of agent sessions with confidence + status.\n\n## Examples\n\n- `examples/ai-support-bot/setup.ts` shows ticket classification → resolution → response draft.\n- `examples/content-generation/generate.ts` produces blog, landing, email, social, SEO output from one brief.\n\n## Next Steps\n\n1. Wire these libraries into vertical apps (H-Circle, ArtisanOS, etc.).\n2. Add background workers that consume the new analytics/growth trackers.\n3. Expand web-landing to highlight these Phase 2 capabilities (see separate TODO).\n"
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_3_AUTO_EVOLUTION.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_3_AUTO_EVOLUTION.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.PHASE_3_AUTO_EVOLUTION",
-	title: "Phase 3: Auto-Evolution Technical Notes",
-	summary: "**Status**: In progress",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/PHASE_3_AUTO_EVOLUTION",
-	tags: ["tech", "PHASE_3_AUTO_EVOLUTION"],
-	body: "# Phase 3: Auto-Evolution Technical Notes\n\n**Status**: In progress  \n**Last updated**: 2025-11-21  \n\nPhase 3 introduces self-learning capabilities that analyze production telemetry, suggest new specs, safely roll out variants, and generate golden tests from real traffic. This document captures the main building blocks delivered in this iteration.\n\n---\n\n## 1. Libraries\n\n### @lssm/lib.evolution\n\n- `SpecAnalyzer` converts raw telemetry samples into usage stats + anomalies.\n- `SpecGenerator` produces `SpecSuggestion` objects and validates confidence thresholds.\n- `SpecSuggestionOrchestrator` routes proposals through the AI approval workflow and writes approved specs to `packages/libs/contracts/src/generated`.\n- Storage adapters:\n  - `InMemorySpecSuggestionRepository` for tests.\n  - `PrismaSpecSuggestionRepository` persists to the new Prisma model (see §4).\n  - `FileSystemSuggestionWriter` emits JSON envelopes for git review.\n\n### @lssm/lib.observability\n\n- Added intent detection modules:\n  - `IntentAggregator` batches telemetry into rolling windows.\n  - `IntentDetector` surfaces latency/error/throughput regressions and sequential intents.\n- `EvolutionPipeline` orchestrates aggregation → detection → intent events and exposes hooks for downstream orchestrators.\n- `createTracingMiddleware` now accepts `resolveOperation`/`onSample` hooks to feed telemetry samples into the pipeline.\n\n### @lssm/lib.growth\n\n- New `spec-experiments` module:\n  - `SpecExperimentRegistry`, `SpecExperimentRunner`, `SpecExperimentAdapter`.\n  - `SpecExperimentAnalyzer` + `SpecExperimentController` handle guardrails and staged rollouts.\n  - Helper `createSpecVariantResolver` plugs directly into `HandlerCtx.specVariantResolver`.\n- `SpecVariantResolver` is now a first-class concept in `@lssm/lib.contracts`. The runtime will attempt to execute variant specs before falling back to the registered handler.\n\n### @lssm/lib.testing\n\n- `TrafficRecorder` + `TrafficStore` capture production requests with sampling and sanitization hooks.\n- `GoldenTestGenerator` converts `TrafficSnapshot`s into Vitest/Jest suites.\n- `generateVitestSuite` / `generateJestSuite` output self-contained test files, and `runGoldenTests` offers a programmatic harness for CI pipelines.\n\n---\n\n## 2. Telemetry → Intent → Spec Pipeline\n\n1. `createTracingMiddleware({ onSample })` emits `TelemetrySample`s for every HTTP request.\n2. `IntentAggregator` groups samples into statistical windows (default 15 minutes).\n3. `IntentDetector` raises signals for:\n   - Error spikes\n   - Latency regressions\n   - Throughput drops\n   - Sequential workflows that hint at missing specs\n4. `EvolutionPipeline` emits `intent.detected` events and hands them to `SpecGenerator`.\n5. `SpecSuggestionOrchestrator` persists suggestions, triggers approval workflows, and—upon approval—writes JSON envelopes to `packages/.../contracts/src/generated`.\n\n---\n\n## 3. Spec Experiments & Rollouts\n\n1. Register spec experiments in `SpecExperimentRegistry` with control + variant bindings.\n2. Expose bucketed specs by attaching `createSpecVariantResolver` to `HandlerCtx.specVariantResolver` inside adapters.\n3. Record outcomes via `SpecExperimentAdapter.trackOutcome()` (latency + error metrics).\n4. `SpecExperimentController` uses guardrails from config and `SpecExperimentAnalyzer` to:\n   - Auto-rollback on error/latency breaches.\n   - Advance rollout stages (1% → 10% → 50% → 100%) when metrics stay green.\n\n---\n\n## 4. Data Models (Prisma)\n\nFile: `packages/libs/database/prisma/schema.prisma`\n\n- `SpecSuggestion` – stores serialized suggestion payloads + statuses.\n- `IntentSnapshot` – captured detector output for auditing/training.\n- `TrafficSnapshot` – persisted production traffic (input/output/error blobs).\n- `SpecExperiment` / `SpecExperimentMetric` – rollout state + metrics for each variant.\n\n> Run `bun database generate` after pulling to refresh the Prisma client.\n\n---\n\n## 5. Golden Test Workflow\n\n1. Capture traffic via middleware or direct `TrafficRecorder.record`.\n2. Use the new CLI command to materialize suites:\n\n```bash\ncontractspec test generate \\\n  --operation billing.createInvoice \\\n  --output tests/billing.createInvoice.golden.test.ts \\\n  --runner-import ./tests/run-operation \\\n  --runner-fn runBillingCommand \\\n  --from-production \\\n  --days 7 \\\n  --sample-rate 0.05\n```\n\n3. Generated files import your runner and assert against recorded outputs (or expected errors for negative paths).\n\n---\n\n## 6. Operational Notes\n\n- **Approvals**: By default, every suggestion still requires human approval. `EvolutionConfig.autoApproveThreshold` can be tuned per environment but should remain conservative (<0.3) until OverlaySpec tooling lands.\n- **Sampling**: Keep `TrafficRecorder.sampleRate` ≤ 0.05 in production to avoid sensitive payload storage; scrub PII through the `sanitize` callback before persistence.\n- **Rollouts**: Guardrails default to 5% error-rate and 750ms P99 latency. Override per experiment to match SLOs.\n\n---\n\n## 7. Next Steps\n\n1. Wire `SpecExperimentAdapter.trackOutcome` into adapters (REST, GraphQL, Workers) so every execution logs metrics automatically.\n2. Add a UI for reviewing `SpecSuggestion` objects alongside approval status.\n3. Expand `TrafficRecorder` to ship directly to the Prisma-backed store (currently in-memory by default).\n4. Integrate `EvolutionPipeline` events with the Regenerator to close the loop (auto-open proposals + attach evidence).\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_4_PERSONALIZATION_ENGINE.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_4_PERSONALIZATION_ENGINE.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.PHASE_4_PERSONALIZATION_ENGINE",
-	title: "Phase 4: Personalization Engine",
-	summary: "**Status**: Complete",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/PHASE_4_PERSONALIZATION_ENGINE",
-	tags: ["tech", "PHASE_4_PERSONALIZATION_ENGINE"],
-	body: "# Phase 4: Personalization Engine\n\n**Status**: Complete  \n**Last updated**: 2025-11-21\n\nPhase 4 unlocks tenant-scoped personalization with zero bespoke code. We shipped three new libraries, a signing-aware Overlay editor, and the persistence layer required to observe usage and apply overlays safely.\n\n---\n\n## 1. Libraries\n\n### @lssm/lib.overlay-engine\n\n- OverlaySpec types + validator mirror the public spec.\n- Cryptographic signer (`ed25519`, `rsa-pss-sha256`) with canonical JSON serialization.\n- Registry that merges tenant/role/user/device overlays with predictable specificity.\n- React hooks (`useOverlay`, `useOverlayFields`) for client-side rendering.\n- Runtime engine audits every applied overlay for traceability.\n\n### @lssm/lib.personalization\n\n- Behavior tracker buffers field/feature/workflow events and exports OTel metrics.\n- Analyzer summarizes field usage and workflow drop-offs into actionable insights.\n- Adapter translates insights into overlay suggestions or workflow tweaks.\n- In-memory store implementation + interface for plugging Prisma/ClickHouse later.\n\n### @lssm/lib.workflow-composer\n\n- `WorkflowComposer` merges base workflows with tenant/role/device extensions.\n- Step injection utilities keep transitions intact and validate anchor steps.\n- Template helpers for common tenant review/approval, plus merge helpers for multi-scope extensions.\n\n---\n\n## 2. Overlay Editor App\n\nPath: `packages/apps/overlay-editor`\n\n- Next.js App Router UI for toggling field visibility, renaming labels, and reordering lists.\n- Live JSON preview powered by `defineOverlay`.\n- Server action that signs overlays via PEM private keys (Ed25519 by default) using the overlay engine signer.\n\n---\n\n## 3. Persistence\n\nAdded Prisma models (see `packages/libs/database/prisma/schema.prisma`):\n\n- `UserBehaviorEvent` – field/feature/workflow telemetry.\n- `OverlaySigningKey` – tenant managed signing keys with revocation timestamps.\n- `Overlay` – stored overlays (tenant/user/role/device scope) plus signature metadata.\n\n---\n\n## 4. Integration Steps\n\n1. Track usage inside apps via `createBehaviorTracker`.\n2. Periodically run `BehaviorAnalyzer.analyze` to generate insights.\n3. Convert insights into OverlaySpecs or Workflow extensions.\n4. Register tenant overlays in `OverlayRegistry` and serve via presentation runtimes.\n5. Compose workflows per tenant using `WorkflowComposer`.\n\nSee the `docs/tech/personalization/*` guides for concrete examples.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS.docblock.js

@@ -1,15 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.PHASE_5_ZERO_TOUCH_OPERATIONS",
-	title: "Phase 5: Zero-Touch Operations",
-	summary: "**Status**: In progress",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/PHASE_5_ZERO_TOUCH_OPERATIONS",
-	tags: ["tech", "PHASE_5_ZERO_TOUCH_OPERATIONS"],
-	body: "# Phase 5: Zero-Touch Operations\n\n**Status**: In progress  \n**Last updated**: 2025-11-21\n\nPhase 5 delivers progressive delivery, SLO intelligence, cost attribution, and anomaly-driven remediation so the platform can deploy continuously without pager rotations.\n\n---\n\n## 1. New Libraries\n\n### @lssm/lib.progressive-delivery\n- `DeploymentStrategy` types capture canary vs blue-green rollouts.\n- `CanaryController` + `CanaryAnalyzer` orchestrate stage evaluation against telemetry thresholds.\n- `TrafficShifter` keeps stable/candidate splits in sync with feature-flag or router state.\n- `DeploymentCoordinator` drives stage progression, emits events, and triggers rollbacks.\n- `RollbackManager` encapsulates safe revert hooks (spec version revert, traffic shift, etc.).\n\n### @lssm/lib.slo\n- Declarative `SLODefinition` with latency + availability targets per capability/spec.\n- `SLOTracker` stores rolling snapshots + error budget positions.\n- `BurnRateCalculator` implements multi-window burn computations (fast vs slow burn).\n- `SLOMonitor` pushes incidents to Ops tooling automatically when burn exceeds thresholds.\n\n### @lssm/lib.cost-tracking\n- `CostTracker` normalizes DB/API/compute metrics into per-operation cost totals.\n- `BudgetAlertManager` raises tenant budget warnings (80% default) with contextual payloads.\n- `OptimizationRecommender` suggests batching, caching, or contract tweaks to cut spend.\n\n### Observability Anomaly Toolkit\n- `BaselineCalculator` establishes rolling intent metrics (latency, error rate, throughput).\n- `AnomalyDetector` flags spikes/drops via relative deltas after 10+ samples.\n- `RootCauseAnalyzer` correlates anomalies with recent deployments.\n- `AlertManager` deduplicates notifications and feeds MCP/SRE transports.\n\n---\n\n## 2. Data Model Additions\n\nFile: `packages/libs/database/prisma/schema.prisma`\n\n| Model | Purpose |\n| --- | --- |\n| `SLODefinition`, `SLOSnapshot`, `ErrorBudget`, `SLOIncident` | Persist definitions, rolling windows, and incidents. |\n| `OperationCost`, `TenantBudget`, `CostAlert`, `OptimizationSuggestion` | Track per-operation costs, budgets, and generated recommendations. |\n| `Deployment`, `DeploymentStage`, `RollbackEvent` | Audit progressive delivery runs and automated rollbacks. |\n| `MetricBaseline`, `AnomalyEvent` | Store computed baselines and anomaly evidence for training/analytics. |\n\nRun `bun database generate` after pulling to refresh the Prisma client.\n\n---\n\n## 3. Operational Flow\n\n1. **Deploy**: Define a `DeploymentStrategy` and feed telemetry via `@lssm/lib.observability`. Canary stages run automatically.\n2. **Protect**: `CanaryAnalyzer` evaluates error rate + latency thresholds. Failures trigger `RollbackManager`.\n3. **Observe**: `SLOMonitor` consumes snapshots and opens incidents when burn rate exceeds thresholds.\n4. **Optimize**: `CostTracker` aggregates spend per tenant + capability, while `OptimizationRecommender` surfaces fixes.\n5. **Detect**: Anomaly signals route to `RootCauseAnalyzer`, which links them to specific deployments for auto-rollback.\n\n---\n\n## 4. Integration Checklist\n\n1. Instrument adapters with `createTracingMiddleware({ onSample })` to feed metric points into `AnomalyDetector`.\n2. Register SLOs per critical operation (`billing.charge`, `knowledge.search`) and wire monitors to Ops notifications.\n3. Attach `CostTracker.recordSample` to workflow runners (DB instrumentation + external call wrappers).\n4. Store deployment metadata using the new Prisma models for auditing + UI surfacing.\n5. Update `@lssm/app.ops-console` (next iteration) to list deployments, SLO status, costs, and anomalies in one timeline.\n\n---\n\n## 5. Next Steps\n\n- Wire `DeploymentCoordinator` into the Contracts CLI so `contractspec deploy` can run staged rollouts.\n- Add UI for SLO dashboards (burn rate sparkline + incident feed).\n- Ship budget suggestions into Growth Agent for automated cost optimizations.\n- Connect `AnomalyEvent` stream to MCP agents for root-cause playbooks.\n"
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/auth/better-auth-nextjs.docblock.js

@@ -1,79 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/auth/better-auth-nextjs.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.auth.better-auth-nextjs",
-	title: "Better Auth + Next.js integration (ContractSpec)",
-	summary: "How ContractSpec wires Better Auth into Next.js (server config, client singleton, and proxy cookie-only redirects).",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/auth/better-auth-nextjs",
-	tags: [
-		"auth",
-		"better-auth",
-		"nextjs",
-		"cookies",
-		"proxy",
-		"hmr"
-	],
-	body: `# Better Auth + Next.js integration (ContractSpec)
-
-This repo uses Better Auth as the primary auth layer (sessions, organizations, teams, API keys, and OAuth).
-
-## Server config (Better Auth)
-
-- Source: \`packages/bundles/contractspec-studio/src/application/services/auth.ts\`
-- Important: \`nextCookies()\` must be the **last** plugin in the Better Auth plugin list so \`Set-Cookie\` is applied correctly in Next.js environments.
-
-## Better Auth Admin plugin
-
-ContractSpec Studio enables the Better Auth **Admin plugin** to support platform-admin user operations (list users, impersonation, etc.).
-
-- Server: \`admin()\` plugin in \`packages/bundles/contractspec-studio/src/application/services/auth.ts\`
-- Client: \`adminClient()\` in \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.ts\`
-
-### PLATFORM_ADMIN ⇒ Better Auth admin role
-
-Better Auth Admin endpoints authorize via \`user.role\`. ContractSpec enforces an org-driven rule:
-
-- If the **active organization** has \`type = PLATFORM_ADMIN\`, the signed-in user is ensured to have \`User.role\` containing \`admin\`.
-- This is applied in the session creation hook and re-checked in \`assertsPlatformAdmin()\`.
-
-This keeps admin enablement deterministic and avoids manual role backfills.
-
-## Client config (React web + Expo)
-
-To avoid duplicate background refresh/polling loops in dev (Fast Refresh/HMR), the Better Auth client is implemented as a singleton cached on \`globalThis\`.
-
-- Web client: \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.ts\`
-- Native client: \`packages/bundles/contractspec-studio/src/presentation/providers/auth/client.native.ts\`
-
-Import guidance:
-
-- If you only need the context/hook, prefer importing from \`@lssm/bundle.contractspec-studio/presentation/providers/auth\`.
-- If you explicitly need the Better Auth client instance (e.g. admin impersonation, direct API calls), import from \`@lssm/bundle.contractspec-studio/presentation/providers/auth/client\`.
-
-## Public routes (login / signup)
-
-Public auth pages should avoid eager \`authClient\` initialization.
-
-Pattern used:
-
-- In the submit handler, dynamically import \`@lssm/bundle.contractspec-studio/presentation/providers/auth/index.web\` and call \`authClient.signIn.*\` / \`authClient.signUp.*\`.
-
-This prevents session refresh behavior from starting just because a public page rendered.
-
-## Next.js proxy auth (web-landing)
-
-The Next.js proxy/middleware is used for **redirect decisions only**. It must not perform DB-backed session reads on every request.
-
-- Source: \`packages/apps/web-landing/src/proxy.ts\`
-- Approach: cookie-only checks via Better Auth cookies helpers:
-  - \`getSessionCookie(request)\`
-  - \`getCookieCache(request)\`
-
-These checks are intentionally optimistic and should only gate routing. Full authorization must still be enforced on server-side actions/routes and GraphQL resolvers.
-`
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/contracts/openapi-export.docblock.js

@@ -1,56 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../../modules/audit-trail/dist/libs/contracts/dist/docs/tech/contracts/openapi-export.docblock.js
-registerDocBlocks([{
-	id: "docs.tech.contracts.openapi-export",
-	title: "OpenAPI export (OpenAPI 3.1) from SpecRegistry",
-	summary: "Generate a deterministic OpenAPI document from a SpecRegistry using jsonSchemaForSpec + REST transport metadata.",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/contracts/openapi-export",
-	tags: [
-		"contracts",
-		"openapi",
-		"rest"
-	],
-	body: `## OpenAPI export (OpenAPI 3.1) from SpecRegistry
-
-### Purpose
-
-ContractSpec specs can be exported into an **OpenAPI 3.1** document for tooling (SDK generation, docs, gateways).
-
-The export is **spec-first**:
-
-- Uses \`jsonSchemaForSpec(spec)\` for input/output JSON Schema (from SchemaModel → zod → JSON Schema)
-- Uses \`spec.transport.rest.method/path\` when present
-- Falls back to deterministic defaults:
-  - Method: \`POST\` for commands, \`GET\` for queries
-  - Path: \`defaultRestPath(name, version)\` → \`/<dot/name>/v<version>\`
-
-### Library API
-
-- Function: \`openApiForRegistry(registry, options?)\`
-- Location: \`@lssm/lib.contracts/openapi\`
-
-### CLI
-
-Export OpenAPI from a registry module:
-
-\`\`\`bash
-contractspec openapi --registry ./src/registry.ts --out ./openapi.json
-\`\`\`
-
-The registry module must export one of:
-
-- \`registry: SpecRegistry\`
-- \`default(): SpecRegistry | Promise<SpecRegistry>\`
-- \`createRegistry(): SpecRegistry | Promise<SpecRegistry>\`
-
-### Notes / limitations (current)
-
-- Responses are generated as a basic \`200\` response (plus schemas when available).
-- Query (GET) inputs are currently represented as a JSON request body when an input schema exists.
-- Errors are not yet expanded into OpenAPI responses; that will be added when we standardize error envelopes.`
-}]);
-
-//#endregion

package/dist/modules/audit-trail/dist/libs/contracts/dist/docs/tech/lifecycle-stage-system.docblock.js

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