@north-light/cli 0.3.544 → 0.3.545

package/dist/builtin-memory/crouter-sdk/release-notes.md

@@ -9,6 +9,12 @@ when-and-why-to-read: When you need Release notes, this knowledge should be read
 
 Changes to `@north-light/sdk` that can change what an existing app sees. Newest first.
 
+## 0.3.545
+
+`@north-light/sdk/stores/postgres` gains an object kit: `PostgresObjectStore` and `objectKitSchemaSql`. Additive: no existing export, request or response changes.
+
+- `PostgresObjectStore` keeps per-person custom objects (`instance`), the nodes watching them (`watch`), and a PostgreSQL publish outbox written inside the caller's transaction (`enqueue`) and delivered at least once by `startPublisher`. `objectKitSchemaSql()` returns the DDL for its three tables. See [Watchable objects](/docs/guides/watchable-objects).
+
 ## 0.3.542
 
 The directory's account page reads and removes individual AI subscription accounts. Additive: no app-facing request or response changes.

package/dist/builtin-memory/northlight-apps/guides/watchable-objects.md

@@ -0,0 +1,74 @@
+---
+kind: knowledge
+when-and-why-to-read: When you need Watchable objects, this knowledge should be
+  read because Give each person a canvas object per thing in your app, let their
+  agents watch it, and publish events to it reliably with the PostgreSQL object
+  kit.
+---
+
+# Watchable objects
+
+`PostgresObjectStore` from `@north-light/sdk/stores/postgres` keeps one canvas object per person for each thing in your app (a problem, a ticket, a workspace), links the person's nodes to it, and delivers events to it from a database outbox. An agent that runs `crtr <your-plugin> thing watch T-12` then receives the events you publish for T-12.
+
+Your app declares the object kinds and their events in its plugin with `definePlugin({objectKinds})` (see [Deploying a plugin](https://crouter.docs.northlight.ai/docs/plugin/deploying)). The store registers objects of those kinds. Install `pg` in your app.
+
+## Create the tables
+
+`objectKitSchemaSql()` returns the DDL. Put it in your migration; the store never creates tables.
+
+```ts
+import {objectKitSchemaSql} from '@north-light/sdk/stores/postgres';
+
+console.log(objectKitSchemaSql()); // or objectKitSchemaSql({object: 'app.watch_object', watcher: '…', publish: '…'})
+```
+
+It creates three tables (names default to `watch_object`, `watch_watcher`, `watch_publish`):
+
+| Table | Holds |
+|---|---|
+| object | `object_id` (the runtime's id), `sub`, `kind`, `target`, `name`, `created_at`; unique on (`sub`, `kind`, `target`) |
+| watcher | `object_id`, `node`, `machine` (`''` for the person's hosted runtime); one row per linked node |
+| publish | the outbox: `id`, `object_id`, `event`, `summary`, `state` (jsonb), `status` (`pending`, `done`, `dropped`), `attempts`, `last_error`, `next_attempt_at`, `created_at` |
+
+Table names are lowercase identifiers, optionally schema-qualified.
+
+## Use it
+
+```ts
+import {Pool} from 'pg';
+import {PostgresObjectStore} from '@north-light/sdk/stores/postgres';
+
+const pool = new Pool({connectionString: process.env.DATABASE_URL});
+const objects = new PostgresObjectStore(pool, {
+  providerId: process.env.CROUTER_CLIENT_ID!,          // kinds register as `<providerId>.<kind>`
+  runtime: (sub) => oauth.appClient(sub),               // the app's client on that person's runtime
+});
+
+// In a command: find or create the person's object, then link the calling node to it.
+const object = await objects.instance(sub, 'problem', 'P-12', {name: 'problem/P-12', description: 'Problem P-12'});
+await objects.watch(object.objectId, ctx.caller.crtr.node, ctx.caller.crtr.machine);
+
+// In the transaction of the write the event records:
+await client.query('BEGIN');
+// … your writes …
+await objects.enqueue(client, object.objectId, {event: 'recovered', summary: 'P-12 recovered', state: {id: 'P-12'}});
+await client.query('COMMIT');
+
+// Once per process:
+const publisher = objects.startPublisher();             // every 5 s, up to 100 rows
+// on shutdown: await publisher.stop();
+```
+
+- `instance(sub, kind, target, {name, description})` returns the existing object for that (person, kind, target), or registers a private object on the person's runtime and stores it. Two calls racing to create the same object each register one; the row that committed first is kept and the other registration is unregistered. Use `''` as `target` for a kind with one object per person.
+- `watch(objectId, node, machine?)` links the node on the person's runtime (`canvas.watch` with `watcher`, plus `watcher_machine` when `machine` is set) and records the link. It is safe to repeat. A node the runtime does not know rejects with `NotFoundError`.
+- `enqueue(client, objectId, {event, summary, state?})` inserts an outbox row with the client you pass. Pass the client of your open transaction and the row exists exactly when your write committed. `summary` is cut to 500 characters. The object must already exist (the outbox references it).
+- `startPublisher({tick?, batch?})` delivers pending rows oldest first, every `tick` ms (default 5000), at most `batch` per tick (default 100). A Postgres advisory lock lets one process at a time deliver, so every instance of your app can run it. Delivery is at least once.
+
+## Delivery rules
+
+- A transient failure (network, 5xx, 429, `unknown_event`) keeps the row pending and retries after `min(2^attempts × 10 s, 15 min)`.
+- A refusal the runtime will never accept (HTTP 400, 404 or 422, other than `unknown_event`) marks the row `dropped` with `last_error` set.
+- A row still undelivered 24 hours after it was enqueued is marked `dropped`.
+- Rows are never deleted; delete `done` and `dropped` rows from your own cleanup job.
+
+`PostgresObjectStore.tick()` runs one delivery pass and answers `false` when another process holds the lock; `startPublisher` calls it on a timer, logging a failed tick and carrying on. Pass `log: {warn, error}` to route those messages.

package/dist/builtin-memory/northlight-apps/reach-people-by-text.md

@@ -40,7 +40,7 @@ The [Comms guide for coding agents](https://comms.northlight.ai/llms.txt) is the
 5. **Text it from your own phone, in test mode.** Add yourself as a tester (`crtr comms testers add --app-id <id> --phone <number> --label <name>`, or the site), then text `JOIN <code>` to the test number. Test mode is free; the [Comms guide](https://comms.northlight.ai/llms.txt) has the tester limit.
 6. **Go to production** when you want your app's own number and anyone to text it. Production is paid: add a card on the billing account, and Comms gets your app its own number.
 
-Comms is priced per person your app texts with in production each month; fake mode and testing are free. The SDK is [`@north-light/comms`](https://www.npmjs.com/package/@north-light/comms) on npm. Its 0.3.0 release declares `@north-light/sdk` 0.3.457 as an exact optional peer, so in a project pinned to a newer SDK install it with `npm i @north-light/comms --legacy-peer-deps`.
+Comms is priced per person your app texts with in production each month; fake mode and testing are free. The SDK is [`@north-light/comms`](https://www.npmjs.com/package/@north-light/comms) on npm. Install it with `npm i @north-light/comms`.
 
 ## Rules
 

package/docs/apps/guides/watchable-objects.md

@@ -0,0 +1,71 @@
+---
+title: Watchable objects
+description: Give each person a canvas object per thing in your app, let their agents watch it, and publish events to it reliably with the PostgreSQL object kit.
+---
+
+# Watchable objects
+
+`PostgresObjectStore` from `@north-light/sdk/stores/postgres` keeps one canvas object per person for each thing in your app (a problem, a ticket, a workspace), links the person's nodes to it, and delivers events to it from a database outbox. An agent that runs `crtr <your-plugin> thing watch T-12` then receives the events you publish for T-12.
+
+Your app declares the object kinds and their events in its plugin with `definePlugin({objectKinds})` (see [Deploying a plugin](https://crouter.docs.northlight.ai/docs/plugin/deploying)). The store registers objects of those kinds. Install `pg` in your app.
+
+## Create the tables
+
+`objectKitSchemaSql()` returns the DDL. Put it in your migration; the store never creates tables.
+
+```ts
+import {objectKitSchemaSql} from '@north-light/sdk/stores/postgres';
+
+console.log(objectKitSchemaSql()); // or objectKitSchemaSql({object: 'app.watch_object', watcher: '…', publish: '…'})
+```
+
+It creates three tables (names default to `watch_object`, `watch_watcher`, `watch_publish`):
+
+| Table | Holds |
+|---|---|
+| object | `object_id` (the runtime's id), `sub`, `kind`, `target`, `name`, `created_at`; unique on (`sub`, `kind`, `target`) |
+| watcher | `object_id`, `node`, `machine` (`''` for the person's hosted runtime); one row per linked node |
+| publish | the outbox: `id`, `object_id`, `event`, `summary`, `state` (jsonb), `status` (`pending`, `done`, `dropped`), `attempts`, `last_error`, `next_attempt_at`, `created_at` |
+
+Table names are lowercase identifiers, optionally schema-qualified.
+
+## Use it
+
+```ts
+import {Pool} from 'pg';
+import {PostgresObjectStore} from '@north-light/sdk/stores/postgres';
+
+const pool = new Pool({connectionString: process.env.DATABASE_URL});
+const objects = new PostgresObjectStore(pool, {
+  providerId: process.env.CROUTER_CLIENT_ID!,          // kinds register as `<providerId>.<kind>`
+  runtime: (sub) => oauth.appClient(sub),               // the app's client on that person's runtime
+});
+
+// In a command: find or create the person's object, then link the calling node to it.
+const object = await objects.instance(sub, 'problem', 'P-12', {name: 'problem/P-12', description: 'Problem P-12'});
+await objects.watch(object.objectId, ctx.caller.crtr.node, ctx.caller.crtr.machine);
+
+// In the transaction of the write the event records:
+await client.query('BEGIN');
+// … your writes …
+await objects.enqueue(client, object.objectId, {event: 'recovered', summary: 'P-12 recovered', state: {id: 'P-12'}});
+await client.query('COMMIT');
+
+// Once per process:
+const publisher = objects.startPublisher();             // every 5 s, up to 100 rows
+// on shutdown: await publisher.stop();
+```
+
+- `instance(sub, kind, target, {name, description})` returns the existing object for that (person, kind, target), or registers a private object on the person's runtime and stores it. Two calls racing to create the same object each register one; the row that committed first is kept and the other registration is unregistered. Use `''` as `target` for a kind with one object per person.
+- `watch(objectId, node, machine?)` links the node on the person's runtime (`canvas.watch` with `watcher`, plus `watcher_machine` when `machine` is set) and records the link. It is safe to repeat. A node the runtime does not know rejects with `NotFoundError`.
+- `enqueue(client, objectId, {event, summary, state?})` inserts an outbox row with the client you pass. Pass the client of your open transaction and the row exists exactly when your write committed. `summary` is cut to 500 characters. The object must already exist (the outbox references it).
+- `startPublisher({tick?, batch?})` delivers pending rows oldest first, every `tick` ms (default 5000), at most `batch` per tick (default 100). A Postgres advisory lock lets one process at a time deliver, so every instance of your app can run it. Delivery is at least once.
+
+## Delivery rules
+
+- A transient failure (network, 5xx, 429, `unknown_event`) keeps the row pending and retries after `min(2^attempts × 10 s, 15 min)`.
+- A refusal the runtime will never accept (HTTP 400, 404 or 422, other than `unknown_event`) marks the row `dropped` with `last_error` set.
+- A row still undelivered 24 hours after it was enqueued is marked `dropped`.
+- Rows are never deleted; delete `done` and `dropped` rows from your own cleanup job.
+
+`PostgresObjectStore.tick()` runs one delivery pass and answers `false` when another process holds the lock; `startPublisher` calls it on a timer, logging a failed tick and carrying on. Pass `log: {warn, error}` to route those messages.

package/docs/apps/reach-people-by-text.md

@@ -37,7 +37,7 @@ The [Comms guide for coding agents](https://comms.northlight.ai/llms.txt) is the
 5. **Text it from your own phone, in test mode.** Add yourself as a tester (`crtr comms testers add --app-id <id> --phone <number> --label <name>`, or the site), then text `JOIN <code>` to the test number. Test mode is free; the [Comms guide](https://comms.northlight.ai/llms.txt) has the tester limit.
 6. **Go to production** when you want your app's own number and anyone to text it. Production is paid: add a card on the billing account, and Comms gets your app its own number.
 
-Comms is priced per person your app texts with in production each month; fake mode and testing are free. The SDK is [`@north-light/comms`](https://www.npmjs.com/package/@north-light/comms) on npm. Its 0.3.0 release declares `@north-light/sdk` 0.3.457 as an exact optional peer, so in a project pinned to a newer SDK install it with `npm i @north-light/comms --legacy-peer-deps`.
+Comms is priced per person your app texts with in production each month; fake mode and testing are free. The SDK is [`@north-light/comms`](https://www.npmjs.com/package/@north-light/comms) on npm. Install it with `npm i @north-light/comms`.
 
 ## Rules
 

package/docs/release-local.md

@@ -3,7 +3,7 @@
 Use this only for a release explicitly authorized by Silas. `.github/workflows/publish.yml` is the source of truth; this is its manual path when Actions cannot run. Work on clean, current `main`, with `npm whoami` showing the publishing account. Verify the code first (`npm run build:api`, `npm run build`, `npx tsc --noEmit`, relevant `npm run test:isolated -- …`). Do not start a release while another agent owns uncommitted changes in this shared checkout.
 
 1. Check the six latest registry versions with `npm view <name> version` for each of `@north-light/cli`, `@north-light/api`, `@north-light/env-docker`, `@north-light/identity`, `@north-light/sdk` and `@north-light/plugin`. Fetch `origin/main`, ensure the release commit is current, and choose a patch version greater than every published version. Do **not** use the workflow's `git reset --hard` in a shared checkout.
-2. Run `node scripts/release-version.mjs "$VERSION"`. It sets all six manifests to `$VERSION`, pins every dependency between them (root → identity, SDK → api and identity, plugin → api and identity) to exactly `$VERSION` with no `^`, writes `SDK_VERSION` in `packages/crouter-sdk/src/version.ts` (informational: compatibility is the contract level), and renames the `## Next release` section of `docs/sdk/release-notes.md` to `## $VERSION`. One release is one version set: an app pinning `@north-light/sdk@$VERSION` gets exactly this release's api and identity. Run `npm install --package-lock-only --ignore-scripts`, then `node scripts/contract.mjs release`: it fails on an unacknowledged breaking `/v1` change or an undeclared watched file (the same check CI runs), then writes `contract/surface.txt`, `CONTRACT_LEVEL` in `src/api/contract.ts` (a minor bump only when the surface changed or a declaration says `bump`), `crouterContract` in the SDK manifest, and resets `contract/next.json`. Run `node scripts/release-version.mjs --check` (prints `one version set`). Check `git diff` and commit only the six manifests, `packages/crouter-sdk/src/version.ts`, `docs/sdk/release-notes.md`, `package-lock.json`, `contract/surface.txt`, `contract/next.json` and `src/api/contract.ts` as `chore: release v$VERSION`. Create `git tag -a "v$VERSION" -m "chore: release v$VERSION"`, then `git push --atomic origin HEAD:main "refs/tags/v$VERSION"`. If rejected due to a concurrent push, remove the *local* release tag, integrate fresh main, then recheck versions and retry; never push a tag separately.
-3. From the tagged release commit run `npm ci`. Publish in dependency order, checking `npm view "$PACKAGE@$VERSION" version` before each and skipping only on a positive sighting: `npm run build:identity` then `npm publish` in `packages/crouter-identity`; `npm run build` then `CRTR_PACK_MINIFY=1 npm publish` at root (Docker must be running: the pack cross-builds the Linux x64 and arm64 native addons into `dist/native/linux/<arch>/addon.node` and fails the release if it cannot); `npm run build:api` then publish in `packages/crouter-api`; `npm run build:env-docker` then publish in `packages/crouter-env-docker`; `npm run build:api && npm run build:identity && npm run build:sdk` then `npm publish --tag next` in `packages/crouter-sdk` (its `prepublishOnly` guard refuses any other form, including `--tag latest`; every SDK release lands on `next`); `npm run build:api && npm run build:identity && npm run build:plugin` then `CRTR_PACK_MINIFY=1 npm publish` in `packages/crouter-plugin`. Use npm's interactive authentication/2FA where required (see `personal-operations/npm-2fa-cli`); a read-only token cannot publish. Provenance remains off because the source repository is private. Do not build or publish the Docker image in this no-Actions path.
+2. Run `node scripts/release-version.mjs "$VERSION"`. It sets all six manifests to `$VERSION`, pins every dependency between them (root → identity, SDK → api, identity and plugin, plugin → api and identity) to exactly `$VERSION` with no `^`, writes `SDK_VERSION` in `packages/crouter-sdk/src/version.ts` (informational: compatibility is the contract level), and renames the `## Next release` section of `docs/sdk/release-notes.md` to `## $VERSION`. One release is one version set: an app pinning `@north-light/sdk@$VERSION` gets exactly this release's api and identity. Run `npm install --package-lock-only --ignore-scripts`, then `node scripts/contract.mjs release`: it fails on an unacknowledged breaking `/v1` change or an undeclared watched file (the same check CI runs), then writes `contract/surface.txt`, `CONTRACT_LEVEL` in `src/api/contract.ts` (a minor bump only when the surface changed or a declaration says `bump`), `crouterContract` in the SDK manifest, and resets `contract/next.json`. Run `node scripts/release-version.mjs --check` (prints `one version set`). Check `git diff` and commit only the six manifests, `packages/crouter-sdk/src/version.ts`, `docs/sdk/release-notes.md`, `package-lock.json`, `contract/surface.txt`, `contract/next.json` and `src/api/contract.ts` as `chore: release v$VERSION`. Create `git tag -a "v$VERSION" -m "chore: release v$VERSION"`, then `git push --atomic origin HEAD:main "refs/tags/v$VERSION"`. If rejected due to a concurrent push, remove the *local* release tag, integrate fresh main, then recheck versions and retry; never push a tag separately.
+3. From the tagged release commit run `npm ci`. Publish in dependency order, checking `npm view "$PACKAGE@$VERSION" version` before each and skipping only on a positive sighting: `npm run build:identity` then `npm publish` in `packages/crouter-identity`; `npm run build` then `CRTR_PACK_MINIFY=1 npm publish` at root (Docker must be running: the pack cross-builds the Linux x64 and arm64 native addons into `dist/native/linux/<arch>/addon.node` and fails the release if it cannot); `npm run build:api` then publish in `packages/crouter-api`; `npm run build:env-docker` then publish in `packages/crouter-env-docker`; `npm run build:plugin` then `CRTR_PACK_MINIFY=1 npm publish` in `packages/crouter-plugin` (the SDK depends on it, so it goes first); then `npm run build:sdk` then `npm publish --tag next` in `packages/crouter-sdk` (its `prepublishOnly` guard refuses any other form, including `--tag latest`; every SDK release lands on `next`). Use npm's interactive authentication/2FA where required (see `personal-operations/npm-2fa-cli`); a read-only token cannot publish. Provenance remains off because the source repository is private. Do not build or publish the Docker image in this no-Actions path.
 4. Confirm all six exact versions with `npm view`. In a fresh temporary directory, `npm init -y && npm install @north-light/sdk@$VERSION`, then prove both `@north-light/sdk/errors` (`errorCodes`) and `@north-light/sdk/stores/postgres` resolve via `node --input-type=module -e '…'`. Record any partial publish and finish it from the exact release tag rather than cutting another version: `gh workflow run publish.yml -f release_tag=v$VERSION` runs `recover-release`, which verifies the tag is a release commit on main, checks it out, and publishes only the packages and image the registry does not yet show (SDK to `next`; it never writes the image `:latest`, so if the recovered tag is the newest release, `:latest` follows the next normal release).
 5. Promote `latest` last, through CI only: `gh workflow run publish.yml -f promote=true` runs the `promote-sdk` job, the one writer of `latest`. It shares the `sdk-dist-tag` concurrency group with the automatic runs (they queue, never overlap), reads the router's `/contract` itself, re-reads `latest` right before the write and moves it only if unchanged. It also runs after each SDK publish and hourly. `PROD_CONTRACT_URL=<the router's /contract URL> node scripts/promote-sdk.mjs` is a read-only dry run; its `--apply` refuses outside Actions. **Never `npm dist-tag add` the SDK by hand.** The one exception is Actions fully down: a person then runs the printed target by hand through the npm 2FA wrapper only after re-reading `npm view @north-light/sdk dist-tags` and confirming no `promote-sdk` run is active (`gh run list --workflow publish.yml`) and that the target is above the current `latest`.

package/docs/sdk/release-notes.md

@@ -7,6 +7,12 @@ description: Behavior changes in @north-light/sdk that an app must act on, newes
 
 Changes to `@north-light/sdk` that can change what an existing app sees. Newest first.
 
+## 0.3.545
+
+`@north-light/sdk/stores/postgres` gains an object kit: `PostgresObjectStore` and `objectKitSchemaSql`. Additive: no existing export, request or response changes.
+
+- `PostgresObjectStore` keeps per-person custom objects (`instance`), the nodes watching them (`watch`), and a PostgreSQL publish outbox written inside the caller's transaction (`enqueue`) and delivered at least once by `startPublisher`. `objectKitSchemaSql()` returns the DDL for its three tables. See [Watchable objects](/docs/guides/watchable-objects).
+
 ## 0.3.542
 
 The directory's account page reads and removes individual AI subscription accounts. Additive: no app-facing request or response changes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@north-light/cli",
-  "version": "0.3.544",
+  "version": "0.3.545",
   "description": "crtr — agent runtime with memory, plugins, and marketplaces",
   "type": "module",
   "main": "dist/index.js",
@@ -93,7 +93,7 @@
     "activate:pull": "git pull && npm install && npm run activate",
     "build:api": "npm run build:identity && tsc -p packages/crouter-api/tsconfig.json",
     "build:env-docker": "tsc -p packages/crouter-env-docker/tsconfig.json",
-    "build:sdk": "npm run build:api && npm run build:identity && npm run build --workspace packages/crouter-sdk",
+    "build:sdk": "npm run build:api && npm run build:identity && npm run build:plugin && npm run build --workspace packages/crouter-sdk",
     "build:plugin": "tsc -p packages/crouter-plugin/tsconfig.json",
     "typecheck": "tsc --noEmit && tsc -p src/doc-editor/tsconfig.json",
     "typecheck:pi-packages": "npx tsc -p src/builtin-pi-packages/pi-crtr-extensions/tsconfig.json",
@@ -140,7 +140,7 @@
   },
   "license": "UNLICENSED",
   "dependencies": {
-    "@north-light/identity": "0.3.544",
+    "@north-light/identity": "0.3.545",
     "@earendil-works/pi-agent-core": "1.1.0",
     "@earendil-works/pi-ai": "1.1.0",
     "@earendil-works/pi-coding-agent": "1.1.0",

package/packages/crouter-identity/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@north-light/identity",
-  "version": "0.3.544",
+  "version": "0.3.545",
   "description": "Northlight access-token verification and scope rules",
   "type": "module",
   "main": "./dist/index.js",

package/runtime.lock.json

@@ -1,12 +1,12 @@
 {
   "name": "@north-light/cli",
-  "version": "0.3.544",
+  "version": "0.3.545",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@north-light/cli",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "hasInstallScript": true,
       "license": "UNLICENSED",
       "workspaces": [
@@ -24,7 +24,7 @@
         "@milkdown/preset-gfm": "^7.22.3",
         "@milkdown/prose": "^7.22.3",
         "@milkdown/utils": "^7.22.3",
-        "@north-light/identity": "0.3.544",
+        "@north-light/identity": "0.3.545",
         "cron-parser": "^5.6.0",
         "esbuild": "^0.27.7",
         "jose": "^6.2.12",
@@ -12455,17 +12455,17 @@
     },
     "packages/crouter-api": {
       "name": "@north-light/api",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "license": "UNLICENSED"
     },
     "packages/crouter-env-docker": {
       "name": "@north-light/env-docker",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "license": "UNLICENSED"
     },
     "packages/crouter-identity": {
       "name": "@north-light/identity",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "license": "UNLICENSED",
       "dependencies": {
         "jose": "^6.2.1"
@@ -12473,20 +12473,21 @@
     },
     "packages/crouter-plugin": {
       "name": "@north-light/plugin",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "license": "UNLICENSED",
       "dependencies": {
-        "@north-light/api": "0.3.544",
-        "@north-light/identity": "0.3.544"
+        "@north-light/api": "0.3.545",
+        "@north-light/identity": "0.3.545"
       }
     },
     "packages/crouter-sdk": {
       "name": "@north-light/sdk",
-      "version": "0.3.544",
+      "version": "0.3.545",
       "license": "UNLICENSED",
       "dependencies": {
-        "@north-light/api": "0.3.544",
-        "@north-light/identity": "0.3.544",
+        "@north-light/api": "0.3.545",
+        "@north-light/identity": "0.3.545",
+        "@north-light/plugin": "0.3.545",
         "jose": "^6.2.1"
       },
       "bin": {