@contractspec/bundle.library 3.7.6 → 3.7.7

package/src/components/docs/ops/ops-runbooks-a.docblocks.ts

@@ -1,39 +1,39 @@
 import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
 
 export const opsRunbookDocsA: DocBlock[] = [
-  {
-    id: 'docs.ops.anomaly-detection.goal',
-    title: 'Anomaly detection goal',
-    summary: 'Why anomaly detection matters for ops stability.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/anomaly-detection/goal',
-    tags: ['ops', 'observability'],
-    body: 'Ensure anomalies are detected early to protect latency, error rate, and throughput SLAs; keep rollback hooks ready and audits reproducible.',
-  },
-  {
-    id: 'docs.ops.anomaly-detection.usage',
-    title: 'Anomaly detection usage guide',
-    summary: 'How to run and consume anomaly detection in operations.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/anomaly-detection/usage',
-    tags: ['ops', 'observability'],
-    body: `- Enable tracing middleware; emit latency/error/throughput samples.
+	{
+		id: 'docs.ops.anomaly-detection.goal',
+		title: 'Anomaly detection goal',
+		summary: 'Why anomaly detection matters for ops stability.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/anomaly-detection/goal',
+		tags: ['ops', 'observability'],
+		body: 'Ensure anomalies are detected early to protect latency, error rate, and throughput SLAs; keep rollback hooks ready and audits reproducible.',
+	},
+	{
+		id: 'docs.ops.anomaly-detection.usage',
+		title: 'Anomaly detection usage guide',
+		summary: 'How to run and consume anomaly detection in operations.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/anomaly-detection/usage',
+		tags: ['ops', 'observability'],
+		body: `- Enable tracing middleware; emit latency/error/throughput samples.
 - Configure thresholds per capability when bursty traffic exists.
 - Wire rollback hook in DeploymentCoordinator for error spikes.
 - Export anomaly JSON into incidents; update MetricBaseline post-fix.
 - Run chaos/load checks to validate signals within 30s.`,
-  },
-  {
-    id: 'docs.ops.anomaly-detection.how',
-    title: 'Anomaly detection runbook',
-    summary: 'Step-by-step runbook for anomaly signals and rollback hooks.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/anomaly-detection/how',
-    tags: ['ops', 'observability'],
-    body: `# Anomaly Detection Runbook
+	},
+	{
+		id: 'docs.ops.anomaly-detection.how',
+		title: 'Anomaly detection runbook',
+		summary: 'Step-by-step runbook for anomaly signals and rollback hooks.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/anomaly-detection/how',
+		tags: ['ops', 'observability'],
+		body: `# Anomaly Detection Runbook
 
 ## 1. Pipeline Overview
 1. \`createTracingMiddleware({ onSample })\` emits metric points (latency, errors, throughput).
@@ -61,40 +61,40 @@ export const opsRunbookDocsA: DocBlock[] = [
 ## 5. Testing
 - Use load test harness to inject latency and verify detector emits signals within 30 seconds.
 - Chaos suite should simulate upstream outages to ensure throughput-drop detection fires.`,
-  },
-  {
-    id: 'docs.ops.cost-optimization.goal',
-    title: 'Cost optimization goal',
-    summary: 'Keep spend predictable and actionable for ops and finance.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/cost-optimization/goal',
-    tags: ['ops', 'cost'],
-    body: 'Align telemetry, budgets, and rollback levers so cost spikes are detected early, communicated clearly, and mitigated without breaking SLAs.',
-  },
-  {
-    id: 'docs.ops.cost-optimization.usage',
-    title: 'Cost optimization usage guide',
-    summary: 'Quick checklist to run cost tracking and optimization.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/cost-optimization/usage',
-    tags: ['ops', 'cost'],
-    body: `- Emit \`CostSample\` via wrapped DB/HTTP clients; include provider/invoice cost.
+	},
+	{
+		id: 'docs.ops.cost-optimization.goal',
+		title: 'Cost optimization goal',
+		summary: 'Keep spend predictable and actionable for ops and finance.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/cost-optimization/goal',
+		tags: ['ops', 'cost'],
+		body: 'Align telemetry, budgets, and rollback levers so cost spikes are detected early, communicated clearly, and mitigated without breaking SLAs.',
+	},
+	{
+		id: 'docs.ops.cost-optimization.usage',
+		title: 'Cost optimization usage guide',
+		summary: 'Quick checklist to run cost tracking and optimization.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/cost-optimization/usage',
+		tags: ['ops', 'cost'],
+		body: `- Emit \`CostSample\` via wrapped DB/HTTP clients; include provider/invoice cost.
 - Batch into \`OperationCost\` every 5m; alert at 80% of monthlyLimit.
 - Nightly run \`OptimizationRecommender.generate\`; push tickets with evidence.
 - Use regional overrides for \`defaultCostModel\` when infra prices differ.
 - Send proactive alerts for ±20% deviations to enterprise tenants.`,
-  },
-  {
-    id: 'docs.ops.cost-optimization.how',
-    title: 'Cost optimization runbook',
-    summary: 'Step-by-step cost tracking, alerting, and communication.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/cost-optimization/how',
-    tags: ['ops', 'cost'],
-    body: `# Cost Tracking & Optimization Runbook
+	},
+	{
+		id: 'docs.ops.cost-optimization.how',
+		title: 'Cost optimization runbook',
+		summary: 'Step-by-step cost tracking, alerting, and communication.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/cost-optimization/how',
+		tags: ['ops', 'cost'],
+		body: `# Cost Tracking & Optimization Runbook
 
 ## 1. Instrumentation
 - Wrap DB client and HTTP adapters to emit \`CostSample\`s to \`CostTracker.recordSample\`.
@@ -117,5 +117,5 @@ export const opsRunbookDocsA: DocBlock[] = [
 ## 5. Customer Communication
 - For enterprise tenants offer proactive alerts when spend deviates ±20% from plan.
 - Connect \`TenantBudget\` alerts to CRM notes so Success teams see when automation saved costs.`,
-  },
+	},
 ];

