chore(release): version packages

[davidfarah2003]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

cotal-ai@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
• Updated dependencies [e986173]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/cli@0.46.0
  • @cotal-ai/manager@0.46.0
  • @cotal-ai/connector-core@0.46.0
  • @cotal-ai/workspace@0.46.0
  • @cotal-ai/runtime@0.46.0
  • @cotal-ai/auth@0.46.0
  • @cotal-ai/delivery@0.46.0

@cotal-ai/cmux@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/connector-codex@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/connector-core@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.
• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.
• e986173: Make manager inspect distinguish a stranded static slot from an unknown name through structured durable-state details, and make attach stop reconnecting when those details show the seat is gone.

@cotal-ai/connector-hermes@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/connector-opencode@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/herdr@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/orca@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/tmux@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.

@cotal-ai/cli@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.
• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.

Patch Changes

• e986173: Make manager inspect distinguish a stranded static slot from an unknown name through structured durable-state details, and make attach stop reconnecting when those details show the seat is gone.
• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0

@cotal-ai/manager@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.
• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.
• e986173: Make manager inspect distinguish a stranded static slot from an unknown name through structured durable-state details, and make attach stop reconnecting when those details show the seat is gone.

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0

@cotal-ai/runtime@0.46.0

Minor Changes

• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0
  • @cotal-ai/lang@0.46.0

@cotal-ai/core@0.46.0

Minor Changes

• 9d745af: Add the local durable runtime adoption seam and report legacy manager continuity before a running update can be described as hot. Runtime.adopt is optional: runtimes without durable custody omit it, and the manager refuses by name rather than requiring a throwing stub on every adapter. cotal update --self reports the selected manager before a global install and hands --space / --server / --creds to the replacement child.
• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.

@cotal-ai/workspace@0.46.0

Minor Changes

• 18a0024: The manager hosts workflow runs. run-start, run-resume, run-answer, run-status and
  run-ps are served on the manager's endpoint rails; a run is validated before anything is
  recorded, driven in the manager's process under a per-run run-driver credential, and taken back
  from its journal after a manager restart. cotal run is a client of that surface by default,
  with --local keeping the in-process drive, now under the run's own run-driver and
  run-operator credentials rather than admin; an answer's writes are pinned to the one pause it
  answers. A user-auth mesh refuses the family by name until a run can carry its user's owner. A new run capability mints the family into an
  agent's credential and injects the cotal_run tool, so an agent can write a cotal-lang program
  and start it from a session. run-answer records the answerer from the caller's credential and
  takes no by; cotal run answer drops --by on the hosted path. spawn({ supervise }) is a restart policy the manager enforces in
  place: { restarts, window? } (default 10m) until the budget is spent, then the seat is
  retired and the next turn is L4002. A policy this host cannot honour is refused at accept.

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0

@cotal-ai/auth@0.46.0

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0

@cotal-ai/delivery@0.46.0

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0

@cotal-ai/connector-claude-code@0.46.0

@cotal-ai/connector-jcode@0.46.0

@cotal-ai/pi@0.46.0

@cotal-ai/web@0.46.0

@cotal-ai/lang@0.46.0

@cotal-ai/example-04-frontier-faces@0.0.75

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0
  • @cotal-ai/workspace@0.46.0

@cotal-ai/example-05-scale-showcase@0.0.33

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0

@cotal-ai/example-06-feed-agent@0.0.14

Patch Changes

• Updated dependencies [9d745af]
• Updated dependencies [18a0024]
  • @cotal-ai/core@0.46.0

[davidfarah2003]

smoke:legacy-packaged-manager fails on this PR and will fail on every release PR, by construction. It is not a defect in the release contents. The suite has a latent hole that only becomes visible when the version being packed is not yet published.

I shepherded #1294, which put this suite into CI, so this is mine to report.

The failure

smoke (shard 3/4), run 33991180157, job 101373580979:

AssertionError [ERR_ASSERTION]: installed current packaged closure
  actual: 1   expected: 0
  implementations/cli/smoke/legacy-packaged-manager.smoke.ts:67
✗ shard 3/4 FAILED at: pnpm smoke:legacy-packaged-manager (exit 1)
NEVER RAN — 10 of 129 planned smoke(s) in this shard's partition did not start

