@aistastudio/myc 0.3.10 → 0.3.11

package/README.md

@@ -26,9 +26,23 @@ the build.
 
 ## Requires Bun — this is not fine print
 
-The runtime is bound to `bun:sqlite` (SQLite and `sqlite-vec` ship inside Bun,
-with no native bindings on the Node side). **It will not start on plain Node.js
-or Deno.** Bun ≥ 1.3.0 is required and pinned in `package.json` → `engines.bun`.
+The runtime is bound to `bun:sqlite` (no native bindings on the Node side).
+**It will not start on plain Node.js or Deno.** Bun ≥ 1.3.0 is required and
+pinned in `package.json` → `engines.bun`.
+
+**SQLite ≥ 3.44.0.** Below 3.44.0, FTS5 cannot be written from triggers under
+`trusted_schema = OFF`, so every write fails. On Linux, Bun links its own SQLite
+(3.53.0 in Bun 1.3.14). On macOS, Bun uses the system SQLite — 3.43.2 on
+macOS 14 — so the package ships its own: `vendor/sqlite/libmyc-sqlite3.dylib`,
+SQLite 3.53.4 built from the official amalgamation for arm64 and x86_64
+(`scripts/build-sqlite.ts`), chosen before anything else except an explicit
+`MYC_SQLITE=/path/to/libsqlite3.dylib`. If the SQLite in use is still below
+3.44.0 — a broken install, or `MYC_SQLITE` pointing at an old library — every
+command, `myc init` included, refuses with `precond.sqlite_unsupported` and says
+what to do, instead of creating a workspace it cannot write to. From 3.44.0 up
+to 3.51.2 myc works but warns (`WARN degraded.sqlite_old`): parallel processes
+may run a background job more than once; on Linux the cure is `bun upgrade`.
+`myc doctor` names the SQLite in use and where it came from.
 
 Install Bun: https://bun.sh
 
@@ -37,8 +51,8 @@ Install Bun: https://bun.sh
 Installation is one command:
 
 ```bash
-bun install -g @aistastudio/myc   # 3.42 MB compressed, 12.58 MB unpacked, 13 files; no models pulled
-myc --version                     # myc 0.3.10 (schema 1)
+bun install -g @aistastudio/myc   # 5.05 MB compressed, 15.59 MB unpacked, 16 files; no models pulled
+myc --version                     # myc 0.3.11 (schema 1)
 ```
 
 It runs on macOS and Linux. On Windows, use WSL and install Bun and myc inside
@@ -97,6 +111,7 @@ myc wire --status-line          # + myc's status line under Claude Code's prompt
 myc wire --queue-hook           # + heavy commands take turns (below)
 myc wire --agents-md            # + the myc block in AGENTS.md
 myc wire --scope user           # the same for agents in git worktrees (Claude Code's user layer)
+myc wire --scope user --agents claude,opencode  # + opencode's global config
 myc unwire                      # remove what wire put in
 ```
 
@@ -118,6 +133,20 @@ workspace the MCP server offers zero tools and no instructions. `--hook-mode
 replace` is refused here. The journal is `~/.myc/wire-user.json`; `myc unwire
 --scope user` restores the settings node by node and removes the MCP server.
 
+opencode in such a worktree is in the same position, and `--agents opencode`
+(or `claude,opencode`; without `--agents` the user layer is Claude Code's only)
+wires its global config, `$XDG_CONFIG_HOME/opencode` or `~/.config/opencode`:
+the `myc` server goes into `mcp` of the `opencode.json[c]` opencode itself treats
+as its own, as one node — the file is JSONC, and other entries, comments and
+trailing commas stay byte for byte — and `plugin/myc.ts` goes next to it. opencode
+starts that server in the directory it was opened in, so `myc mcp` finds the
+workspace from a worktree by itself. The plugin makes the same two checks as the
+helper, once per project and without starting myc: no workspace here, or the
+project wires opencode itself (`opencode.json` with `mcp.myc`, or
+`.opencode/plugin/myc.ts` — opencode loads the plugins of both layers, and a
+project's `mcp.myc` overrides this one) — then it registers no hooks at all.
+`myc unwire --scope user` takes out exactly that node and the plugin.
+
 With `--status-line` the user layer also gets myc's status line, `myc
 statusline --scope user`: in a myc workspace — a git worktree of one included —
 it is the full line, outside one it prints nothing of its own. The line that was
@@ -134,7 +163,7 @@ unwire --scope user` puts the previous line back byte for byte. `myc doctor
 --hooks` checks the whole user layer against the journal: myc's hook entries and
 rules still in `~/.claude/settings.json`, the helpers exactly what this build
 writes (a stale one is named with the build that wrote it), the status line, the
-MCP server.
+MCP server — and, when opencode is wired, its plugin and `mcp.myc`.
 
 ## Heavy commands take turns
 
@@ -431,8 +460,9 @@ last-writer-wins over whole records.
 
 **Guards are proved by mutation.** Every refusal and every invariant is
 accompanied by a mutation that removes it; a guard whose removal breaks no test
-is treated as absent. The full suite: 3672 pass / 0 fail / 16 skip
-(`bun test`, 2026-09-11).
+is treated as absent. The full suite: 3790 pass / 1 fail / 16 skip
+(`bun test`, 2026-09-15; the one failure is the queue hook's latency budget —
+p99 46 ms against 30 ms on a loaded laptop, the hook itself unchanged since 0.3.10).
 
 ## What myc does