package/src/components/docs/ops/ops-runbooks-b.docblocks.ts

@@ -1,39 +1,39 @@
 import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
 
 export const opsRunbookDocsB: DocBlock[] = [
-  {
-    id: 'docs.ops.profile-settings.goal',
-    title: 'Profile settings goal',
-    summary: 'Keep identity/profile flows reliable and debuggable.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/profile-settings/goal',
-    tags: ['ops', 'auth'],
-    body: 'Ensure profile linking/unlinking stays stable across FC+ and SMS flows, with clear monitoring and quick recovery steps.',
-  },
-  {
-    id: 'docs.ops.profile-settings.usage',
-    title: 'Profile settings usage guide',
-    summary: 'Quick checklist for profile settings operations.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/profile-settings/usage',
-    tags: ['ops', 'auth'],
-    body: `- Verify Better Auth config in \`src/lib/auth.ts\`; JWKS for FC+.
+	{
+		id: 'docs.ops.profile-settings.goal',
+		title: 'Profile settings goal',
+		summary: 'Keep identity/profile flows reliable and debuggable.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/profile-settings/goal',
+		tags: ['ops', 'auth'],
+		body: 'Ensure profile linking/unlinking stays stable across FC+ and SMS flows, with clear monitoring and quick recovery steps.',
+	},
+	{
+		id: 'docs.ops.profile-settings.usage',
+		title: 'Profile settings usage guide',
+		summary: 'Quick checklist for profile settings operations.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/profile-settings/usage',
+		tags: ['ops', 'auth'],
+		body: `- Verify Better Auth config in \`src/lib/auth.ts\`; JWKS for FC+.
 - Monitor Sentry spans \`profile.*\`; PostHog events connection_linked/unlinked.
 - On unlink failures: check \`/api/auth/connections/unlink\` logs.
 - FC+ issues: validate discovery URL and partner redirects.
 - OTP throttling: confirm SMS service rate limiter is active.`,
-  },
-  {
-    id: 'docs.ops.profile-settings.how',
-    title: 'Profile settings runbook',
-    summary: 'Detailed runbook for profile/settings operations.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/profile-settings/how',
-    tags: ['ops', 'auth'],
-    body: `## Runbook – Profile Settings
+	},
+	{
+		id: 'docs.ops.profile-settings.how',
+		title: 'Profile settings runbook',
+		summary: 'Detailed runbook for profile/settings operations.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/profile-settings/how',
+		tags: ['ops', 'auth'],
+		body: `## Runbook – Profile Settings
 
 ### Feature flags / Env
 
@@ -50,40 +50,40 @@ export const opsRunbookDocsB: DocBlock[] = [
 - Unlink failures → check \`/api/auth/connections/unlink\` logs
 - FC+ link issues → verify discovery URL and partner console redirects
 - Phone OTP rate limit → server-side limiter in SMS service`,
-  },
-  {
-    id: 'docs.ops.progressive-delivery.goal',
-    title: 'Progressive delivery goal',
-    summary: 'Roll out safely with fast rollback and clear guardrails.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/progressive-delivery/goal',
-    tags: ['ops', 'delivery'],
-    body: 'Use canary/blue-green with metrics guardrails so deployments can be halted or rolled back before customer impact.',
-  },
-  {
-    id: 'docs.ops.progressive-delivery.usage',
-    title: 'Progressive delivery usage guide',
-    summary: 'Quick checklist for canary/blue-green runs.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/progressive-delivery/usage',
-    tags: ['ops', 'delivery'],
-    body: `- Register \`DeploymentStrategy\`; wire telemetry via observability middleware.
+	},
+	{
+		id: 'docs.ops.progressive-delivery.goal',
+		title: 'Progressive delivery goal',
+		summary: 'Roll out safely with fast rollback and clear guardrails.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/progressive-delivery/goal',
+		tags: ['ops', 'delivery'],
+		body: 'Use canary/blue-green with metrics guardrails so deployments can be halted or rolled back before customer impact.',
+	},
+	{
+		id: 'docs.ops.progressive-delivery.usage',
+		title: 'Progressive delivery usage guide',
+		summary: 'Quick checklist for canary/blue-green runs.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/progressive-delivery/usage',
+		tags: ['ops', 'delivery'],
+		body: `- Register \`DeploymentStrategy\`; wire telemetry via observability middleware.
 - Define rollback actions (flag toggle/spec revert/infrastructure swap) in \`RollbackManager\`.
 - Use canary thresholds (err 1%, P99 500ms) or stricter per domain.
 - Pipe stage events to Ops Slack + Ops Console timeline.
 - For blue-green, run smoke tests before swap; freeze old env 24h post-swap.`,
-  },
-  {
-    id: 'docs.ops.progressive-delivery.how',
-    title: 'Progressive delivery runbook',
-    summary: 'Step-by-step for canary and blue-green rollouts.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/progressive-delivery/how',
-    tags: ['ops', 'delivery'],
-    body: `# Progressive Delivery Runbook
+	},
+	{
+		id: 'docs.ops.progressive-delivery.how',
+		title: 'Progressive delivery runbook',
+		summary: 'Step-by-step for canary and blue-green rollouts.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/progressive-delivery/how',
+		tags: ['ops', 'delivery'],
+		body: `# Progressive Delivery Runbook
 
 **Scope**: Contracts runtime deployments running on ContractSpec infrastructure.
 
@@ -128,5 +128,5 @@ thresholds: {
 - \`Deployment\`, \`DeploymentStage\`, and \`RollbackEvent\` tables store the full history.
 - Tag rollbacks with incident ID to keep Ops Console synchronized.
 - Auto-resolve the incident once \`status === 'completed'\` and SLO burn rate returns < 2x.`,
-  },
+	},
 ];

package/src/components/docs/ops/ops-slo-tenant.docblocks.ts

@@ -1,39 +1,39 @@
 import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
 
 export const opsSloTenantDocs: DocBlock[] = [
-  {
-    id: 'docs.ops.slo-management.goal',
-    title: 'SLO management goal',
-    summary: 'Keep availability/latency SLOs observable and enforceable.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/slo-management/goal',
-    tags: ['ops', 'slo'],
-    body: 'Ensure every capability has a versioned SLO with alerts, burn-rate workflows, and incident cross-links so rollbacks are justified and auditable.',
-  },
-  {
-    id: 'docs.ops.slo-management.usage',
-    title: 'SLO management usage guide',
-    summary: 'Quick checklist for defining and operating SLOs.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/slo-management/usage',
-    tags: ['ops', 'slo'],
-    body: `- Define \`SLODefinition\` per capability; tag tenant/tier for filtering.
+	{
+		id: 'docs.ops.slo-management.goal',
+		title: 'SLO management goal',
+		summary: 'Keep availability/latency SLOs observable and enforceable.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/slo-management/goal',
+		tags: ['ops', 'slo'],
+		body: 'Ensure every capability has a versioned SLO with alerts, burn-rate workflows, and incident cross-links so rollbacks are justified and auditable.',
+	},
+	{
+		id: 'docs.ops.slo-management.usage',
+		title: 'SLO management usage guide',
+		summary: 'Quick checklist for defining and operating SLOs.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/slo-management/usage',
+		tags: ['ops', 'slo'],
+		body: `- Define \`SLODefinition\` per capability; tag tenant/tier for filtering.
 - Deploy \`SLOMonitor\`; pipe incidents to PagerDuty + Ops Slack.
 - Fast burn 14x -> page; slow burn 6x -> create ticket.
 - Use \`SLOSnapshot\` for dashboards; include deployment IDs in incidents.
 - Reset or advance error budgets after resolution when appropriate.`,
-  },
-  {
-    id: 'docs.ops.slo-management.how',
-    title: 'SLO management runbook',
-    summary: 'Detailed runbook for SLO lifecycle and incident handling.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/slo-management/how',
-    tags: ['ops', 'slo'],
-    body: `# SLO Management Runbook
+	},
+	{
+		id: 'docs.ops.slo-management.how',
+		title: 'SLO management runbook',
+		summary: 'Detailed runbook for SLO lifecycle and incident handling.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/slo-management/how',
+		tags: ['ops', 'slo'],
+		body: `# SLO Management Runbook
 
 ## 1. Definition Lifecycle
 1. Create an entry in \`SLODefinition\` via migration or the Ops Console.
@@ -66,41 +66,41 @@ monitor.recordWindow({ good, bad, latencyP99, latencyP95 });
 ## 5. Reporting
 - Weekly summary = AVG burn rate, # incidents, # auto-rollbacks triggered by SLO monitor.
 - Feed \`SLOIncident\` into Growth Agent for customer comms when SLAs impact tenants.`,
-  },
-  {
-    id: 'docs.ops.tenant-customization.goal',
-    title: 'Tenant customization goal',
-    summary:
-      'Let tenants customize overlays/workflows safely with audit and rollback.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops/tenant-customization/goal',
-    tags: ['ops', 'tenant'],
-    body: 'Provide controlled overlays and workflow extensions per tenant with signed assets, versioning, and observability so UI/flow tweaks stay safe and reversible.',
-  },
-  {
-    id: 'docs.ops.tenant-customization.usage',
-    title: 'Tenant customization usage guide',
-    summary: 'Quick steps for onboarding a tenant customization.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/ops/tenant-customization/usage',
-    tags: ['ops', 'tenant'],
-    body: `- Capture fields to hide/rename and workflow deviations.
+	},
+	{
+		id: 'docs.ops.tenant-customization.goal',
+		title: 'Tenant customization goal',
+		summary:
+			'Let tenants customize overlays/workflows safely with audit and rollback.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops/tenant-customization/goal',
+		tags: ['ops', 'tenant'],
+		body: 'Provide controlled overlays and workflow extensions per tenant with signed assets, versioning, and observability so UI/flow tweaks stay safe and reversible.',
+	},
+	{
+		id: 'docs.ops.tenant-customization.usage',
+		title: 'Tenant customization usage guide',
+		summary: 'Quick steps for onboarding a tenant customization.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/ops/tenant-customization/usage',
+		tags: ['ops', 'tenant'],
+		body: `- Capture fields to hide/rename and workflow deviations.
 - Build overlay in overlay editor; sign JSON with tenant key.
 - Persist in \`Overlay\` table; register via \`OverlayRegistry\` or admin API.
 - Compose \`WorkflowExtension\`; store alongside overlay metadata.
 - Run sandbox smoke tests; ensure audit logs capture overlay events.`,
-  },
-  {
-    id: 'docs.ops.tenant-customization.how',
-    title: 'Tenant customization runbook',
-    summary: 'Detailed runbook for overlays and workflow extensions.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/ops/tenant-customization/how',
-    tags: ['ops', 'tenant'],
-    body: `# Tenant Customization Runbook
+	},
+	{
+		id: 'docs.ops.tenant-customization.how',
+		title: 'Tenant customization runbook',
+		summary: 'Detailed runbook for overlays and workflow extensions.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/ops/tenant-customization/how',
+		tags: ['ops', 'tenant'],
+		body: `# Tenant Customization Runbook
 
 Phase 4 introduces managed overlays and workflow extensions. Ops teams should follow this flow when onboarding a tenant that requests UI tweaks or workflow changes.
 
@@ -141,5 +141,5 @@ Managed tenants can override lifecycle playbooks without touching database schem
    - Subscribe to \`LifecycleKpiPipeline\` events (see \`@contractspec/bundle.lifecycle-managed\`) to forward stage changes into tenant-specific analytics.
 
 All lifecycle overrides must be versioned alongside the tenant’s overlay and workflow extensions so ops can rollback safely.`,
-  },
+	},
 ];

