DevSquad 0.11.1 — Claude hook-loading correction

DevSquad 0.11.1 — Claude hook-loading correction

This corrects the legacy Claude plugin hook configuration from0.11.0.
The standalone squad core stays0.1.0; its source tree/payload are unchanged.
This is a local tool and GitHub release, not a hosted service or registry release.

Correction

The normal scoped plugin updater returned0 and installed0.11.0, but Claude's
actual loader/validator rejected its event-only hook file. Version0.11.1 adds
the required top-level hooks object, preserving every command, matcher and
15s timeout. Offline tests now reject the old shape and require consistent
plugin/marketplace versions. The old release's tag/assets are unchanged and
its notes disclose the issue.

Independent review is clean. Actual Claude2.1.220 validation passes for the
corrected source; an exact-old-shape fixture fails. All261 Bash assertions
pass, including nine packaging assertions. Final public CI
passed all four jobs onbefc7e8: Bash3.2 (261 assertions), Python3.11.9
(604 tests/900.372s), Python3.14.7 (604 tests/869.101s), and optionalMCP
(23 tests/3.809s, one optional skip). Both full core jobs had two optionalSDK
skips and zero failures/errors/unraisable diagnostics. Exact merge
cddfa68 has the same tree as that candidate.

The normal user-scoped updater installed0.11.1 enabled, and the actual installed
Claude plugin now validates with zero loading errors. Its hook file exactly
matches the independently reviewed correction. Downloaded release assets
match all staged checksums.

Use it

git clone https://github.com/joshidikshant/devsquad.git
cd devsquad
./install.sh --core-only
export PATH="$HOME/.local/bin:$PATH"
squad doctor

Existing Claude plugin users can run:

claude plugin update devsquad@devsquad-marketplace --scope user

Start a new Claude Code session after updating. For an already-open old MCP
server, reconnect only DevSquad's MCP connection to load the selected package.
No unrelated plugin/server/account settings need changing.

In a committed project, use squad review --base main --dry-run, then a bounded
review/fix. Saved review/check evidence and the displayed finish command bind
acceptance to the exact candidate. The runtime guide
covers setup, pinned optional MCP, installation, safe upgrades and recovery.

Accepted core evidence and limits

Core CI previously passed604 tests each on Python3.11.9 and3.14.7, with two
optionalSDK skips each and no failures/errors/unraisable diagnostics. The actual
selected schema17 MCP release passed nine SDK tests/no skips, idempotent
reinstall/no drift/pip check. Live Claude CLI handoff, Claude implementation →
independently verified Codex review → tests, Grok MCP operation and updated
Antigravity agy CLI MCP status have separate recorded receipts/scopes.

Grok/agy MCP operations do not prove automatic writer/reviewer roles. Claude
desktop Code-tab operation remains unverified; Antigravity IDE is outside scope.
Council remains experimental/native-unavailable/automaticOFF; its fixture
comparison is inconclusive. Jev routing staysOFF. The broader engineering-team
plan is not declared complete. No paid API fallback or subscription-window
savings claim is made. Failed/rejected gates remain in tracked evidence.

Source/plugin archives are from the exact tested merge; wheel reuse requires
exact core tree/payload equality. Attached SHA256SUMS cover all three assets.
Base installation downloads no dependencies; optional MCP requires an explicitly
prepared pinned wheelhouse. Python3.11+ and Unix-like hosts are required.