[nissa-seru]

This is the 0.22.2 release commit, cut with npm version patch from main at 7125cb86, which is 0.22.1 plus the 24 changes merged since, through #377. Among its fixes are the ways a stdio MCPL server could end its host or leave stop() waiting for ever: a child ended by a signal the transport didn't send, such as an OOM kill (#331), a command that can't be spawned (#336), and an error on the child's stdin or stdout. Context maintenance now fails one agent at a time and holds still while an operator surgery or switchBranch moves the store, and stop() waits for an operator's operation that is already running.

Anarchid's review of #372 asked for any further 0.22.x patch to go out before #372 merges, and this is that patch.

What this branch is

• 64894b17 corrects four fragments before they're folded:
  • mcpl-transport-close and mcpl-transport-spawn take the corrections that Anarchid's review of fix(mcpl): no hang after a signal kill, no uncaught transport or spawn errors #344 asked for in R1-2 and R1-4, as fix(mcpl): SIGTERM a stdio child whose stdin or stdout fails #384's description said the release commit would.
  • mcpl-transport-pipe-error now starts from 0.22.1, where an error on the child's stdin, stdout or stderr was thrown as an uncaught exception, and fix(mcpl): no hang after a signal kill, no uncaught transport or spawn errors #344's third bullet, which described main between fix(mcpl): no hang after a signal kill, no uncaught transport or spawn errors #344 and fix(mcpl): SIGTERM a stdio child whose stdin or stdout fails #384, goes.
  • typescript-7's counts of the source maps that change were measured again on this tree, and hold.
• 63b6feb9 adds an operator section to ## Unreleased: what the first passes after upgrading do on a workspace mount over 5000 files, and the one kind of stored setting that stops 0.22.1 from starting, with its remedy.
• fe2898b9 is npm version patch's commit. It folds the 22 fragments into ## 0.22.2 — 2026-10-17, with the operator section at its top, and sets the version.

It's cut from 7125cb86, so changes merged after that commit aren't in it. #372 and #400 are among the open pull requests that carry breaking entries, and once one of them merges, npm version refuses another 0.22.x from main. Merged back, this PR gives main the version and the folded changelog. It changes only CHANGELOG.md, package.json's version and the 22 fragments it deletes.

Why a patch, and all of main

• None of the 22 fragments is breaking: three are added, two changed and seventeen fixed. npm version's check for a pending breaking entry (build(release): while a breaking entry is pending, a new version must open a line no release has reached #348) passed, so the release is a patch, which ^0.22.1 takes. connectome-host 0.10.2 declares ^0.22.1, so an npm install of the host resolves to this release, while a checkout keeps the 0.22.1 its lockfiles name until they move.
• 7125cb86 is the tree that was tested together:
  • CI passed on main at that commit.
  • A cross-package run built agent-framework at that tree with the main branches of its dependencies and of connectome-host, context-manager's 0.15.0 among them, ran connectome-host's 1,826 tests and two boots against it, and loaded stores written by connectome-host 0.3.1 through 0.10.2.
  • The full suite passed on this release's code, with context-manager 0.14.1, membrane 0.5.87 and chronicle 0.4.0 from npm, as an install of this release resolves them: 2,434 of 2,434 tests on Node 20 and on Node 24, each file run on its own. Under npm test's --test-force-exit, Node 24 ran 2,424 of them, since the flag ends four files before their last tests (npm test's --test-force-exit can end a test file before its tests report, so a short run still passes #294).
• 0.21.3, npm's release-0.21, requires context-manager ^0.15.0, while this release still requires ^0.14.1, so a host moving from it to 0.22.2 takes context-manager back to 0.14. In a probe, a store the published 0.21.3 wrote on context-manager 0.15.0 opened under this release's code on 0.14.1: an autobiographical resident's messages, L1 summaries and summary-id counter came through, and turns and maintenance ran. It opened again back on 0.21.3. Not tried: merged levels, a store whose load repair 0.15 changed, kv-unified, or connectome-host.

Going back

A probe installed the packed candidate on its own, with the published 0.22.1 beside it, both on context-manager 0.14.1, and walked stores from the candidate to 0.22.1 and back. Going back is safe for a store 0.22.2 wrote, with one exception, which the operator section names with its remedy: 0.22.1 refuses to create the framework when an agent's persisted runtime setting is one that 0.22.2 keeps set but unapplied. Resetting that setting under 0.22.2 first let 0.22.1 start. 0.22.1 keeps #290's new contextBudgetReachedTokens key in the persisted settings, and 0.22.2 trusts it only when it equals the stored budget. The operator section also says what the probe didn't cover.

Checks

• No open issue is labelled release-hold, and npm version checked again before it bumped anything (build(release): an open release-hold issue stops the release #329).
• The package packed from this release's code installs on its own in an empty directory, with its dependencies from npm, and loads under Node 24 and bun 1.4.3 (scripts/pack-installs-alone.mjs, build(release): install the packed release on its own before publishing, and on pull requests #349). The publish workflow runs the same check before it publishes.

— Ada-1017 (Claude Opus 5.5). Hilda-2681 read the notes against the code at v0.22.1 and at this tree, and each entry's "before" wherever an earlier merge in this release could have touched the same code. Gladys-2413 planned going back, ran its probe and drafted the operator section.

[greptile-apps]

Confidence Score: 5/5

[Low impact] This release-only PR appears safe to merge.

Summary

Prepares the 0.22.2 release without changing runtime code.

• The package and changelog now identify release 0.22.2.

_{Reviews (1) · Last reviewed commit: "0.22.2" · Reviewed by Greptile}