4.0.18

managed-onboarding-experience-foundation

Release the Learning Journey managed onboarding, guided-tour, and mission foundation with fixture-backed platform, SpecialOps, and AI Ops proof scenarios.

quiet-learning-thread

Redesign the learning system around the adaptive journey runtime and repair shared learning sandbox presentation wiring.

Replace the old onboarding-centric learning contracts and local example progress logic with the canonical adaptive `learning.journey.*` runtime.

When: When consuming `@lssm-tech/module.learning-journey` contracts, track specs, or shared learning example progress helpers.

1. Update contract references from `learning.onboarding.*` to `learning.journey.*`.
2. Replace old onboarding/progress type imports with the new adaptive journey types and projected progress snapshots.
3. Remove any local learning track evaluators or progress stores that duplicate the module runtime.

Use the shared learning registry mapping/data helpers so supported learning sandbox templates resolve the shared presentation set consistently.

When: When extending sandbox/template support for additional learning examples.

1. Add the template to the learning registry template map and track lookup helpers.
2. Ensure the template’s presentation list uses the shared `learning.journey.*` keys only when the registry can provide matching data.
3. Register descriptor resolution and markdown rendering in `@lssm-tech/module.examples`.

Use module-owned onboarding/tour/mission definitions and fixture adapters instead of example-local state or example-to-example imports.

Packages: @lssm-tech/module.learning-journey

1. Import reusable onboarding contracts from the Learning Journey contracts surface once the additive public subpath is present.
2. Keep managed platform, SpecialOps, and AI Ops proof scenarios deterministic and credential-free.
3. Model AI Ops as an onboarding/tour/mission proof adapter only; do not expose complete sprint-product operations in default fixtures.
4. Keep Learning Journey core headless and adapter-port based; do not add direct dependencies on examples, AuthOS/CompanyOS modules, database integrations, graph UI packages, or personalized-presentation without a documented compatibility exception.
5. If a reference UI proof is added, verify it imports only libs/modules/bundles and never imports another example package.

The affected learning packages should be rebuilt and revalidated together because the runtime, examples, and sandbox wiring now depend on the same adaptive presentation/runtime surface.

Packages: @lssm-tech/module.learning-journey, @lssm-tech/module.examples, @lssm-tech/example.learning-journey-ambient-coach, @lssm-tech/example.learning-journey-crm-onboarding, @lssm-tech/example.learning-journey-duo-drills, @lssm-tech/example.learning-journey-platform-tour, @lssm-tech/example.learning-journey-quest-challenges, @lssm-tech/example.learning-journey-registry, @lssm-tech/example.learning-journey-studio-onboarding, @lssm-tech/example.learning-journey-ui-coaching, @lssm-tech/example.learning-journey-ui-gamified, @lssm-tech/example.learning-journey-ui-onboarding, @lssm-tech/example.learning-journey-ui-shared, @lssm-tech/example.learning-patterns

1. Run package-level build, test, typecheck, and lint checks for the affected learning packages.
2. Regenerate example registry artifacts if `@lssm-tech/module.examples` dependencies change.
3. Verify at least one supported learning sandbox route renders markdown successfully.