@brutalsystems/muster 0.7.2 → 0.7.3

package/CONTRACT_PROVENANCE.md

@@ -79,6 +79,35 @@ the same codename remediation via a history rewrite (`git filter-repo
 whose content or ancestry it touched. This is a historical acquisition
 record, not a claim that the commit is still reachable.
 
+## Contract baseline moved to 0.6.0 — 2026-09-20
+
+Tin Can 0.6.0 changes the endpoint it delivers to on the opencode leg, from the
+v2 `/api/session/{id}/prompt` to the v1 `/session/{id}/prompt_async`, and the
+change resolves the failure described in the 0.5.9 entry below. It is a minor
+rather than a patch because `urgent` was removed as a capability: the v1 route
+has no equivalent of v2's steer/queue distinction, so rather than accept it and
+ignore it, Tin Can now reports urgent as unsupported on every runtime. Muster
+never referenced that capability, so nothing here changes.
+
+Muster's contract suite was run against a real installed
+`@brutalsystems/tincan@0.6.0` and passed all four cases. Naming is untouched:
+0.6.0's `canonical-id.json` was compared case by case with Muster's frozen copy
+and every pre-existing case is present with an unchanged expectation, with the
+same four additive opencode-specific cases introduced in 0.5.7.
+
+Verified end to end rather than by the suite alone: a Muster-launched OpenCode
+session in a terminal received a Tin Can message, ran the turn, and replied to
+the sending Claude Code session. The OpenCode log for that session shows a
+started loop and a resolved model with no `Failed to drain` line, which is the
+signature the 0.5.9 entry documents as the failure.
+
+One operational trap worth recording, because it makes a working setup look
+broken: the OpenCode plugin is a **copy on disk** under
+`~/.config/opencode/plugin/`. Updating the npm package does not update it, and
+a stale plugin keeps posting to the old v2 route. The peer registry records
+`plugin_version`; confirm it matches the installed package before trusting a
+delivery result.
+
 ## Contract baseline moved to 0.5.9 — 2026-09-20
 
 Re-pinned from `0.5.7`, skipping a separate `0.5.8` pass, because the `notice`

package/README.md

@@ -413,18 +413,18 @@ The ordinary suite requires tmux, node-pty, POSIX `ps`/`lsof`, and Python 3 for
 real file locks in the fake Codex executable. It uses isolated runtime homes and
 no model APIs. It skips the four explicitly invoked compatibility cases.
 
-The verified contract baseline is **Tin Can 0.5.9**. The suite spawns an installed binary as an MCP
+The verified contract baseline is **Tin Can 0.6.0**. The suite spawns an installed binary as an MCP
 subprocess, compares durable IDs, and verifies delivery to fake runtimes through
 both terminal hosts. A missing binary or missing durable field fails the test.
 For reproducible verification, install that exact release outside Muster:
 
 ```sh
 contract_dir=$(mktemp -d)
-npm install --prefix "$contract_dir" --no-save @brutalsystems/tincan@0.5.9
+npm install --prefix "$contract_dir" --no-save @brutalsystems/tincan@0.6.0
 MUSTER_TINCAN_BIN="$contract_dir/node_modules/.bin/tincan" npm run test:contract
 ```
 
-Verification uses the published 0.5.9 release installed in an isolated
+Verification uses the published 0.6.0 release installed in an isolated
 temporary directory. No Tin Can source edits are made.
 Fixture version metadata alone does not indicate address-format drift: compare
 the case arrays. Those arrays cover naming only, not peer-list membership or

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brutalsystems/muster",
-  "version": "0.7.2",
+  "version": "0.7.3",
   "description": "Launch instructed, reachable local agent sessions",
   "type": "module",
   "engines": {