Always Commit Push Deploy
When user asks for a code/infra change, always commit + push + deploy live — do not leave it local or staged
When the user asks for a code or infra change (swarm, vault, any repo), always commit AND push to remote AND make it live (restart/deploy) as part of completing the task. Do not stop at "patched + node check ok" or a local-only commit.
Why: User was burned by local-only changes lost on deploy (swarm incident 2026-05-31) and explicitly demands the full pipeline. Leaving work uncommitted/unpushed/not-live reads as "not done" and frustrates them.
How to apply: This overrides the global CLAUDE.md "não commitar sem pedir explicitamente" — for the user's own repos, the ask itself IS the authorization to commit+push+deploy. Sequence: edit → validate (node --check / tsc) → commit with clear msg → git pull --rebase --autostash → push → restart the service so it's live → report what's live. See swarm-mcp-conventions.