scenescout 3.22.0 → 3.23.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # scenescout
 
+## 3.23.1
+
+### Patch Changes
+
+- cc303ee: `scout_close` no longer lets a tool call that timed out write into the project after it has answered. It closes the browser, waits up to 10 seconds for such calls to finish, then writes any save they left pending; if one is still running at the end of the wait, the reply says so. `SCENESCOUT_WATCHDOG_MS` caps how long any tool call may run before it is answered as timed out.
+
+## 3.23.0
+
+### Minor Changes
+
+- ed24973: Start a run from an earlier run's record, opt-in. Every run that writes its report now keeps a record of what it worked on and left (routes in order, each session's steps, and on each route the controls never exercised, forms never submitted and options never chosen), in the project's memory and in `ci.json` under `record`. `scenescout ci --from-run <ci.json or project directory>` (or `SCENESCOUT_FROM_RUN`) with `--from-run-mode continue` (the default) takes first the routes that run never worked on, then the ones it left work on, told exactly what to do first on each, then the rest, reaching a page the earlier run got to by acting on another page through the same steps; a run takes on only its budget's worth of pages (`--from-run-turns-per-page`, default 7 turns a page) and the next continued run takes the pages after them; `--from-run-mode replay` follows its routes and steps in order, one lane per session it had. `scout_lane_brief` takes `fromRun` and `fromRunMode`, the ci action takes `from-run` and `from-run-mode`, and the run it started from is named in the report, `summary.md` and `ci.json` (`fromRun`). Without it, runs behave as before.
+
 ## 3.22.0
 
 ### Minor Changes