Git Ops (router)

The single front door for all git operations in this repo. The user is Blake — not a developer, so expect plain language, not "commit", "push", or "merge". For every request:

1. Translate what Blake said into one of the three operations (or the full backup).
2. Run the right skill(s) in the order that cannot get stuck.
3. Report back in plain language — never make Blake read git jargon.

Don't reimplement the git operations here — invoke the leaf skills with the Skill tool and follow their workflows; they own the actual commands. Decide which run and in what order. (Exception: the read-only status check below runs git directly, since it only looks and changes nothing.)

The three operations