@cardinal4/opencode-fold-diffs 0.3.1 → 0.3.3

package/README.md

@@ -1,8 +1,15 @@
 # opencode-fold-diffs
 
+> [!IMPORTANT]
+> **This is a fork, and it exists for one reason: OpenCode V2 support.**
+>
+> The original plugin is **[Tanner Bruhn](https://github.com/tannerbruhn)**'s [`tannerbruhn/opencode-fold-diffs`](https://github.com/tannerbruhn/opencode-fold-diffs) (npm: `opencode-fold-diffs`) — the **OpenCode V1** plugin, whose V1 implementation does not run in V2. This fork — [`cardin/opencode-fold-diffs`](https://github.com/cardin/opencode-fold-diffs), published as [`@cardinal4/opencode-fold-diffs`](https://www.npmjs.com/package/@cardinal4/opencode-fold-diffs) — ports it to **OpenCode V2** (the `@opencode/cli` 2.x line, `opencode v2.0.x`). Install this fork if you are on V2; install upstream if you are on V1.
+>
+> **All credit for the original plugin goes to [Tanner Bruhn](https://github.com/tannerbruhn).** This fork is unofficial and independent: Tanner has not reviewed it, does not maintain it, and does not endorse it. Report bugs in this fork here, not upstream.
+
 **Every `write` and `edit` dumps the whole file or the whole diff into your transcript, and stays there.** This plugin folds those blocks down to their header line — `# Wrote 40 lines · click to expand  src/app.ts` — and opens them again on click, or with a fold/unfold-all key if you configure one.
 
-This branch targets **OpenCode V2** (the `@opencode/cli` 2.x line, `opencode v2.0.x`). The V1 plugin implementation does not run in V2; see [Migrating from V1](#migrating-from-v1).
+The V2 port is not a re-host: it follows V2's new plugin API and render tree, so the V1 code cannot be reused. See [Migrating from V1](#migrating-from-v1) for what changed.
 
 ## What V2 already folds
 
@@ -117,14 +124,15 @@ The V2 TUI plugin API (`@opencode/plugin/tui`) has no slot for message parts, so
 
 Renderable classes are matched by duck-typing (`typeof node.diff === "string"`, `content` + `filetype` for code) rather than `instanceof`, because the opentui classes are minified in the shipped binary and their names are not stable.
 
-Blocks are re-scanned on `message.part.updated` and `message.updated`, plus a 2 s sweep that catches a session opened from history, whose parts land before any event this plugin sees.
+Blocks are re-scanned on V2's `session.message.content.updated`, `session.tool.success` and `session.tool.failed`, plus `session.step.ended` and `session.execution.succeeded` (`session.shell.ended` joins them when `bash` folding is on). A 2 s sweep catches a session opened from history, whose parts land before any event this plugin sees.
 
 ## Migrating from V1
 
-V1 plugin implementations do not run in V2. This branch made these changes:
+V1 plugin implementations do not run in V2. The V2 port made these changes:
 
 - Entrypoint is a `{ id, setup(context) }` definition (`Plugin.define()` is an identity helper, so the shape is the same). `setup` returns the cleanup function instead of `api.lifecycle.onDispose`.
 - `api.renderer` → `context.renderer`; `api.route.current.name` → `context.ui.router.current().type`; `api.event.on` → `context.data.on`; `api.ui.toast` → `context.ui.toast.show`; `api.keymap.registerLayer` → `context.keymap.layer`.
+- Event names are V2's: `message.updated` / `message.part.updated` are legacy schemas in V2 and are never emitted. The plugin listens to `session.message.content.updated`, `session.tool.success` / `session.tool.failed`, `session.step.ended` and `session.execution.succeeded` (plus `session.shell.ended` when bash folding is on). These names exist from 2.0.10 on, so older V2 installs get the same fix without upgrading.
 - Tool headers are no longer one string. V1 rendered `"← Edit src/app.ts"`; V2 renders a label node plus a path node, so detection and the stats suffix target the label.
 - `bash` defaults to `false`, because V2 now trims long commands to two lines itself.
 - Config moves from `tui.json` to `cli.json` (or `opencode.json(c)`).
@@ -146,7 +154,7 @@ V1 plugin implementations do not run in V2. This branch made these changes:
 
 ## Status
 
-Written against **opencode v2.0.10 / v2.0.11**. The tree-walking, block matching, fold/unfold and toggle logic run green against a mock renderer tree shaped like V2's (`node --test`), and the fold was checked against a real transcript: `visible = false` (Yoga `display: none`) is what actually hides a body, not `maxHeight`.
+Written against **opencode v2.0.24**, and compatible across the V2 line: the `session.*` events this version listens to exist from v2.0.10 on, so an older V2 install gets the fix without upgrading. The tree-walking, block matching, fold/unfold and toggle logic run green against a mock renderer tree shaped like V2's (`node --test`), and the fold was checked against a real transcript: `visible = false` (Yoga `display: none`) is what actually hides a body, not `maxHeight`.
 
 Edits with fewer than `min_lines` changed lines (default 6) are left expanded on purpose — a one-line change is already its own summary. Set `min_lines: 0` to fold every file block.
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@cardinal4/opencode-fold-diffs",
-  "version": "0.3.1",
-  "description": "OpenCode V2 TUI plugin: write, edit and apply_patch blocks render folded to their header line, click or ctrl+o to open them.",
+  "version": "0.3.3",
+  "description": "Unofficial OpenCode V2 fork of opencode-fold-diffs: write, edit and apply_patch blocks render folded to their header line, click to expand.",
   "license": "MIT",
   "type": "module",
   "keywords": [

package/tui.js

@@ -10,15 +10,15 @@
 // closed without one, so this does it from a plugin.
 //
 // A folded block renders as its header line -- "# Wrote 40 lines · click to
-// expand  src/app.ts" -- and opens on click, or with ctrl+o for every block at
-// once.
+// expand  src/app.ts" -- and opens on click, or with the optional `key`
+// binding for every block at once.
 //
 // Options (cli.json -> ["opencode-fold-diffs", { ... }] or opencode.json(c)):
 //   lines      lines of the body left visible when folded  (default 0, title only)
 //   min_lines  leave blocks with fewer content lines alone  (default 6)
 //   stats      append "40 lines · click to expand" to the header (default true)
 //   folded     new blocks start folded                      (default true)
-//   key        binding that folds/unfolds every block        (default "ctrl+o")
+//   key        binding that folds/unfolds every block        (default "", none)
 //   bash       fold long bash commands too                   (default false on V2)
 //   bash_lines rows of the command left visible when folded  (default 1)
 //
@@ -420,10 +420,18 @@ export default {
       }, 120);
     }
 
-    const offs = [
-      context.data.on("message.part.updated", schedule),
-      context.data.on("message.updated", schedule),
+    // V1's message.part.updated / message.updated are legacy schemas in V2 --
+    // the client emits the session.* events instead, so the V1 names were a
+    // silent no-op and a new block only folded on the sweeping timer.
+    const events = [
+      "session.message.content.updated", // a part was appended or replaced
+      "session.tool.success", // a tool body (diff or file) appeared
+      "session.tool.failed", // a failed tool still renders its block
+      "session.step.ended", // the step's final content has arrived
+      "session.execution.succeeded", // the turn settled; take a final look
     ];
+    if (shell) events.push("session.shell.ended"); // the command now carries its "$ " prefix
+    const offs = events.map((name) => context.data.on(name, schedule));
     const timer = setInterval(sweep, SWEEP_MS);
     schedule();