You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Security
Dev Squad approval events (#333, PR #344): a plan approval label needs a current label state, a fresh application event and an actor with current repository push permission. The newer authorized label or comment decision wins; unavailable label evidence and permission errors fail closed.
Dev Squad SDK reference (#342): test commands use credential-filtered environments and fresh reports; plan approval comments require repository push permission; webhook request bodies are bounded by raw bytes during streaming, before signature verification.
Added
Dev Squad acceptance tests (#333, PR #344): eight boundary test files with fixture, loopback and mocked evidence. A fresh isolated install runs the nine roles through the installed runner and a trusted CLI; a wrong implementation yields a real nonzero exit; the tower validates with 0 errors and 0 warnings. Scope and limits are in docs/dev-squad-harness-trial.md; no real provider or GitHub call is claimed.
Dev Squad acceptance evidence (#333): recorded the Codex-led local nine-role baseline with independent tests and final-head review/security; preserved Pi/Claude Code results and incomplete-role evidence. Closure targets the maintainer-confirmed portable workflow; automatic harness launch remains in #320.
Portable Dev Squad onboarding (#332, #334): squad doctor checks local Node/git, runner/config and OpenRouter readiness without paid calls or mandatory Claude credentials. The user's current harness stays the lead. Shared specialist roles now include triage, architect, researcher, tester, verifier and doc-writer, with canonical tower nodes and per-role model selection. Doc-writer requires explicit writable folders. The skill documents the complete lead-driven workflow and its current safety/budget limitations; cross-harness end-to-end evidence remains tracked in #333.
Fixed
Dev Squad SDK pipeline and quality gates (#333, PR #344): unsuccessful quickfix and quality roles stop delivery; empty or unmet verification criteria, a red or unknown suite and explicit gaps hold. Delivery returns explicit outcomes and SDK CLI exits nonzero unless it reaches pr_open. The portable runner attempts exactly one terminal live event after each start, including provider/protocol failures and interruption; argument failures before start emit no lifecycle, and an offline viewer remains best effort.
Squad step limits (#336): exhausted tool loops now exit nonzero instead of falling through as success. The last assistant text is surfaced as bounded, control-stripped INCOMPLETE diagnostics, not a verdict. Limits are validated before paid calls and the last two calls include an honest finish reminder. Deterministic tests cover cap outcomes, final-call completion and tool-message pairing; live researcher/verifier repeats at 3/5 steps completed, without claiming guaranteed model compliance.
Dev Squad installation (#330): squad init now distributes the complete canonical eight-layer tower from examples/dev-squad, with nested towers, agents, prompts and source. Removed the obsolete reduced tower template and placeholder substitution. Updates preserve existing towers and bundle edits; bundled example logs remain trackable. The task runner does not launch the full SDK pipeline automatically.