squad-kit 0.12.3 → 0.12.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,30 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.12.4] — 2026-08-26
11
+
12
+ ### Bug fixes
13
+
14
+ - **"Open" on a freshly generated plan 404'd in the console.** After a run finished, the *Plan
15
+ saved* callout's **Open** link — and the **Open plan** button on the run report — resolved to
16
+ `/plans/<feature>/.squad%2Fplans%2F<feature>%2F<file>.md`, and the page rendered
17
+ `404 Not Found: {"error":"not_found"}`. Reported as
18
+ [#9](https://github.com/AzmSquad/Squad-Kit/issues/9).
19
+
20
+ Run records and the `done` event carry `planFile` as a path relative to the workspace root
21
+ (`.squad/plans/<feature>/<file>.md`) — that is the form shown to the user, and what both
22
+ `squad new-plan` and the console runs API have always written. The `/plans/$feature/$planFile`
23
+ route and `GET /api/plans/:feature/:planFile` want the **file name** only, because the API
24
+ resolves it under `.squad/plans/<feature>/`. Both link sites now normalise the value.
25
+
26
+ Normalising in the UI rather than at the writers also repairs every run record already on disk,
27
+ which all store the long form — so the run report's link works for historical runs too, not just
28
+ new ones.
29
+
30
+ The existing test asserted the correct href but fed the component a bare file name the server
31
+ never sends, so it passed while the real link was broken. The fixture now matches the actual
32
+ payload, and reverting the fix makes it fail.
33
+
10
34
  ## [0.12.3] — 2026-08-25
11
35
 
12
36
  ### Bug fixes