Mechanism

The suite packs eight workspace packages and npm installs that set as a closure:

bin -> cotal-ai              packages/core       -> @cotal-ai/core
packages/workspace           implementations/cli -> @cotal-ai/cli
implementations/manager      implementations/delivery
implementations/auth         extensions/connector-core

bin/package.json declares "@cotal-ai/runtime": "workspace:*", and implementations/runtime is not in that list. pnpm pack rewrites workspace:* to the concrete current version, so the install must resolve @cotal-ai/runtime@<version> from the registry.

• On main: the version is 0.45.0, which is published, so npm fetches it and the install succeeds.
• On a release PR: the version is 0.46.0, which is not published yet — that is what the release PR exists to do. The install fails, and the assertion reports 1 !== 0.

Verified: npm view @cotal-ai/runtime version → 0.45.0; implementations/runtime/package.json is @cotal-ai/runtime, not private, and this PR bumps it.

The deeper defect, which matters more than the blocker

The cell is named "installed current packaged closure". On main it passes while pulling one member of that closure from the registry at the last published version, not from the build under test. So the suite has never verified what its name claims for @cotal-ai/runtime, and nobody could tell, because the registry copy was always close enough to work.

A green here has been partly an artifact of the last release being published. The release PR is the only context that exposes it.

Remedy

Add implementations/runtime to the packed set. That fixes the release-PR blocker and closes the hole on main at the same time — the closure becomes genuinely self-contained rather than self-contained-except-one.

