@cotal-ai/connector-jcode 0.47.0 → 0.47.1

package/dist/host.js

@@ -59522,7 +59522,7 @@ config(en_default());
 
 // ../connector-core/dist/docs-bundle.generated.js
 var DOCS_BUNDLE = {
-  "version": "0.47.0",
+  "version": "0.47.1",
   "generatedFrom": "docs/*.md + SPEC.md + spec/cotal-lang.md + spec/cotal.schema.json",
   "pages": [
     {
@@ -59733,7 +59733,7 @@ var DOCS_BUNDLE = {
       "title": "Publishing a release",
       "kind": "Project (non-normative maintainer notes)",
       "summary": "Cotal uses Changesets to version and publish the workspace packages under packages/, extensions/, and implementations/ to npm.",
-      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
+      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm build && node scripts/seat-assemble-natives.mjs && pnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `pnpm build`: build every workspace package first, supplying local workspace dependency outputs\n  when a partial retry publishes only the packages still missing.\n- `seat-assemble-natives.mjs`: assemble the downloaded native seat artifacts before publication.\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
     },
     {
       "slug": "roadmap",

package/dist/index.js

@@ -14840,7 +14840,7 @@ import { isConcreteChannel as isConcreteChannel3, channelInAllow as channelInAll
 
 // ../connector-core/dist/docs-bundle.generated.js
 var DOCS_BUNDLE = {
-  "version": "0.47.0",
+  "version": "0.47.1",
   "generatedFrom": "docs/*.md + SPEC.md + spec/cotal-lang.md + spec/cotal.schema.json",
   "pages": [
     {
@@ -15051,7 +15051,7 @@ var DOCS_BUNDLE = {
       "title": "Publishing a release",
       "kind": "Project (non-normative maintainer notes)",
       "summary": "Cotal uses Changesets to version and publish the workspace packages under packages/, extensions/, and implementations/ to npm.",
-      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
+      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm build && node scripts/seat-assemble-natives.mjs && pnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `pnpm build`: build every workspace package first, supplying local workspace dependency outputs\n  when a partial retry publishes only the packages still missing.\n- `seat-assemble-natives.mjs`: assemble the downloaded native seat artifacts before publication.\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
     },
     {
       "slug": "roadmap",

package/dist/mcp.js

@@ -57515,7 +57515,7 @@ import { execFileSync } from "node:child_process";
 
 // ../connector-core/dist/docs-bundle.generated.js
 var DOCS_BUNDLE = {
-  "version": "0.47.0",
+  "version": "0.47.1",
   "generatedFrom": "docs/*.md + SPEC.md + spec/cotal-lang.md + spec/cotal.schema.json",
   "pages": [
     {
@@ -57726,7 +57726,7 @@ var DOCS_BUNDLE = {
       "title": "Publishing a release",
       "kind": "Project (non-normative maintainer notes)",
       "summary": "Cotal uses Changesets to version and publish the workspace packages under packages/, extensions/, and implementations/ to npm.",
-      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
+      "body": "# Publishing a release\n\n> **Project** (non-normative maintainer notes) \xB7 **For:** maintainers shipping Cotal\n\nCotal uses [Changesets](https://github.com/changesets/changesets) to version and publish the\nworkspace packages under `packages/*`, `extensions/*`, and `implementations/*` to npm.\n`examples/**` is ignored, since it is not published.\n\n## 0.11 runtime migration\n\nThe published binary no longer bundles the optional tmux and cmux runtimes. Existing operators\nmust run `cotal ext add @cotal-ai/tmux` or `cotal ext add @cotal-ai/cmux` once after upgrading,\nbefore using `runtime: tmux|cmux` in a manifest or passing `--runtime tmux|cmux`. Missing runtimes\nfail loudly with the matching install command; they never fall back to pty.\n\n## Trusted publishing\n\nTrusted publishing replaces the long-lived `NPM_TOKEN` secret with short-lived OIDC tokens\nissued by GitHub Actions. Each published package must be configured once on npmjs.com.\n\nThe `fixed` group in [`.changeset/config.json`](../.changeset/config.json) is the list that\ngets versioned and published. Derive the package list from it instead of\nmaintaining it by hand. It had drifted by six packages before this was last reconciled.\n\nFor **every** published package, `cotal-ai` (the binary), `@cotal-ai/core`,\n`@cotal-ai/workspace`, `@cotal-ai/cli`, `@cotal-ai/manager`, `@cotal-ai/delivery`,\n`@cotal-ai/web`, `@cotal-ai/cmux`, `@cotal-ai/orca`, `@cotal-ai/tmux`, `@cotal-ai/herdr`,\n`@cotal-ai/connector-core`, `@cotal-ai/connector-claude-code`, `@cotal-ai/connector-hermes`,\n`@cotal-ai/connector-opencode`, `@cotal-ai/connector-codex`, `@cotal-ai/pi`, `@cotal-ai/auth`:\n\n1. Go to `https://www.npmjs.com/package/<name>/access` (e.g.\n   `https://www.npmjs.com/package/@cotal-ai/core/access`).\n2. Scroll to **Trusted publishing** \u2192 **Add a trusted publisher**.\n3. Pick **GitHub Actions**.\n4. Fill in:\n   - **Organization or user:** the GitHub owner (your org or user).\n   - **Repository:** `Cotal`.\n   - **Workflow filename:** `changesets.yml`.\n   - **Environment name:** leave blank.\n5. Save. Repeat for every package.\n\n> The first time, you may need to publish a version manually (with a classic token) so the\n> package exists on npm. After that, OIDC takes over.\n\n## Day-to-day flow\n\n1. Open a PR that changes code in a publishable package.\n2. Add a changeset describing the change:\n\n   ```bash\n   pnpm changeset\n   ```\n\n   Pick the affected packages plus the semver bump (patch / minor / major), and write a\n   one-line summary. Commit the generated `.changeset/<name>.md` file alongside your code\n   change.\n3. Merge to `main`.\n4. The `Changesets` workflow runs:\n   - If there are pending changesets, it opens (or updates) a PR titled `chore(release):\n     version packages` that bumps versions and updates `CHANGELOG.md` files.\n   - When **that** PR is merged, the same workflow detects the bumped versions, runs `pnpm\n     build`, and `pnpm publish`es each changed package to npm with provenance.\n\n## Manual publish (escape hatch)\n\nIf the workflow is broken, you can run the same steps locally with a classic npm token:\n\n```bash\npnpm ci:version\npnpm ci:publish\n```\n\nSet `NPM_TOKEN` in your environment first. **Do not** commit the token.\n\n## Publication workflow\n\n`ci:publish` in the root `package.json` is:\n\n```bash\npnpm build && node scripts/seat-assemble-natives.mjs && pnpm publish -r --provenance --access=public --no-git-checks\n```\n\n- `pnpm build`: build every workspace package first, supplying local workspace dependency outputs\n  when a partial retry publishes only the packages still missing.\n- `seat-assemble-natives.mjs`: assemble the downloaded native seat artifacts before publication.\n- `-r`: recursively publish all workspace packages.\n- `--provenance`: emit SLSA provenance attestations (a no-op without OIDC, automatic with it).\n- `--access=public`: required for scoped packages on first publish.\n- `--no-git-checks`: skip pnpm's branch / clean-tree guard, since CI does not need it.\n"
     },
     {
       "slug": "roadmap",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@cotal-ai/connector-jcode",
   "description": "Cotal connector for Jcode: a host-mode mesh peer driven through Jcode's Harness API bridge.",
-  "version": "0.47.0",
+  "version": "0.47.1",
   "license": "Apache-2.0",
   "repository": {
     "type": "git",
@@ -29,9 +29,9 @@
     "esbuild": "^0.28.0",
     "tsx": "^4.22.4",
     "zod": "^4.4.3",
-    "@cotal-ai/connector-core": "0.47.0",
+    "@cotal-ai/connector-core": "0.47.1",
     "@cotal-ai/smoke-kit": "0.0.0",
-    "@cotal-ai/core": "0.47.0"
+    "@cotal-ai/core": "0.47.1"
   },
   "files": [
     "dist"