v0.2.47.0 fix: Cycle 0056 pt1: an LLM Wiki start says when it joins, stops or passes its bound, and releases or writes back what it claimed

.github/workflows/storage-locks-windows.yml

@@ -113,6 +113,7 @@ on:
       - extension/src/utils/judgeLeftEmpty.ts
       - extension/src/utils/listFolderTreeWithoutFollowing.ts
       - extension/src/utils/listPlacedClaims.ts
+      - extension/src/utils/longestWikiRunMs.ts
       - extension/src/utils/modifiedAtMsOf.ts
       - extension/src/utils/namesMachineInClear.ts
       - extension/src/utils/newStagedConfigPath.ts

CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## [0.2.47.0] - 2026-10-27 (development candidate)
+
+Cycle 0056 ([Issue #135](https://github.com/laststance/codebook/issues/135)), a bug-fix cycle, first of its three pull requests: the LLM Wiki run lifecycle says what happens on a joined, stopped or bounded start and releases what it claimed. The LLM Wiki view and the reader (second pull request) and the Cursor test-replay fix with the native trial N56 (third) follow.
+
+**Starting and stopping an LLM Wiki run.**
+
+- **A press that joins a start under way says so once**: a second Generate or Update LLM Wiki (or the reader's **Update**) during a start shows `Codebook is already starting an LLM Wiki <generation|update> in this window; this press joins it.`; **Generate anyway**, **Update anyway** or the offer's **Update LLM Wiki** pressed then shows `…, so this choice was not applied. If that start stops for the same reason, choose it again.`
+- **In Cursor, readying Codebook's skill is bounded and stoppable.** The skill's check and deployment run for at most 30 seconds with the Wiki's marker claimed. **Stop LLM Wiki Run** ends them at once (`The LLM Wiki <generation|update> was cancelled at <time> while Codebook readied the Cursor skill; no agent was started. Press <Generate|Update> LLM Wiki when you want to start again.`, with the time you pressed Stop), and the 30 seconds end them with `Codebook stopped readying the Cursor skill after 30 seconds; no agent was started. …`. A closing window ends them too, and a window that is already closing starts none. A new press waits for a stopped step that is still writing the skill, so two deployments never run at once; a step that never settles is named with **Developer: Reload Window** as the way out.
+- **Remove Managed Cursor Skill waits for a skill step of the window** (up to 5 seconds) so a late deployment cannot bring the skill back, says so when the step does not end in time, and a Generate or Update pressed during the removal readies no skill and starts no agent.
+- **A start never loses another window's protection.** When **Generate anyway** or **Update anyway** took over a stopped VS Code watch's reservation and the start is then refused (for example by a skill conflict in Cursor), the reservation is written back as that window's own marker text, with its own window and bound, so that window still removes it; a closing window keeps it on disk and retries a write-back that another window's claim blocked for up to 5 seconds. A reservation already gone from disk is never brought back.
+- **A marker that cannot be removed at once is removed on a retry** instead of standing until its bound.
+- **With nothing running, Stop LLM Wiki Run says** `No LLM Wiki run is going on in this window.`
+
+**Clearer sentences.**
+
+- **One verb per editor for a stop**: VS Code says `stopped watching` and Cursor says `cancelled` in every notice and Output record, including a stop after a Wiki was published.
+- **A folder that cannot take a first Wiki names what is in the way** (`The folder <folder> cannot take a new LLM Wiki: <path> is in the way. Press Update LLM Wiki for the details and the next step.`); the block's cause id moves to the Output record.
+- **The LLM Wiki view shows `Waiting for chat`** as soon as a stopped watch's reservation is written, also without a file event.
+
+**Diagrams.** The bundled skill moves to **1.0.50**: two conditional edges between the same nodes, an edge that crosses a row, and edges between different nodes with one midpoint no longer draw their labels over each other or over a node.
+
+**Compatibility.** The MCP API stays 1.8; the Wiki's published format, the marker format and stored learner data do not change.
+
 ## [0.2.46.0] - 2026-10-26 (development candidate)
 
 Cycle 0055 ([Issue #132](https://github.com/laststance/codebook/issues/132)), a feature cycle, second of its two pull requests: the LLM Wiki gets its own view in Codebook's Activity Bar, and the Wiki feature area is proven again natively in VS Code and Cursor (trial N55).

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.46.0** once the second pull request of [Cycle 0055](https://github.com/laststance/codebook/issues/132) is merged; until then 0.2.45.0 ([PR #133](https://github.com/laststance/codebook/pull/133), the cycle's first pull request) is the delivered one, and the active cycle Issue says where the delivery stands. [Cycle 0055](https://github.com/laststance/codebook/issues/132) is a feature cycle: **Codebook: Generate LLM Wiki** writes a project's first LLM Wiki through the editor's agent from Codebook's own entry (its first pull request), and an **LLM Wiki** view in the Activity Bar shows, opens and updates it (its second). Cycle 0053 was a feature cycle: a test inside a workspace package runs with that package's Vitest and config, as the package's own `vitest` would, while a test the repository root's config already selects keeps running from the root. Cycle 0054 is a bug-fix cycle that closes the three defects Cycle 0053 carried: a test that ends before a later declared stop says so, a package test's launch asks the repository root again whether its config now selects the test, and the native-trial bootstrap keeps a listing it could not release. 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 was a bug-fix cycle that closed 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.47.0** once the first pull request of [Cycle 0056](https://github.com/laststance/codebook/issues/135) is merged; until then 0.2.46.0 ([PR #134](https://github.com/laststance/codebook/pull/134), Cycle 0055's second pull request) is the delivered one, and the active cycle Issue says where the delivery stands. Cycle 0056 is a bug-fix cycle that closes the defects Cycle 0055 carried, in three pull requests: the first makes an LLM Wiki start say what happens when it joins a start under way, is stopped or passes its bound, and release or write back what it claimed; the second the LLM Wiki view and the reader; the third a saved test replay that Cursor refused to open, with the native trial. [Cycle 0055](https://github.com/laststance/codebook/issues/132) is a feature cycle: **Codebook: Generate LLM Wiki** writes a project's first LLM Wiki through the editor's agent from Codebook's own entry (its first pull request), and an **LLM Wiki** view in the Activity Bar shows, opens and updates it (its second). Cycle 0053 was a feature cycle: a test inside a workspace package runs with that package's Vitest and config, as the package's own `vitest` would, while a test the repository root's config already selects keeps running from the root. Cycle 0054 is a bug-fix cycle that closes the three defects Cycle 0053 carried: a test that ends before a later declared stop says so, a package test's launch asks the repository root again whether its config now selects the test, and the native-trial bootstrap keeps a listing it could not release. 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 was a bug-fix cycle that closed 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.
 
@@ -42,7 +42,8 @@ Read [AGENTS.md](AGENTS.md) when starting or resuming work; Codex loads it as it
 ## Tracking and continuation
 
 - [Goal Issue #1](https://github.com/laststance/codebook/issues/1) remains open until all acceptance conditions and owner acceptance hold.
-- [Cycle 0055 Issue #132](https://github.com/laststance/codebook/issues/132) is the active cycle: a feature cycle in which Codebook's Activity Bar generates, opens and updates the LLM Wiki, re-proven natively in both editors. Its baseline E1 measured a first generation at 34 min 33 s in VS Code and 4 min 14 s in Cursor's agent CLI, so a generation is bounded at 55 minutes.
+- [Cycle 0056 Issue #135](https://github.com/laststance/codebook/issues/135) is the active cycle: a bug-fix cycle with no increment that closes the defects Cycle 0055 carried, in three pull requests (the LLM Wiki run lifecycle; the LLM Wiki view and the reader; the Cursor test-replay fix with the native trial N56); the Issue holds its tasks and state.
+- [Cycle 0055 Issue #132](https://github.com/laststance/codebook/issues/132) is closed after [PR #133](https://github.com/laststance/codebook/pull/133) and [PR #134](https://github.com/laststance/codebook/pull/134): a feature cycle in which Codebook's Activity Bar generates, opens and updates the LLM Wiki, re-proven natively in both editors. Its baseline E1 measured a first generation at 34 min 33 s in VS Code and 4 min 14 s in Cursor's agent CLI, so a generation is bounded at 55 minutes.
 - [Cycle 0054 Issue #130](https://github.com/laststance/codebook/issues/130) is closed after [PR #131](https://github.com/laststance/codebook/pull/131): a bug-fix cycle with no increment that closed the three defects Cycle 0053 carried (an unreached declared stop explains itself, a launch asks the root claim again, the native trial keeps unreleased listings); the Issue holds its tasks and state.
 - [Cycle 0053 Issue #128](https://github.com/laststance/codebook/issues/128) is closed after [PR #129](https://github.com/laststance/codebook/pull/129): a feature cycle in which a test inside a workspace package runs with that package's Vitest and config (TanStack Query's and Redux Toolkit's library tests among the final-acceptance targets); the three defects it carried are the tasks of Cycle 0054.
 - [Cycle 0052 Issue #124](https://github.com/laststance/codebook/issues/124) is closed after [PR #125](https://github.com/laststance/codebook/pull/125), [PR #126](https://github.com/laststance/codebook/pull/126) and [PR #127](https://github.com/laststance/codebook/pull/127): a bug-fix cycle with no increment that closed every defect Cycle 0051 carried (replays leave, open and reload without stale frames; a test replay's moves and summary page; the live runtime, a browser run's refusals and the tests' hygiene); it carried nothing.

VERSION

@@ -1 +1 @@
-0.2.46.0
+0.2.47.0