@lssm/example.learning-journey-studio-onboarding 0.0.0-canary-20251217063201 → 0.0.0-canary-20251217072406

package/dist/learning-journey-studio-onboarding.feature.js

@@ -1 +1,66 @@
-const e={meta:{key:`learning-journey-studio-onboarding`,title:`Learning Journey: Studio Onboarding`,description:`Studio onboarding journey for getting started with ContractSpec Studio`,domain:`learning-journey`,owners:[`@examples.learning-journey.studio-onboarding`],tags:[`learning`,`onboarding`,`studio`,`journey`],stability:`experimental`},operations:[{name:`learningJourney.studioOnboarding.recordEvent`,version:1},{name:`learningJourney.studioOnboarding.getTrack`,version:1}],events:[],presentations:[{name:`learning.journey.studio.track`,version:1},{name:`learning.journey.studio.widget`,version:1}],opToPresentation:[{op:{name:`learningJourney.studioOnboarding.getTrack`,version:1},pres:{name:`learning.journey.studio.track`,version:1}}],presentationsTargets:[{name:`learning.journey.studio.track`,version:1,targets:[`react`,`markdown`,`application/json`]},{name:`learning.journey.studio.widget`,version:1,targets:[`react`]}],capabilities:{requires:[{key:`identity`,version:1}]}};export{e as LearningJourneyStudioOnboardingFeature};
+//#region src/learning-journey-studio-onboarding.feature.ts
+/**
+* Learning Journey Studio Onboarding feature module that bundles
+* Studio-specific onboarding track operations and presentations.
+*/
+const LearningJourneyStudioOnboardingFeature = {
+	meta: {
+		key: "learning-journey-studio-onboarding",
+		title: "Learning Journey: Studio Onboarding",
+		description: "Studio onboarding journey for getting started with ContractSpec Studio",
+		domain: "learning-journey",
+		owners: ["@examples.learning-journey.studio-onboarding"],
+		tags: [
+			"learning",
+			"onboarding",
+			"studio",
+			"journey"
+		],
+		stability: "experimental"
+	},
+	operations: [{
+		name: "learningJourney.studioOnboarding.recordEvent",
+		version: 1
+	}, {
+		name: "learningJourney.studioOnboarding.getTrack",
+		version: 1
+	}],
+	events: [],
+	presentations: [{
+		name: "learning.journey.studio.track",
+		version: 1
+	}, {
+		name: "learning.journey.studio.widget",
+		version: 1
+	}],
+	opToPresentation: [{
+		op: {
+			name: "learningJourney.studioOnboarding.getTrack",
+			version: 1
+		},
+		pres: {
+			name: "learning.journey.studio.track",
+			version: 1
+		}
+	}],
+	presentationsTargets: [{
+		name: "learning.journey.studio.track",
+		version: 1,
+		targets: [
+			"react",
+			"markdown",
+			"application/json"
+		]
+	}, {
+		name: "learning.journey.studio.widget",
+		version: 1,
+		targets: ["react"]
+	}],
+	capabilities: { requires: [{
+		key: "identity",
+		version: 1
+	}] }
+};
+
+//#endregion
+export { LearningJourneyStudioOnboardingFeature };

package/dist/libs/contracts/dist/capabilities/openbanking.js