package/src/components/docs/ops/ops-top.docs.ts

@@ -1,15 +1,15 @@
 import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
 
 export const opsTopDocs: DocBlock[] = [
-  {
-    id: 'docs.ops.index',
-    title: 'Operations docs index',
-    summary: 'Entry point for operations runbooks and guides.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/ops',
-    tags: ['ops'],
-    body: `# Operations
+	{
+		id: 'docs.ops.index',
+		title: 'Operations docs index',
+		summary: 'Entry point for operations runbooks and guides.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/ops',
+		tags: ['ops'],
+		body: `# Operations
 
 Browse runbooks and guides for ops workflows:
 - Anomaly detection (goal/usage/how)
@@ -19,5 +19,5 @@ Browse runbooks and guides for ops workflows:
 - Progressive delivery (goal/usage/how)
 - SLO management (goal/usage/how)
 - Tenant customization (goal/usage/how)`,
-  },
+	},
 ];

package/src/components/docs/ops/ops.docs.ts

@@ -1,14 +1,14 @@
 import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
-import { opsRunbookDocsA } from './ops-runbooks-a.docblocks';
 import { opsLifecycleDocs } from './ops-lifecycle.docblocks';
+import { opsRunbookDocsA } from './ops-runbooks-a.docblocks';
 import { opsRunbookDocsB } from './ops-runbooks-b.docblocks';
 import { opsSloTenantDocs } from './ops-slo-tenant.docblocks';
 import { opsTopDocs } from './ops-top.docs';
 
 export const opsDocBlocks: DocBlock[] = [
-  ...opsTopDocs,
-  ...opsRunbookDocsA,
-  ...opsLifecycleDocs,
-  ...opsRunbookDocsB,
-  ...opsSloTenantDocs,
+	...opsTopDocs,
+	...opsRunbookDocsA,
+	...opsLifecycleDocs,
+	...opsRunbookDocsB,
+	...opsSloTenantDocs,
 ];

package/src/components/docs/product/product.docblocks.ts

@@ -2,75 +2,75 @@ import type { DocBlock } from '@contractspec/lib.contracts-spec/docs';
 import { registerDocBlocks } from '@contractspec/lib.contracts-spec/docs';
 
 export const productDocs: DocBlock[] = [
-  {
-    id: 'docs.product.lifecycle-stages.goal',
-    title: 'Lifecycle stages goal',
-    summary: 'Why lifecycle staging exists for ContractSpec products.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-stages/goal',
-    tags: ['product', 'lifecycle'],
-    body: 'Provide a clear, staged journey so teams can adopt ContractSpec incrementally with measurable milestones and ceremonies.',
-  },
-  {
-    id: 'docs.product.lifecycle-stages.usage',
-    title: 'Lifecycle stages usage',
-    summary: 'How to use lifecycle stages across products.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-stages/usage',
-    tags: ['product', 'lifecycle'],
-    body: `- Map tenant or project to a lifecycle stage using assessment signals.
+	{
+		id: 'docs.product.lifecycle-stages.goal',
+		title: 'Lifecycle stages goal',
+		summary: 'Why lifecycle staging exists for ContractSpec products.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-stages/goal',
+		tags: ['product', 'lifecycle'],
+		body: 'Provide a clear, staged journey so teams can adopt ContractSpec incrementally with measurable milestones and ceremonies.',
+	},
+	{
+		id: 'docs.product.lifecycle-stages.usage',
+		title: 'Lifecycle stages usage',
+		summary: 'How to use lifecycle stages across products.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-stages/usage',
+		tags: ['product', 'lifecycle'],
+		body: `- Map tenant or project to a lifecycle stage using assessment signals.
 - Use stage checklists to guide adoption; trigger ceremonies on stage change.
 - Keep stage definitions versioned and referenced by UI and ops docs.
 - Align product messaging to the current stage for clarity and expectation setting.`,
-  },
-  {
-    id: 'docs.product.lifecycle-stages.how',
-    title: 'Lifecycle stages reference',
-    summary: 'Reference of lifecycle stages and guidance (from markdown).',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-stages/how',
-    tags: ['product', 'lifecycle'],
-    body: `# Lifecycle Stages
+	},
+	{
+		id: 'docs.product.lifecycle-stages.how',
+		title: 'Lifecycle stages reference',
+		summary: 'Reference of lifecycle stages and guidance (from markdown).',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-stages/how',
+		tags: ['product', 'lifecycle'],
+		body: `# Lifecycle Stages
 
 Refer to lifecycle stages definition and guidance in product docs. Keep stage names, descriptions, and ceremonies aligned with implementation and ops runbooks.`,
-  },
-  {
-    id: 'docs.product.lifecycle-user-guide.goal',
-    title: 'Lifecycle user guide goal',
-    summary: 'Why the lifecycle user guide exists.',
-    kind: 'goal',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-user-guide/goal',
-    tags: ['product', 'lifecycle'],
-    body: 'Help users navigate lifecycle assessments, recommendations, and ceremonies without requiring ops intervention.',
-  },
-  {
-    id: 'docs.product.lifecycle-user-guide.usage',
-    title: 'Lifecycle user guide usage',
-    summary: 'How users should follow lifecycle guidance.',
-    kind: 'usage',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-user-guide/usage',
-    tags: ['product', 'lifecycle'],
-    body: `- Review recommended actions after each assessment.
+	},
+	{
+		id: 'docs.product.lifecycle-user-guide.goal',
+		title: 'Lifecycle user guide goal',
+		summary: 'Why the lifecycle user guide exists.',
+		kind: 'goal',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-user-guide/goal',
+		tags: ['product', 'lifecycle'],
+		body: 'Help users navigate lifecycle assessments, recommendations, and ceremonies without requiring ops intervention.',
+	},
+	{
+		id: 'docs.product.lifecycle-user-guide.usage',
+		title: 'Lifecycle user guide usage',
+		summary: 'How users should follow lifecycle guidance.',
+		kind: 'usage',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-user-guide/usage',
+		tags: ['product', 'lifecycle'],
+		body: `- Review recommended actions after each assessment.
 - Complete milestone checklists to progress stages.
 - Acknowledge stage regressions and follow suggested remediation.
 - Use the Studio UI to trigger reassessments when major changes occur.`,
-  },
-  {
-    id: 'docs.product.lifecycle-user-guide.how',
-    title: 'Lifecycle user guide reference',
-    summary: 'Reference content for lifecycle user guide.',
-    kind: 'how',
-    visibility: 'public',
-    route: '/docs/product/lifecycle-user-guide/how',
-    tags: ['product', 'lifecycle'],
-    body: `# Lifecycle User Guide
+	},
+	{
+		id: 'docs.product.lifecycle-user-guide.how',
+		title: 'Lifecycle user guide reference',
+		summary: 'Reference content for lifecycle user guide.',
+		kind: 'how',
+		visibility: 'public',
+		route: '/docs/product/lifecycle-user-guide/how',
+		tags: ['product', 'lifecycle'],
+		body: `# Lifecycle User Guide
 
 User-facing guide for navigating lifecycle assessments, recommendations, and ceremonies. Keep aligned with runtime logic and ops runbooks.`,
-  },
+	},
 ];
 registerDocBlocks(productDocs);