v0.2.42.0 fix: Cycle 0052 pt3: a live test run survives a value it cannot read, and a browser run's refusals and seals say what happened

CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## [0.2.42.0] - 2026-10-26 (development candidate)
+
+Cycle 0052 pt3 ([Issue #124](https://github.com/laststance/codebook/issues/124)), the last of three pull requests of a bug-fix cycle: a live test run survives a value it cannot read, and a browser run's refusals and seals say what happened.
+
+**A live test run keeps going past a value it cannot read.**
+
+- **A value the chat asks for at a test stop is read also when it is a name the stopped file imports**, such as `revalidatePath.mock.calls.length` of a mocked `next/cache` or a mocked database client's `db.insert.mock.calls`: Codebook reads it through the module Vitest binds it to, as the export the file's import declaration names, so an alias reads its module's original export and a default import its default export, each from that declaration's own module, never from another module that happens to export the same name; a name the file does not import, or an import whose module the stop cannot see, stays unavailable rather than guessed. A getter on the asked path runs once, as it does when you expand it in the Variables view.
+- **A required value that still cannot be read no longer ends the run.** The stop keeps its other values and names the missing one, and the continuation that reached it (the chat's `codebook_continue`, or your Continue in the Study pane) answers `EVIDENCE_UNAVAILABLE` naming it while the run stays paused there, so it can go on without it or stop the run; `codebook://help/errors` says so in its recovery. A getter the debugger cannot expand, or expands to no single value, leaves only its own value unavailable (never its `(...)` placeholder), and a local variable keeps priority over an import of the same name even when its value cannot be read.
+- **A run that went on without a required value seals its history partial**, with a reason that names the value and its stop: the study reads partial although the test passed.
+
+**A browser run says where a stop can go and why it ended.**
+
+- **A stop in another page's component** (one a link from the launched page navigates to) is refused before input with a sentence that names the stop's file and the launched page, and says to start the run at the stop's page (`entryPath`) or to choose a stop in the launched page's own components.
+- **A run refused during its preparation, or failed later, seals its recording with that failure's own words** (`The run failed: <cause>. Recorded prefix retained.`, a long cause cut so that the sentence keeps its end), not as an interrupted run; a run whose release did not complete keeps `Runtime cleanup incomplete; recorded prefix retained.`
+- **A browser replay whose open fails** also writes one `open:recording` entry to **Output › Codebook**, with the study, the profile and the cause.
+
+**Other fixes.**
+
+- **A node-history reference with an unknown study id** (a mistyped id, for example, or a history removed while it is read) is refused as `NOT_FOUND`, naming the id and telling the agent to copy the `studyId` or `historyUri` from `codebook://node-history`, instead of a failed operation with a raw file error.
+- **Update anyway chosen right after this window's own update run ended** starts the update: it waits for that run's marker change instead of refusing itself as another window's update.
+
+**Compatibility.** The MCP API stays 1.8, the bundled skill is unchanged (1.0.47) and no stored format changes. This closes Issue #124's tasks; nothing is carried.
+
 ## [0.2.41.0] - 2026-10-25 (development candidate)
 
 Cycle 0052 pt2 ([Issue #124](https://github.com/laststance/codebook/issues/124)), the second of three pull requests of a bug-fix cycle: a test replay's moves, notices and summary page.

README.md

@@ -16,7 +16,7 @@ Codebook contributes `debug.focusEditorOnBreak: false` as the native debugger de
 
 ## Implementation status
 
-This is a preview, not a Marketplace or Open VSX release. The delivered version is **0.2.41.0** once the second pull request of [Cycle 0052](https://github.com/laststance/codebook/issues/124) is merged; until then 0.2.40.0 ([PR #125](https://github.com/laststance/codebook/pull/125)) is the delivered one, and the active cycle Issue says where the delivery stands. Cycle 0051 opened a test replay in the learning-replay composition a browser replay has: the Learning summary in the chat's place, one transport for both replay families, and a Learning summary button that shows a hidden summary again. Cycle 0052 is a bug-fix cycle that closes every defect Cycle 0051 carried, in three pull requests: the first makes replays leave, open and reload without stale frames and makes their entries and exits behave as the learner chose; the second fixes a test replay's moves and its summary page; the third the live runtime's unreadable facts, a browser run's refusals and the tests' hygiene. The MCP API is 1.8. What each earlier cycle delivered, with its tests, trials and limits, is in the [change history](CHANGELOG.md) and in that cycle's record, kept under the tag [`docs-archive-2026-10-20`](https://github.com/laststance/codebook/tree/docs-archive-2026-10-20/docs/cycles); from Cycle 0048 on, the cycle's Issue holds its tasks and state, and its pull requests the results.
+This is a preview, not a Marketplace or Open VSX release. The delivered version is **0.2.42.0** once the third pull request of [Cycle 0052](https://github.com/laststance/codebook/issues/124) is merged; until then 0.2.41.0 ([PR #126](https://github.com/laststance/codebook/pull/126)) is the delivered one, and the active cycle Issue says where the delivery stands. Cycle 0051 opened a test replay in the learning-replay composition a browser replay has: the Learning summary in the chat's place, one transport for both replay families, and a Learning summary button that shows a hidden summary again. Cycle 0052 is a bug-fix cycle that closes every defect Cycle 0051 carried, in three pull requests: the first makes replays leave, open and reload without stale frames and makes their entries and exits behave as the learner chose; the second fixes a test replay's moves and its summary page; the third the live runtime's unreadable facts, a browser run's refusals and the tests' hygiene. The MCP API is 1.8. What each earlier cycle delivered, with its tests, trials and limits, is in the [change history](CHANGELOG.md) and in that cycle's record, kept under the tag [`docs-archive-2026-10-20`](https://github.com/laststance/codebook/tree/docs-archive-2026-10-20/docs/cycles); from Cycle 0048 on, the cycle's Issue holds its tasks and state, and its pull requests the results.
 
 The specification is [goal version 10](PRODUCT_GOAL.md), and the implementation targets external repositories. Historical fixture or coupled-Wiki success is not proof of that destination.
 

VERSION

@@ -1 +1 @@
-0.2.41.0
+0.2.42.0