@@ -1 +1,88 @@
-import{e}from"../ownership.js";const t=[`platform.finance`],n=[`open-banking`,`finance`];[...t],[...n],e.Experimental,[...t],[...n],e.Experimental,[...t],[...n],e.Experimental;
+import { StabilityEnum } from "../ownership.js";
+
+//#region ../../libs/contracts/dist/capabilities/openbanking.js
+const OWNERS = ["platform.finance"];
+const TAGS = ["open-banking", "finance"];
+const openBankingAccountsReadCapability = {
+	meta: {
+		key: "openbanking.accounts.read",
+		version: 1,
+		kind: "integration",
+		title: "Open Banking Accounts (Read)",
+		description: "Provides read-only access to linked bank accounts, including account summaries and metadata.",
+		domain: "finance",
+		owners: [...OWNERS],
+		tags: [...TAGS],
+		stability: StabilityEnum.Experimental
+	},
+	provides: [
+		{
+			surface: "operation",
+			name: "openbanking.accounts.list",
+			version: 1,
+			description: "List bank accounts linked to a Powens open banking connection."
+		},
+		{
+			surface: "operation",
+			name: "openbanking.accounts.get",
+			version: 1,
+			description: "Retrieve the canonical bank account record for a specific account."
+		},
+		{
+			surface: "operation",
+			name: "openbanking.accounts.sync",
+			version: 1,
+			description: "Trigger a refresh of bank account metadata from the open banking provider."
+		}
+	]
+};
+const openBankingTransactionsReadCapability = {
+	meta: {
+		key: "openbanking.transactions.read",
+		version: 1,
+		kind: "integration",
+		title: "Open Banking Transactions (Read)",
+		description: "Enables retrieval of transaction history for linked bank accounts via open banking providers.",
+		domain: "finance",
+		owners: [...OWNERS],
+		tags: [...TAGS, "transactions"],
+		stability: StabilityEnum.Experimental
+	},
+	provides: [{
+		surface: "operation",
+		name: "openbanking.transactions.list",
+		version: 1,
+		description: "List transactions for a given bank account with optional date filtering."
+	}, {
+		surface: "operation",
+		name: "openbanking.transactions.sync",
+		version: 1,
+		description: "Synchronise transactions from the open banking provider into the canonical ledger."
+	}]
+};
+const openBankingBalancesReadCapability = {
+	meta: {
+		key: "openbanking.balances.read",
+		version: 1,
+		kind: "integration",
+		title: "Open Banking Balances (Read)",
+		description: "Allows querying of current and available balances for linked bank accounts via open banking providers.",
+		domain: "finance",
+		owners: [...OWNERS],
+		tags: [...TAGS, "balances"],
+		stability: StabilityEnum.Experimental
+	},
+	provides: [{
+		surface: "operation",
+		name: "openbanking.balances.get",
+		version: 1,
+		description: "Retrieve the latest known balances for a specified bank account."
+	}, {
+		surface: "operation",
+		name: "openbanking.balances.refresh",
+		version: 1,
+		description: "Force a balance refresh from the open banking provider."
+	}]
+};
+
+//#endregion

package/dist/libs/contracts/dist/client/index.js

@@ -1 +1,5 @@
-"use client";import"./react/feature-render.js";import"./react/form-render.js";import"./react/index.js";
+'use client';
+
+import "./react/feature-render.js";
+import "./react/form-render.js";
+import "./react/index.js";

package/dist/libs/contracts/dist/client/react/feature-render.js

@@ -1 +1,2 @@
-import"../../presentations.v2.js";import"react";
+import "../../presentations.v2.js";
+import "react";

package/dist/libs/contracts/dist/client/react/form-render.js

@@ -1 +1,4 @@
-import"react";import"react-hook-form";import"@hookform/resolvers/zod";import"react/jsx-runtime";
+import "react";
+import "react-hook-form";
+import "@hookform/resolvers/zod";
+import "react/jsx-runtime";

package/dist/libs/contracts/dist/client/react/index.js

@@ -1 +1,4 @@
-"use client";import"./feature-render.js";import"./form-render.js";
+'use client';
+
+import "./feature-render.js";
+import "./form-render.js";

package/dist/libs/contracts/dist/contract-registry/index.js

@@ -1 +1 @@
-import{i as e,n as t,r as n}from"./schemas.js";
+import { ContractRegistryFileSchema, ContractRegistryItemSchema, ContractRegistryItemTypeSchema } from "./schemas.js";

package/dist/libs/contracts/dist/contract-registry/schemas.js

