squad-kit 1.0.0 → 1.0.1

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,81 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [1.0.1] — 2026-11-03
11
+
12
+ squad-kit 1.0.1 makes the squad steadier and easier to follow, from what we saw in the first trials. To get it
13
+ from 1.0.0, run `squad upgrade` once. From now on the app updates itself with one button.
14
+
15
+ ### Easier to follow
16
+
17
+ - **"From an idea or message" works and shows its progress.** The dialog no longer disappears behind a blurred
18
+ board. The Analyst works in the background with three steps and a clock, and you can press Cancel. You can
19
+ close the window: the draft waits for you under New ticket.
20
+ - **Errors stay on screen** until you close them.
21
+ - **The Conversation tab reads in plain words.** "Handed in its answer" replaces the raw answer, and a command
22
+ the step may not run shows in grey as skipped, not in red as a failure.
23
+ - **A ticket waiting for a free place says so**: "Waiting for a free place", with the limit, instead of
24
+ looking as if it runs.
25
+ - **"Resumed after sleep"** shows when the computer slept in the middle of a step.
26
+
27
+ ### The Update button
28
+
29
+ - **The app looks for a new version** on start and once a day. When one is out, Home and every project show
30
+ it with what is new. **Update now** waits until no agent is in the middle of a step, installs, and restarts
31
+ the app on the same link. Every ticket carries on where it was.
32
+ - **Settings › About squad-kit** shows your version, when it last checked, and a switch for the daily check.
33
+ Terminal: `squad upgrade`.
34
+
35
+ ### Quality
36
+
37
+ - **A new Quality setting** on the Squad and AI page: **Best** (the default), **Balanced** or **Thrifty**.
38
+ On Best, the strongest model builds and reviews at high effort. On Claude Code that is Opus. Terminal:
39
+ `squad config set quality best`.
40
+ - **A new "extra high" effort.** On Best, a Builder run that fails moves the next one up to extra high.
41
+ - **The Reviewer is never weaker than the Builder** on Best and Balanced.
42
+ - **Reading the project after a merge is cheaper.** The project map is only read again when files are added,
43
+ moved or removed, and that read runs on a lighter model.
44
+
45
+ ### No silent hangs
46
+
47
+ - **Stop works at every moment**, also between two runs, and it ends the agent with everything it started. A
48
+ step that runs out of time ends the same way.
49
+ - **Git that talks to a remote has a time limit**, and never waits for a password prompt nobody sees.
50
+ - **Starting an agent has a time limit.** If it cannot start, the step says why instead of waiting.
51
+ - **The Builder no longer waits for the "before" screenshots.** They are taken beside it, with their own time
52
+ limit.
53
+ - **A test, lint or build command with no output for 5 minutes is stopped**, and the ticket says which one.
54
+
55
+ ### Agents stay in their lane
56
+
57
+ - **Every agent runs with the permissions of its step.** The Tester can run the app but cannot change the code;
58
+ what it changes anyway, squad-kit puts back.
59
+ - **No agent can change the instruction files** the next session would follow, such as `CLAUDE.md`, or
60
+ squad-kit's own `.squad/` folder. Agents read copies of the project's rules, never your own folder.
61
+ - **No agent can rewrite git history.** squad-kit checks after each Builder and Tester step.
62
+ - **Every answer is checked.** An incomplete answer is asked for once more, then the step says so plainly.
63
+ - **Text from outside**, such as a tracker item or a pasted message, reaches the agents as data, never as
64
+ orders.
65
+ - **Test, setup and release commands no longer get the AI and tracker keys.**
66
+
67
+ ### No lost work
68
+
69
+ - **A release and a "Looks right" at the same moment** no longer get in each other's way.
70
+ - **Stop keeps the step the ticket was at.**
71
+ - **"Bring in the latest main"** uses the remote's main, not an old local copy.
72
+ - **Only a real clash counts as a clash.** Other git errors say what went wrong. `squad doctor` checks the git
73
+ version.
74
+ - **Tracker updates are kept until they are sent**, and retried when the tracker is down.
75
+ - **A release whose push failed** says "not pushed yet", with **Push again** on the Releases page. Terminal:
76
+ `squad release <version> --push-again`.
77
+ - **Withdraw change** takes back an approved change the squad has not built yet, and puts the spec back to how
78
+ it was. Terminal: `squad propose <ID> --withdraw`.
79
+
80
+ ### Fixes
81
+
82
+ - **The Architect writes the stack**, with each part's role, from the code it reads. `stack.md` was empty.
83
+ - **The Reviewer is told the checks already ran**, so it does not run them again.
84
+
10
85
  ## [1.0.0] — 2026-11-02
11
86
 
12
87
  squad-kit 1.0 is an agent harness for the whole software cycle. You write a ticket in plain words. A squad of
@@ -728,7 +803,8 @@ First public release.
728
803
  - Plan-generation meta-prompt (`generate-plan.md`), intake template (`intake.md`), and plan skeleton reference (`story-skeleton.md`).
729
804
  - Documentation: `docs/philosophy.md`, `docs/getting-started.md`, `docs/customization.md`, `docs/vs-spec-kit.md`.
730
805
 
731
- [Unreleased]: https://github.com/AzmSquad/squad-kit/compare/v1.0.0...HEAD
806
+ [Unreleased]: https://github.com/AzmSquad/squad-kit/compare/v1.0.1...HEAD
807
+ [1.0.1]: https://github.com/AzmSquad/squad-kit/releases/tag/v1.0.1
732
808
  [1.0.0]: https://github.com/AzmSquad/squad-kit/releases/tag/v1.0.0
733
809
  [0.6.0]: https://github.com/AzmSquad/squad-kit/releases/tag/v0.6.0
734
810
  [0.5.0]: https://github.com/AzmSquad/squad-kit/releases/tag/v0.5.0
package/README.md CHANGED
@@ -11,7 +11,7 @@
11
11
  <a href="https://squad-kit.com"><img src="https://img.shields.io/badge/site-squad--kit.com-7cffa0?labelColor=0a0a0c" alt="Website"></a>
12
12
  </p>
13
13
 
14
- **You write the ticket. Your squad does the rest.**
14
+ **Your AI Engineering Squad. One Unified Harness.**
15
15
 
16
16
  squad-kit is an agent harness for the whole software cycle. You describe what you need in plain words. A
17
17
  squad of AI agents takes it from that ask to a release: the Analyst, the Architect, the Builder, the Tester
@@ -148,9 +148,10 @@ linked ticket or a bug report.
148
148
 
149
149
  ## Cost and models
150
150
 
151
- - squad-kit picks a **model level** for each role and step: **strongest** where a mistake is expensive (spec,
152
- design, review), **balanced** for building, **fast** for screenshots and small helpers. The team or each
153
- person can change them on the **Squad and AI** page.
151
+ - squad-kit picks a **model level** for each role and step from the project's **Quality** setting: **Best**
152
+ (the default) builds and reviews on the strongest model, **Balanced** builds on it at medium effort, and
153
+ **Thrifty** builds on a lighter one. **Fast** stays for screenshots and small helpers. The team or each person
154
+ can change single steps on the **Squad and AI** page.
154
155
  - The board shows **what each ticket and each role used**, in tokens and in money at the AI company's API
155
156
  prices. Your own AI subscription pays for it. This shows where the cost goes.
156
157
  - One **limit of tickets at once** (2 by default, up to 5) is shared by all your projects, because they use the