Worth a guard so this cannot recur silently: after packing, assert that the install resolved every @cotal-ai/* dependency from the local tarball set, or run the install with --offline so any registry fetch fails loudly instead of succeeding by luck. Either turns "the closure is complete" from an assumption into an assertion.

Not done

Nothing changed and no branch touched. Flagging rather than fixing because this is a release PR with its own ownership, and because the fix belongs in the suite rather than in the release.

[davidfarah2003]

BLOCK at 2798a3f8df08c389d464ea932e12ee5290c580ea under the stated release-diff acceptance rule.

I performed a diff sanity review only. I did not install node_modules or run suites.

Verified:

• All 21 public packages in the fixed group move in lockstep from 0.45.0 to 0.46.0. No fixed-group package is left behind.
• The breaking release is a 0.x minor, not a major.
• Three private examples patch-bump independently. No package manifest field besides version changes.
• All 24 CHANGELOG diffs are additions only.
• The static-slot/attach entry from fix(manager): expose stranded static slot state #1313 is present under e986173.
• The changesets from fix(test): bypass pnpm dependency checks in mutations #1326 and test(manager): detect overlapping lease renewals #1327 are present and consumed. They declare no packages, so they correctly produce no package CHANGELOG entry.
• All five changeset source commits are ancestors of main tip 13b5484a53c96aa7def389b09ccf65c05187337b.

Blocking scope finding: the 54-file diff includes content outside package version bumps and CHANGELOG lines:

• extensions/connector-core/src/docs-bundle.generated.ts changes its embedded version from 0.45.0 to 0.46.0.
• Five .changeset/*.md files are deleted as part of release consumption.

Those are normal release-generation artifacts, but the review brief explicitly makes anything outside a version bump or CHANGELOG line a finding. On that rule, this PR cannot be approved as-is.

[davidfarah2003]

SUPERSEDING VERDICT: APPROVE at 2798a3f8df08c389d464ea932e12ee5290c580ea under the corrected Changesets release rule.

This supersedes my earlier BLOCK, which correctly applied the original but invalid acceptance rule.

I re-read the exact head through git and ran an executable four-class assertion harness. It reported:

• 24 package manifests change only version.
• All 21 public fixed-group packages move in lockstep from 0.45.0 to 0.46.0. The three private examples patch-bump independently.
• All 24 CHANGELOG diffs are additions only.
• Exactly five .changeset/*.md files are deleted, and they are the five changesets consumed by this release.
• extensions/connector-core/src/docs-bundle.generated.ts changes only its embedded version line from 0.45.0 to 0.46.0. No version-adjacent or generated CHANGELOG content changed unexpectedly.
• Zero paths fall outside the four permitted classes.
• git diff --check passes.

The five changeset source commits are ancestors of main tip 13b5484a53c96aa7def389b09ccf65c05187337b. The #1313 static-slot/attach package entry is present. The #1326 mutation-reproof and #1327 lease-renew changesets declare no packages and therefore correctly produce no package CHANGELOG entry.

I did not install node_modules and did not run suites for this release-diff sanity review.

[davidfarah2003]

APPROVE at 2798a3f8df08c389d464ea932e12ee5290c580ea. Sanity review of the version/CHANGELOG diff, not a code review.

Did not pnpm install. Did not run suites. Confirmed this sha contains main tip 13b5484a53c96aa7def389b09ccf65c05187337b (#1327). Compared origin/main...origin/pr-1305.

Lockstep: all 21 fixed-group packages move 0.45.0 -> 0.46.0 together (cotal-ai, core, workspace, lang, runtime, cli, manager, delivery, web, cmux, orca, tmux, herdr, connector-core, connector-claude-code, connector-hermes, connector-jcode, connector-opencode, connector-codex, pi, auth). None left behind. Packages are 0.x, so the breaking hosted-runs change (18a0024 feat!) is a MINOR, not a major. No 1.x.

CHANGELOG 0.46.0 matches merged work: 9d745af (#1294 custody seam), 18a0024 (#1296 hosted runs), e986173 (#1313 static-slot/attach). Last-night #1326 and #1327 are test-only empty changesets (no package list), so they correctly add no user-facing CHANGELOG lines and are deleted by the bot.

Only non-changelog / non-package.json / non-changeset path: extensions/connector-core/src/docs-bundle.generated.ts, one line, "version": "0.45.0" -> "0.46.0". Version stamp of the bundled docs, not a behavior change. Naming it because this review asks for anything that is not a bump or a CHANGELOG line. Not a block.

package.json diffs are version fields only. Remaining .changeset on the branch is README + config.json. Mutation reproof / CI / Windows / unit / smoke shards green on this sha.

[davidfarah2003]

Public-release acceptance supplement. Verdict remains APPROVE at 2798a3f8df08c389d464ea932e12ee5290c580ea.

I validated the result through the customer-facing npm interface rather than only reading the release diff:

• all 21 public fixed-group packages are available from the public registry at 0.46.0
• npm pack cotal-ai@0.46.0 downloaded the actual release tarball without installing it
• its package metadata exposes cotal as ./dist/cotal.js
• its eight first-party runtime dependencies are all pinned to 0.46.0, including @cotal-ai/runtime
• the downloaded tarball's SHA-512 exactly matches npm's published dist.integrity
• repository tag v0.46.0 resolves to merge 74f7eeb09866abb0c5128dd4c20415f75c45d6a9, whose parent 2 is the approved head

Observed outcome: the reviewed lockstep version change reached the public registry as an integrity-verifiable, core-matched package closure. This closes the release acceptance loop that a manifest-only review could not.

I did not install or execute the package, start a stack, or run a live suite.

[davidfarah2003]

Whole-result feedback-loop supplement. Verdict remains APPROVE at 2798a3f8df08c389d464ea932e12ee5290c580ea.

I reran one coherent check over the earlier release-diff review and the final public outcome.

The merge result reported:

• merge parent 2 is the reviewed head
• 24 package manifests, all version-only
• 24 CHANGELOG files, additions only under the reviewed release rule
• exactly 5 consumed changesets
• exactly 1 generated docs-bundle version stamp
• 0 paths outside those four permitted classes
• all 21 fixed public packages at 0.46.0
• generated docs bundle at 0.46.0

The customer-facing publication check then reported:

• all 21 fixed public package names resolve from npm at 0.46.0
• the downloaded cotal-ai@0.46.0 tarball matches npm's SHA-512 integrity
• its first-party runtime dependency closure is pinned to 0.46.0
• tag v0.46.0 resolves to merge 74f7eeb09866abb0c5128dd4c20415f75c45d6a9

Observed conclusion: the earlier diff classification and the eventual public release agree. The release contained only the permitted generated classes and reached customers as the reviewed lockstep version. No contradictory observation emerged.