@@ -1 +1,60 @@
-import{e}from"../ownership.js";import t from"zod";const n=t.enum([`contractspec:operation`,`contractspec:event`,`contractspec:presentation`,`contractspec:form`,`contractspec:feature`,`contractspec:workflow`,`contractspec:template`,`contractspec:integration`,`contractspec:data-view`,`contractspec:migration`,`contractspec:telemetry`,`contractspec:experiment`,`contractspec:app-config`,`contractspec:knowledge`]),r=t.object({path:t.string().min(1),type:t.string().min(1),content:t.string().optional()}),i=t.object({name:t.string().min(1),type:n,version:t.number().int().nonnegative(),title:t.string().min(1),description:t.string().min(1),meta:t.object({stability:t.enum([e.Idea,e.InCreation,e.Experimental,e.Beta,e.Stable,e.Deprecated]),owners:t.array(t.string().min(1)).default([]),tags:t.array(t.string().min(1)).default([])}),dependencies:t.array(t.string().min(1)).optional(),registryDependencies:t.array(t.string().min(1)).optional(),files:t.array(r).min(1),schema:t.object({input:t.unknown().optional(),output:t.unknown().optional()}).optional()});t.object({$schema:t.string().min(1).optional(),name:t.string().min(1),homepage:t.string().min(1).optional(),items:t.array(i)});export{i,n,r};
+import { StabilityEnum } from "../ownership.js";
+import z from "zod";
+
+//#region ../../libs/contracts/dist/contract-registry/schemas.js
+const ContractRegistryItemTypeSchema = z.enum([
+	"contractspec:operation",
+	"contractspec:event",
+	"contractspec:presentation",
+	"contractspec:form",
+	"contractspec:feature",
+	"contractspec:workflow",
+	"contractspec:template",
+	"contractspec:integration",
+	"contractspec:data-view",
+	"contractspec:migration",
+	"contractspec:telemetry",
+	"contractspec:experiment",
+	"contractspec:app-config",
+	"contractspec:knowledge"
+]);
+const ContractRegistryFileSchema = z.object({
+	path: z.string().min(1),
+	type: z.string().min(1),
+	content: z.string().optional()
+});
+const ContractRegistryItemSchema = z.object({
+	name: z.string().min(1),
+	type: ContractRegistryItemTypeSchema,
+	version: z.number().int().nonnegative(),
+	title: z.string().min(1),
+	description: z.string().min(1),
+	meta: z.object({
+		stability: z.enum([
+			StabilityEnum.Idea,
+			StabilityEnum.InCreation,
+			StabilityEnum.Experimental,
+			StabilityEnum.Beta,
+			StabilityEnum.Stable,
+			StabilityEnum.Deprecated
+		]),
+		owners: z.array(z.string().min(1)).default([]),
+		tags: z.array(z.string().min(1)).default([])
+	}),
+	dependencies: z.array(z.string().min(1)).optional(),
+	registryDependencies: z.array(z.string().min(1)).optional(),
+	files: z.array(ContractRegistryFileSchema).min(1),
+	schema: z.object({
+		input: z.unknown().optional(),
+		output: z.unknown().optional()
+	}).optional()
+});
+const ContractRegistryManifestSchema = z.object({
+	$schema: z.string().min(1).optional(),
+	name: z.string().min(1),
+	homepage: z.string().min(1).optional(),
+	items: z.array(ContractRegistryItemSchema)
+});
+
+//#endregion
+export { ContractRegistryFileSchema, ContractRegistryItemSchema, ContractRegistryItemTypeSchema };

package/dist/libs/contracts/dist/docs/PUBLISHING.docblock.js

