Repository navigation
v0.16.1
·
159 commits
to main
since this release
Changed
- Squad: the coder changes only the lines the task needs; a file that would pass ~400 lines is reported in
Known gapsinstead of trimming other code. The README says each role keeps its tasks in its own folder, sincesteps.shruns every file as a coder step (#386).
Fixed
- Squad runner: an answer is the first json object block that validates, so an echoed template or a quoted draft no longer wins; a role answer is read without
run.mjsheader lines, so a verifier PASS is read (it was always held); an unreadable triage answer is asked for once more;file:~200citations resolve; a person can release one issue's plan sign-off withSQUAD_APPROVE=<issue number>, posted on the issue (#369). - CLI:
reportandexportrun from a checkout path with spaces (the entry guard compared a percent-encoded URL with a raw path), the update command quotes the folder, and the tests pass there (#307). - dev-squad example: the README counts nine layers (the unattended runner is the ninth) and the GLM node no longer claims the architect, which defaults to GPT 6.1 Terra (#371).
- Squad: when
pack.mjstrimmed a review or security task to fit,run.mjsprints atrimmed: N KBheader andgate.mjsadds a note that the pass did not see the whole change, so READY no longer reads as full coverage (#383). - Squad:
squad.jsonrefuses a command with shell syntax (&&, pipes, redirects,$(…), quotes) when it is loaded, andsquad doctorreports it: the runner runs commands without a shell, so such a command could only fail at every step (#382).
Security
- Squad runner: a plan file entry with a comma or a line break is refused, so
src/a.js, .github/xcan no longer pass the control-file sign-off as one path and then reach the coder as two (#391).