feat(install)!: one setup command - hooks are the plugin's job, mcp-config prints only #231
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!231
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-172-install-consolidation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
BREAKING (released surface): the binary hook-delivery channel is removed and all client wiring consolidates under
madtea install.madtea install --hooks/mcp-config --hooks/--remove-hooksare gone along with the hook materialization and settings-merge machinery - the plugin (marketplace add + install) is the one way to get the guardrail hooks, and install prints that recommendation where the offer used to fire.mcp-config --installno longer wires anything for ANY client: it survives one release cycle as a hidden flag that always refuses with the replacement commands, and mcp-config becomes a pure snippet printer.madtea installis the single setup command: the bare run keeps today's behavior (binary + completions + Claude Code MCP registration when detected, consent flags untouched); --skip-binary/--skip-completions/--skip-mcp re-run any single feature; the new --mcp-client codex|gemini|antigravity (repeatable/comma) wires the other agents through the same single implementations mcp-config previously used (exported Wire helpers - one implementation, two names gone). Explicitly-requested client wiring reports an aggregate nonzero error on partial failure; the best-effort bare-run registration stays best-effort. Docs consolidated accordingly, including a pre-existing wrong antigravity config path fixed to match the code.Closes #172