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

package/dist/libs/contracts/dist/docs/tech/vscode-extension.docblock.js

@@ -1,101 +0,0 @@
-import { registerDocBlocks } from "../registry.js";
-
-//#region ../../libs/contracts/dist/docs/tech/vscode-extension.docblock.js
-const tech_vscode_extension_DocBlocks = [{
-	id: "docs.tech.vscode.extension",
-	title: "ContractSpec VS Code Extension",
-	summary: "VS Code extension for spec-first development with validation, scaffolding, and MCP integration.",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/vscode/extension",
-	tags: [
-		"vscode",
-		"extension",
-		"tooling",
-		"dx"
-	],
-	body: `# ContractSpec VS Code Extension
-
-The ContractSpec VS Code extension provides spec-first development tooling directly in your editor.
-
-## Features
-
-- **Real-time Validation**: Get instant feedback on spec errors and warnings as you save files
-- **Build/Scaffold**: Generate handler and component skeletons from specs (no AI required)
-- **Spec Explorer**: List and navigate all specs in your workspace
-- **Dependency Analysis**: Visualize spec dependencies and detect cycles
-- **MCP Integration**: Search ContractSpec documentation via Model Context Protocol
-- **Snippets**: Code snippets for common ContractSpec patterns
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| \`ContractSpec: Validate Current Spec\` | Validate the currently open spec file |
-| \`ContractSpec: Validate All Specs\` | Validate all spec files in the workspace |
-| \`ContractSpec: Build/Scaffold\` | Generate handler/component from the current spec |
-| \`ContractSpec: List All Specs\` | Show all specs in the workspace |
-| \`ContractSpec: Analyze Dependencies\` | Analyze and visualize spec dependencies |
-| \`ContractSpec: Search Docs (MCP)\` | Search documentation via MCP |
-
-## Configuration
-
-| Setting | Description | Default |
-|---------|-------------|---------|
-| \`contractspec.api.baseUrl\` | Base URL for ContractSpec API (enables MCP + remote telemetry) | \`""\` |
-| \`contractspec.telemetry.posthogHost\` | PostHog host URL for direct telemetry | \`"https://eu.posthog.com"\` |
-| \`contractspec.telemetry.posthogProjectKey\` | PostHog project key for direct telemetry | \`""\` |
-| \`contractspec.validation.onSave\` | Run validation on save | \`true\` |
-| \`contractspec.validation.onOpen\` | Run validation on open | \`true\` |
-
-## Architecture
-
-The extension uses:
-- \`@lssm/module.contractspec-workspace\` for pure analysis + templates
-- \`@lssm/bundle.contractspec-workspace\` for workspace services + adapters
-
-This allows the extension to work without requiring the CLI to be installed.
-
-## Telemetry
-
-The extension uses a hybrid telemetry approach:
-1. If \`contractspec.api.baseUrl\` is configured → send to API \`/api/telemetry/ingest\`
-2. Otherwise → send directly to PostHog (if project key configured)
-
-Telemetry respects VS Code's telemetry settings. No file paths, source code, or PII is collected.
-`
-}, {
-	id: "docs.tech.vscode.snippets",
-	title: "ContractSpec Snippets",
-	summary: "Code snippets for common ContractSpec patterns in VS Code.",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/vscode/snippets",
-	tags: [
-		"vscode",
-		"snippets",
-		"dx"
-	],
-	body: `# ContractSpec Snippets
-
-The VS Code extension includes snippets for common ContractSpec patterns.
-
-## Available Snippets
-
-| Prefix | Description |
-|--------|-------------|
-| \`contractspec-command\` | Create a new command (write operation) |
-| \`contractspec-query\` | Create a new query (read-only operation) |
-| \`contractspec-event\` | Create a new event |
-| \`contractspec-docblock\` | Create a new DocBlock |
-| \`contractspec-telemetry\` | Create a new TelemetrySpec |
-| \`contractspec-presentation\` | Create a new Presentation |
-
-## Usage
-
-Type the prefix in a TypeScript file and press Tab to expand the snippet. Tab through the placeholders to fill in your values.
-`
-}];
-registerDocBlocks(tech_vscode_extension_DocBlocks);
-
-//#endregion