@@ -1,76 +1,16 @@
-import{a as e}from"./registry.js";e([{id:`docs.PUBLISHING`,title:`Publishing ContractSpec Libraries`,summary:`This guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).`,kind:`reference`,visibility:`public`,route:`/docs/PUBLISHING`,tags:[`PUBLISHING`],body:`# Publishing ContractSpec Libraries
-
-This guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).
-
-## Release Tracks
-
-| Track | Branch | npm Tag | Frequency | Versioning | Use Case |
-|-------|--------|---------|-----------|------------|----------|
-| **Stable** | \`release\` | \`latest\` | Manual | SemVer (e.g., \`1.7.4\`) | Production, external users |
-| **Canary** | \`main\` | \`canary\` | Every Push | Snapshot (e.g., \`1.7.4-canary...\`) | Dev, internal testing |
-
-## Prerequisites
-
-- ✅ \`NPM_TOKEN\` secret is configured in GitHub (owner or automation token with _publish_ scope).
-- ✅ \`GITHUB_TOKEN\` (built-in) has permissions to create PRs (enabled by default in new repos).
-- ✅ For stable releases: \`release\` branch exists and is protected.
-
-## Canary Workflow (Automatic)
-
-Every commit pushed to \`main\` triggers the \`.github/workflows/publish-canary.yml\` workflow.
-
-1. **Trigger**: Push to \`main\`.
-2. **Versioning**: Runs \`changeset version --snapshot canary\` to generate a temporary snapshot version.
-3. **Publish**: Packages are published to npm with the \`canary\` tag using \`changeset publish --tag canary\`.
-
-### Consuming Canary Builds
-
-To install the latest bleeding-edge version:
-
-\`\`\`bash
-npm install @lssm/lib.contracts@canary
-# or
-bun add @lssm/lib.contracts@canary
-\`\`\`
-
-## Stable Release Workflow (Manual)
-
-Stable releases are managed via the \`release\` branch using the standard [Changesets Action](https://github.com/changesets/action).
-
-1. **Develop on \`main\`**: Create features and fixes.
-2. **Add Changesets**: Run \`bun changeset\` to document changes and impact (major/minor/patch).
-3. **Merge to \`release\`**: When ready to ship, open a PR from \`main\` to \`release\` or merge manually.
-4. **"Version Packages" PR**:
-   - The GitHub Action detects new changesets and automatically creates a Pull Request titled **"Version Packages"**.
-   - This PR contains the version bumps and updated \`CHANGELOG.md\` files.
-5. **Merge & Publish**:
-   - Review and merge the "Version Packages" PR.
-   - The Action runs again, detects the versions have been bumped, builds the libraries, and publishes them to npm with the \`latest\` tag.
-
-### Publishing Steps
-
-1. Ensure all changesets are present on \`main\`.
-2. Merge \`main\` into \`release\`:
-   \`\`\`bash
-   git checkout release
-   git pull origin release
-   git merge main
-   git push origin release
-   \`\`\`
-3. Go to GitHub Pull Requests. You will see a **"Version Packages"** PR created by the bot.
-4. Merge that PR.
-5. The release is now live on npm!
-
-## Manual Verification (Optional)
-
-Before publishing a new version you can run:
-
-\`\`\`bash
-bun run build:not-apps
-npx npm-packlist --json packages/libs/contracts
-\`\`\`
-
-## Rollback
-
-If a publish fails mid-way, re-run the workflow once the issue is fixed. Already published packages are skipped automatically. Use \`npm deprecate <package>@<version>\` if we need to warn consumers about a broken release.
-`}]);
+import { registerDocBlocks } from "./registry.js";
+
+//#region ../../libs/contracts/dist/docs/PUBLISHING.docblock.js
+const PUBLISHING_DocBlocks = [{
+	id: "docs.PUBLISHING",
+	title: "Publishing ContractSpec Libraries",
+	summary: "This guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).",
+	kind: "reference",
+	visibility: "public",
+	route: "/docs/PUBLISHING",
+	tags: ["PUBLISHING"],
+	body: "# Publishing ContractSpec Libraries\n\nThis guide describes how we release the ContractSpec libraries to npm. We use a dual-track release system: **Stable** (manual) and **Canary** (automatic).\n\n## Release Tracks\n\n| Track | Branch | npm Tag | Frequency | Versioning | Use Case |\n|-------|--------|---------|-----------|------------|----------|\n| **Stable** | `release` | `latest` | Manual | SemVer (e.g., `1.7.4`) | Production, external users |\n| **Canary** | `main` | `canary` | Every Push | Snapshot (e.g., `1.7.4-canary...`) | Dev, internal testing |\n\n## Prerequisites\n\n- ✅ `NPM_TOKEN` secret is configured in GitHub (owner or automation token with _publish_ scope).\n- ✅ `GITHUB_TOKEN` (built-in) has permissions to create PRs (enabled by default in new repos).\n- ✅ For stable releases: `release` branch exists and is protected.\n\n## Canary Workflow (Automatic)\n\nEvery commit pushed to `main` triggers the `.github/workflows/publish-canary.yml` workflow.\n\n1. **Trigger**: Push to `main`.\n2. **Versioning**: Runs `changeset version --snapshot canary` to generate a temporary snapshot version.\n3. **Publish**: Packages are published to npm with the `canary` tag using `changeset publish --tag canary`.\n\n### Consuming Canary Builds\n\nTo install the latest bleeding-edge version:\n\n```bash\nnpm install @lssm/lib.contracts@canary\n# or\nbun add @lssm/lib.contracts@canary\n```\n\n## Stable Release Workflow (Manual)\n\nStable releases are managed via the `release` branch using the standard [Changesets Action](https://github.com/changesets/action).\n\n1. **Develop on `main`**: Create features and fixes.\n2. **Add Changesets**: Run `bun changeset` to document changes and impact (major/minor/patch).\n3. **Merge to `release`**: When ready to ship, open a PR from `main` to `release` or merge manually.\n4. **\"Version Packages\" PR**:\n   - The GitHub Action detects new changesets and automatically creates a Pull Request titled **\"Version Packages\"**.\n   - This PR contains the version bumps and updated `CHANGELOG.md` files.\n5. **Merge & Publish**:\n   - Review and merge the \"Version Packages\" PR.\n   - The Action runs again, detects the versions have been bumped, builds the libraries, and publishes them to npm with the `latest` tag.\n\n### Publishing Steps\n\n1. Ensure all changesets are present on `main`.\n2. Merge `main` into `release`:\n   ```bash\n   git checkout release\n   git pull origin release\n   git merge main\n   git push origin release\n   ```\n3. Go to GitHub Pull Requests. You will see a **\"Version Packages\"** PR created by the bot.\n4. Merge that PR.\n5. The release is now live on npm!\n\n## Manual Verification (Optional)\n\nBefore publishing a new version you can run:\n\n```bash\nbun run build:not-apps\nnpx npm-packlist --json packages/libs/contracts\n```\n\n## Rollback\n\nIf a publish fails mid-way, re-run the workflow once the issue is fixed. Already published packages are skipped automatically. Use `npm deprecate <package>@<version>` if we need to warn consumers about a broken release.\n"
+}];
+registerDocBlocks(PUBLISHING_DocBlocks);
+
+//#endregion