- `extension-create` and `extension-install` move from 4.1.32 to 4.1.33, the version `extension-develop` already ran on, so the nightly engine-pin check reads all three engines as current.
- CI runs the canary cell on stable when npm's canary tag is behind it (the tag sat on 4.1.31-canary while stable was 4.1.33), so a stale canary no longer reds the required `verify (canary)` check on a golden the pinned engine already changed.
- The generated tool reference moves from `claude/rules/mcp-tools.md` to `claude/reference/mcp-tools.md`. At 71k characters it restates the schemas the server already sends, and anyone who copied `claude/rules` into a project as Claude Code rules loaded it into every session; two such copies on one path (a workspace folder and a project in it) crossed Claude Code's 150k instruction limit and painted a warning naming the file. `claude/rules` now holds only the two hand-written rules, and a test keeps that folder under 10k characters.
- `extension_start` and `extension_wait` on a production session say what they read and never point at a file: the answer carries `browserPid` and `browserAlive` from the contract the launcher stamps, `extensionLoaded: null` with `loadEvidence` saying plainly that a production launch opens no debug port and carries no dev bridge (so `extension_logs` has no stream for it and the load itself is unread), and names `extension_dev` for a proven load; the `/var/folders/.../session.log` path left the answer.
- `extension_stop` says what it ended: the answer carries `serverGone`, the `browserPid` the launcher recorded in `ready.json` and `browserGone`, and its detail reads "Ended: the server (pid N) is gone; the browser the launcher recorded (pid M) is gone" (or that no browser pid was recorded, or that a build-only session launched none); a browser still alive keeps `stopped` false.
- `extension_wait` answers with every port the session bound, read from the contract: `port` (the dev server), `controlPort` (the control channel) and `cdpPort` (the browser's debug port on Chromium) or `rdpPort` (on Gecko), or `debugPortNote` when the session opened none; `extension_dev`'s ready block inherits them.
- `extension_add_feature`'s description is the trigger: it names the asks it answers (add an options page, a popup, a side panel, a content script, a devtools panel, a new tab page or a background script), says it plans the surface and the agent writes what the plan says, and hands the follow-up to the manifest check and `extension_dev`.