package/dist/libs/contracts/dist/docs/tech/workflows/overview.docblock.js

@@ -1,20 +0,0 @@
-import { registerDocBlocks } from "../../registry.js";
-
-//#region ../../libs/contracts/dist/docs/tech/workflows/overview.docblock.js
-const tech_workflows_overview_DocBlocks = [{
-	id: "docs.tech.workflows.overview",
-	title: "WorkflowSpec Overview",
-	summary: "WorkflowSpec provides a declarative, versioned format for long-running flows that mix automation and human review. Specs stay inside `@lssm/lib.contracts` (`src/workflow/spec.ts`) so the same definition powers runtime execution, documentation, and future generation.",
-	kind: "reference",
-	visibility: "public",
-	route: "/docs/tech/workflows/overview",
-	tags: [
-		"tech",
-		"workflows",
-		"overview"
-	],
-	body: "# WorkflowSpec Overview\n\n## Purpose\n\nWorkflowSpec provides a declarative, versioned format for long-running flows that mix automation and human review. Specs stay inside `@lssm/lib.contracts` (`src/workflow/spec.ts`) so the same definition powers runtime execution, documentation, and future generation.\n\n## Core Types\n\n- `WorkflowMeta`: ownership metadata (`title`, `domain`, `owners`, `tags`, `stability`) plus `name` and `version`.\n- `WorkflowDefinition`:\n  - `entryStepId?`: optional explicit entry point (defaults to first step).\n  - `steps[]`: ordered list of `Step` descriptors.\n  - `transitions[]`: directed edges between steps with optional expressions.\n  - `sla?`: aggregated timing hints for the overall flow or per-step budgets.\n  - `compensation?`: fallback operations executed when a workflow is rolled back or fails.\n- `Step`:\n  - `type`: `human`, `automation`, or `decision`.\n  - `action`: references either a `ContractSpec` (`operation`) or `FormSpec` (`form`).\n  - Optional `guard`, `timeoutMs`, and retry policy (`maxAttempts`, `backoff`, `delayMs`, `maxDelayMs?`).\n  - `requiredIntegrations?`: integration slot ids that must be bound before the step may execute.\n  - `requiredCapabilities?`: `CapabilityRef[]` that must be enabled in the resolved app config.\n- `Transition`: `from` → `to` with optional `condition` string (simple data expressions).\n\n## Registry & Validation\n\n- `WorkflowRegistry` (`src/workflow/spec.ts`) stores specs by key `<name>.v<version>` and exposes `register`, `list`, and `get`.\n- `validateWorkflowSpec()` (`src/workflow/validation.ts`) checks:\n  - Duplicate step IDs.\n  - Unknown `from`/`to` transitions.\n  - Empty guards/conditions.\n  - Reachability from the entry step.\n  - Cycles in the graph.\n  - Operation/Form references against provided registries.\n- `assertWorkflowSpecValid()` wraps validation and throws `WorkflowValidationError` when errors remain.\n\n## Runtime\n\n- `WorkflowRunner` (`src/workflow/runner.ts`) executes workflows and coordinates steps.\n  - `start(name, version?, initialData?)` returns a `workflowId`.\n  - `executeStep(workflowId, input?)` runs the current step (automation or human).\n  - `getState(workflowId)` retrieves the latest state snapshot.\n  - `cancel(workflowId)` marks the workflow as cancelled.\n  - `preFlightCheck(name, version?, resolvedConfig?)` evaluates integration/capability requirements before the workflow starts.\n  - Throws `WorkflowPreFlightError` if required integration slots are unbound or required capabilities are disabled.\n- `StateStore` (`src/workflow/state.ts`) abstracts persistence. V1 ships with:\n  - `InMemoryStateStore` (`src/workflow/adapters/memory-store.ts`) for tests/dev.\n  - Placeholder factories for file/database adapters (`adapters/file-adapter.ts`, `adapters/db-adapter.ts`).\n- Guard evaluation: expression guards run through `evaluateExpression()` (`src/workflow/expression.ts`); custom policy guards can be provided via `guardEvaluator`.\n- Events: the runner emits `workflow.started`, `workflow.step_completed`, `workflow.step_failed`, and `workflow.cancelled` through the optional `eventEmitter`.\n- React bindings (`@lssm/lib.presentation-runtime-react`):\n  - `useWorkflow` hook (polls state, exposes `executeStep`, `cancel`, `refresh`).\n  - `WorkflowStepper` progress indicator using design-system Stepper.\n  - `WorkflowStepRenderer` helper to render human/automation/decision steps with sensible fallbacks.\n\n## Authoring Checklist\n\n1. Reuse existing operations/forms; create new specs when missing.\n2. Prefer explicit `entryStepId` for clarity (especially with decision branches).\n3. Give automation steps an `operation` and human steps a `form` (warnings surface otherwise).\n4. Use short, meaningful step IDs (`submit`, `review`, `finalize`) to simplify analytics.\n5. Keep guard expressions deterministic; complex policy logic should move to PolicySpec (Phase 2).\n\n## Testing\n\n- Add unit tests for new workflows via `assertWorkflowSpecValid`.\n- Use the new Vitest suites (`validation.test.ts`, `expression.test.ts`, `runner.test.ts`) as examples.\n- CLI support will arrive in Phase 1 PR 3 (`contractspec create --type workflow`).\n\n## Tooling\n\n- `contractspec create --type workflow` scaffolds a WorkflowSpec with interactive prompts.\n- `contractspec build <spec.workflow.ts>` generates a runner scaffold (`.runner.ts`) wired to `WorkflowRunner` and the in-memory store.\n- `contractspec validate` understands `.workflow.ts` files and checks core structure (meta, steps, transitions).\n\n## Next Steps (Non-MVP)\n\n- Persistence adapters (database/file) for workflow state (Phase 2).\n- React bindings (`useWorkflow`, `WorkflowStepper`) and presentation-runtime integration (PR 3).\n- Policy engine integration (`guard.type === 'policy'` validated against PolicySpec).\n- Telemetry hooks for step execution metrics.\n\n"
-}];
-registerDocBlocks(tech_workflows_overview_DocBlocks);
-
-//#endregion

