@laitszkin/apollo-toolkit 2.14.11 → 2.14.12
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
|
@@ -4,6 +4,12 @@ All notable changes to this repository are documented in this file.
|
|
|
4
4
|
|
|
5
5
|
## [Unreleased]
|
|
6
6
|
|
|
7
|
+
## [v2.14.12] - 2026-04-10
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
- Tighten `implement-specs-with-worktree` so detached or temporary worktrees must recover the exact requested `docs/plans/...` spec set from the authoritative branch or main working tree before coding, instead of substituting nearby plans.
|
|
11
|
+
- Require `implement-specs-with-worktree` to sync only the in-scope spec directory plus its governing batch `coordination.md`, avoiding accidental sibling-spec imports into the worktree.
|
|
12
|
+
|
|
7
13
|
## [v2.14.11] - 2026-04-09
|
|
8
14
|
|
|
9
15
|
### Changed
|
|
@@ -22,9 +22,9 @@ description: >-
|
|
|
22
22
|
|
|
23
23
|
## Standards
|
|
24
24
|
|
|
25
|
-
- Evidence: Read and understand the complete specs set before starting implementation.
|
|
26
|
-
- Execution: Create or use an isolated worktree for implementation, follow the implementation standards from the dependent skills, and commit to a local branch when done.
|
|
27
|
-
- Quality: Complete all planned tasks, run relevant tests,
|
|
25
|
+
- Evidence: Read and understand the complete specs set before starting implementation, and when the requested plan path is missing from the current worktree verify where the authoritative copy actually lives before substituting any nearby spec.
|
|
26
|
+
- Execution: Create or use an isolated worktree for implementation, sync the exact approved plan set into that worktree when it is missing there, follow the implementation standards from the dependent skills, and commit to a local branch when done.
|
|
27
|
+
- Quality: Complete all planned tasks, run relevant tests, backfill the spec documents with actual completion status, and avoid dragging unrelated sibling specs into the worktree just because they share a batch directory.
|
|
28
28
|
- Output: Keep the worktree branch clean with only the intended implementation commits.
|
|
29
29
|
|
|
30
30
|
## Goal
|
|
@@ -38,6 +38,11 @@ Implement approved spec planning sets in an isolated git worktree, ensuring main
|
|
|
38
38
|
- Locate the specs directory. The path format is `docs/plans/{YYYY-MM-DD}/{change_name}/` for single-spec work, or `docs/plans/{YYYY-MM-DD}/{batch_name}/{change_name}/` for coordinated multi-spec work.
|
|
39
39
|
- If the user provides a specific path, use that directly.
|
|
40
40
|
- If only a `change_name` or date is given, search for matching directories under `docs/plans/`.
|
|
41
|
+
- If the requested path is absent from the current worktree, stop and identify the authoritative source before implementing:
|
|
42
|
+
- inspect the main working tree and any relevant local branches/worktrees for that exact `docs/plans/...` path
|
|
43
|
+
- prefer the exact matching plan directory from the repository's authoritative branch or main working tree over archived, approximate, or sibling plan directories
|
|
44
|
+
- if the plan lives under a batch directory, sync only the requested spec directory plus the shared `coordination.md` that governs it
|
|
45
|
+
- do not copy neighboring sibling spec directories into the worktree unless the user explicitly expanded scope
|
|
41
46
|
- When the plan sits under a batch directory, also read the sibling `coordination.md` before implementation.
|
|
42
47
|
- Read all five spec files:
|
|
43
48
|
- `spec.md` — requirements and BDD behaviors
|
|
@@ -52,6 +57,7 @@ Implement approved spec planning sets in an isolated git worktree, ensuring main
|
|
|
52
57
|
|
|
53
58
|
- Run `git worktree list` to see existing worktrees and branches.
|
|
54
59
|
- Determine if the current session is already inside a worktree (check `git rev-parse --show-toplevel` and compare with `git worktree list`).
|
|
60
|
+
- If the current worktree is missing the exact requested plan set, sync that plan into the worktree before coding and re-read the synced files there so implementation happens against the same plan snapshot that will be backfilled later.
|
|
55
61
|
|
|
56
62
|
### 3) Create a new worktree if needed
|
|
57
63
|
|
package/package.json
CHANGED