@basein/runner 0.2.11 → 0.2.12

package/docs/quickstart.md

@@ -168,7 +168,7 @@ its prompt, its tool calls and its final answer.
 |---|---|
 | `~/.baseinstrunner/config.json` | the service address; `BIR_AUTH_URL` in the environment overrides it, and `bir setup` warns when the two differ |
 | `~/.baseinstrunner/credentials.json` | the cached session, bound to the service that issued it |
-| `~/.baseinstrunner/installed.json` | the original text of every file it rewrote, and each project's port, token and replay switches |
+| `~/.baseinstrunner/installed.json` | the original text of every file it rewrote, and each project's port, token and replay switches, and whether Claude's `bir` tools may change scenarios there (`bir scenario editing on`) |
 | `~/.baseinstrunner/logs/<key>.log` | the recorder's audit log, one file per project |
 | `~/.baseinstrunner/node/` | a private Node, only if the machine had no usable one; not on PATH |
 | `~/.baseinstrunner/npm/` | the runner package |
@@ -256,9 +256,49 @@ answer. Then:
 For a turn that did not do what you expected — a scenario that did not run, a
 saving that was not made — `bir investigate` reads the journal and the service
 and says why. When it names a step whose code is wrong, you can fix that step
-yourself with `bir scenario edit` (not yet released) — see
+yourself: see the next section.
+
+---
+
+## Fixing a step (not yet released)
+
+Built 2026-09-25. It needs the next `@basein/runner` version and a service
+deploy, so it does not work yet. The full guide, with real output, is
 [calculatedReplayGuide.md](calculatedReplayGuide.md) §9.2.
 
+A calculated step is code. When `bir investigate` says a step's code is wrong,
+you can change that step. The service checks your change against the
+recording. It saves it only if it gives the same call the recording made, and
+is not a pasted copy of that call. Only the owner of a scenario can change it.
+
+1. **Read the step.** `bir scenario show scn_… --step 4` (the `scn_` id and the
+   step number are the ones `bir investigate` printed).
+2. **Write the new code to a file,** for example `step4.js`. Never on the
+   command line: the shell breaks JavaScript.
+3. **Check it.** `bir scenario check scn_… --step 4 --input-logic step4.js`.
+   Nothing is saved. You should see `input    reproduces the recorded call`.
+4. **Save it.** `bir scenario edit scn_… --step 4 --input-logic step4.js --note "why"`.
+   You should see a line that starts `Saved as sedit_…`.
+5. **Changed your mind?** `bir scenario undo scn_…` takes back the newest
+   change. Run it again to go one further back. With `--step 4` it takes
+   back only step 4's changes, newest first. An undo that would break a later
+   step or the final answer is refused (`undo_refused`).
+
+If the check refuses your change, it says why. For example, the `input` line
+says where your call differs from the recorded one. Fix the code and check
+again. `--force --note "why"` saves it anyway, but use it only when the
+recording itself was wrong.
+
+The saved code runs on your machine without asking you, like the code the
+calculation wrote. The check only tests what it sends for the recording's
+values. So read the code before it is saved, yours or Claude's.
+
+Claude can do this for you. Ask it in the session; it runs the same commands,
+and Claude Code asks you before each one, unless you allowed it. Or run
+`bir scenario editing on` in the project folder and restart Claude Code: the
+`bir` server then also offers tools that change a scenario. These `bir` calls
+are never recorded as part of your task.
+
 ---
 
 ## Where to go next

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@basein/runner",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "description": "A recording MCP proxy: sits between any MCP client and its MCP servers, executes each call on the client's behalf, and records the run as a reusable BaseIn scenario.",
   "type": "module",
   "license": "MIT",