package/dist/presentations/index.d.ts

@@ -1,9 +0,0 @@
-import { PresentationDescriptorV2 } from "@lssm/lib.contracts";
-
-//#region src/presentations/index.d.ts
-declare const LearningTrackListPresentation: PresentationDescriptorV2;
-declare const LearningTrackDetailPresentation: PresentationDescriptorV2;
-declare const LearningTrackProgressWidgetPresentation: PresentationDescriptorV2;
-declare const learningJourneyPresentations: PresentationDescriptorV2[];
-//#endregion
-export { LearningTrackDetailPresentation, LearningTrackListPresentation, LearningTrackProgressWidgetPresentation, learningJourneyPresentations };

package/dist/progress-store.d.ts

@@ -1,10 +0,0 @@
-import { TrackProgress } from "./api-types.js";
-import { LearningJourneyTrackSpec } from "@lssm/module.learning-journey/track-spec";
-
-//#region src/progress-store.d.ts
-declare const progressStore: Map<string, Map<string, TrackProgress>>;
-declare const getTrackResolver: (tracks: LearningJourneyTrackSpec[]) => (trackId: string) => LearningJourneyTrackSpec | undefined;
-declare const getLearnerTracks: (learnerId: string) => Map<string, TrackProgress>;
-declare const initProgress: (learnerId: string, track: LearningJourneyTrackSpec) => TrackProgress;
-//#endregion
-export { getLearnerTracks, getTrackResolver, initProgress, progressStore };

