@warren-dean/code-kit 0.36.1 → 0.38.0

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.
@@ -9,7 +9,7 @@
9
9
  "name": "code-kit",
10
10
  "source": "./",
11
11
  "description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
12
- "version": "0.36.1",
12
+ "version": "0.38.0",
13
13
  "category": "development",
14
14
  "tags": ["guardrails", "architecture", "lanes", "layers", "spec-driven", "ci", "multi-agent"],
15
15
  "license": "MIT"
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "code-kit",
3
- "version": "0.36.1",
3
+ "version": "0.38.0",
4
4
  "description": "Keeps AI coding agents inside your project's rules, from idea to merged code: spec design, lanes, layer rules, protected paths with an approval log, spec-check and design gates, proof-before-finish checks, dispatch, review, build status and CI verification, configured per project from its docs",
5
5
  "author": {
6
6
  "name": "Warren Langeveldt"
package/CHANGELOG.md CHANGED
@@ -2,6 +2,22 @@
2
2
 
3
3
  What changed in each release of code-kit, newest first. Versions follow the plugin manifest and the npm package `@warren-dean/code-kit`. Each release is also on [GitHub Releases](https://github.com/warrendeanlangeveldt/code-kit/releases).
4
4
 
5
+ ## 0.38.0 (2026-11-16)
6
+
7
+ - **Any stream's lead merges the queue.** In a project built as streams only the lead in the main checkout was given the merge step, so every stream's reviewed branches waited on that one session, while it worked on its own stream's stories: branches waited three to twelve hours, and dozens stood in the queue. Now another stream's lead merges the queue's head whenever its own stream has only waiting to do. One merge still runs at a time: a lock stops two leads starting one at once.
8
+ - **A failed group sends back only the branch at fault.** When branches queued to merge together failed, every one went back to its lane, though most had nothing wrong, and each needed reviewing and queueing again. Now a member that doesn't merge onto the base, or breaks its own lane's rules, goes back alone, and its partners keep their places and their reviews. Only a failure of the merged tree's checks, which can't be pinned on one member, sends the group back together.
9
+ - **Shared lists in core.** In a project built as streams, a stream's story that needed one more line in a core file every stream adds to (an allow-list of routes, a catalogue of lines) had to ask core for it, and wait for a core story, a core lane and a merge together. Name such a file a shared list (`anyActor` with `"adds": true`): any lane adds its entries in its own branch, and changing or removing an entry already there stays the owner's, refused as the edit is made and by `verify`.
10
+ - **Fewer, real candidates for core.** The check for code that belongs in core raised a candidate for every run of 60 tokens alike, tests included, and one per function a pair of files shared, so a platform lead could face over a thousand to decide. Now tests are left out, a clone takes 100 tokens alike by default, a pair of files is one candidate, a whole-project `promote scan` withdraws open clones it no longer finds, and module code that repeats core's is its own stream's lead's to decide.
11
+ - **A fix check that couldn't run no longer sends its branch back.** The fresh checkout a fix's tests run in copied installs only when it had none, so one holding a virtualenv but no `node_modules` ran the web checks without their tools, and the merge queue sent good branches back. It now copies each install it lacks, runs the project's install where its lockfiles differ, as the merge's checkout does, and a check that couldn't run (a tool not installed, an install that failed, a run out of time) leaves the branch in its place.
12
+ - **A stream's lead keeps its worktree after its branch merges.** Merging a stream's `lead/<stream>` branch took away that lead's own worktree, as a finished lane's is, and its shell stopped working. It stays now.
13
+ - **`defer` finds a story a stream's lead added in its own worktree.** It read only the main checkout's plan, where the story arrives when the lead's branch merges, so it answered that there was no such story.
14
+
15
+ ## 0.37.0 (2026-11-15)
16
+
17
+ - **The README covers every feature: what it does, how to use it and why.** It was checked against every spec and the code. Added: why streams exist and how to turn them on in a project that started as one, the usage-limit wait, branches merged together, standards, the QA lane, design hand-over, the plan's extra story lines, what a fix's test must show, teams when GitHub can't be reached, vibe's how and why, and every hook. The settings' Approvals section is in `/harness`; there's no Settings tab.
18
+ - **Each stream's lead sees its own stream in the mod.** The panes showed the whole project to every session, so a stream's lead saw the other streams' lanes, stories and milestone as if it ran them. Now the Build panel, the Lanes panel, what's ready and the Trail are the stream's own, each named for it, with a line per other stream (who leads it and what its lanes are on) and one for the shared core lanes. A session that leads nothing offers **Lead `<stream>`** for each stream, and the Code map labels each layer core or its stream's module.
19
+ - **A stream's loop gets its own stream's step.** The mod asked `code-kit next` without naming its session, so in a project built as streams a stream's lead could be prompted with the project's next step, another stream's story among them. It now names the session, and each lead's loop gets only its own stream's work.
20
+
5
21
  ## 0.36.1 (2026-11-14)
6
22
 
7
23
  - **`/code-kit:lead` moves the lead itself.** Typing `/code-kit:lead` (or `/code-kit:lead <stream>`) answered with which session leads and a `!` command for you to run, since the hooks refuse moving the lead from an agent. Typing the command is already your choice, so code-kit now records this session as the lead, of the stream you named, as the prompt arrives; the skill confirms it, says what it means, and moves into a worktree when another stream's lead holds the main checkout. A stream that doesn't exist changes nothing, and the answer names the streams.