package/dist/tracks.d.ts

@@ -1,39 +0,0 @@
-import { LearningJourneyStepSpec, LearningJourneyTrackSpec, StepAvailabilitySpec, StepCompletionConditionSpec } from "@lssm/module.learning-journey/track-spec";
-import { crmLearningTracks } from "@lssm/example.learning-journey-crm-onboarding/track";
-import { platformLearningTracks } from "@lssm/example.learning-journey-platform-tour/track";
-import { studioLearningTracks } from "@lssm/example.learning-journey-studio-onboarding/track";
-
-//#region src/tracks.d.ts
-interface OnboardingStepDto {
-  id: string;
-  title: string;
-  description?: string;
-  completionEvent: string;
-  completionCondition?: StepCompletionConditionSpec;
-  xpReward?: number;
-  isRequired?: boolean;
-  canSkip?: boolean;
-  actionUrl?: string;
-  actionLabel?: string;
-  availability?: StepAvailabilitySpec;
-  metadata?: Record<string, unknown>;
-}
-interface OnboardingTrackDto {
-  id: string;
-  name: string;
-  description?: string;
-  productId?: string;
-  targetUserSegment?: string;
-  targetRole?: string;
-  totalXp?: number;
-  streakRule?: LearningJourneyTrackSpec['streakRule'];
-  completionRewards?: LearningJourneyTrackSpec['completionRewards'];
-  steps: OnboardingStepDto[];
-  metadata?: Record<string, unknown>;
-}
-declare const mapStep: (step: LearningJourneyStepSpec) => OnboardingStepDto;
-declare const mapTrackSpecToDto: (track: LearningJourneyTrackSpec) => OnboardingTrackDto;
-declare const learningJourneyTracks: LearningJourneyTrackSpec[];
-declare const onboardingTrackCatalog: OnboardingTrackDto[];
-//#endregion
-export { OnboardingStepDto, OnboardingTrackDto, crmLearningTracks, learningJourneyTracks, mapStep, mapTrackSpecToDto, onboardingTrackCatalog, platformLearningTracks, studioLearningTracks };

package/dist/ui/LearningMiniApp.d.ts

@@ -1,23 +0,0 @@
-import * as react_jsx_runtime0 from "react/jsx-runtime";
-import { LearningView } from "@lssm/example.learning-journey-ui-shared";
-
-//#region src/ui/LearningMiniApp.d.ts
-/** Template IDs that map to learning journey tracks */
-type LearningTemplateId = 'learning-journey-duo-drills' | 'learning-journey-quest-challenges' | 'learning-journey-studio-onboarding' | 'learning-journey-platform-tour' | 'learning-journey-ambient-coach' | 'learning-journey-crm-onboarding';
-interface LearningMiniAppProps {
-  templateId: string;
-  initialView?: LearningView;
-  onViewChange?: (view: LearningView) => void;
-}
-/** Router component that picks the correct mini-app based on template ID */
-declare function LearningMiniApp({
-  templateId,
-  initialView,
-  onViewChange
-}: LearningMiniAppProps): react_jsx_runtime0.JSX.Element;
-/** Check if a template ID is a learning journey template */
-declare function isLearningTemplate(templateId: string): templateId is LearningTemplateId;
-/** Get all learning template IDs */
-declare function getLearningTemplateIds(): LearningTemplateId[];
-//#endregion
-export { LearningMiniApp, getLearningTemplateIds, isLearningTemplate };

package/dist/ui/index.d.ts

@@ -1,2 +0,0 @@
-import { LearningMiniApp, getLearningTemplateIds, isLearningTemplate } from "./LearningMiniApp.js";
-export { LearningMiniApp, getLearningTemplateIds, isLearningTemplate };