the automation layer

Two suites, run together, built against real throwaway repositories — one dirty, one clean — rather than mocks, because half of what these hooks decide depends on whether there is anything to lose.

• 20theme-push-guard · must ask. Anything that reaches production: a push to main in seven spellings, a merge on main, shopify theme push, and gh pr merge in four forms — including when a compound command cds into the theme first.
• 14theme-push-guard · must pass silently. Ordinary work: branch pushes, git status, git commit, shopify theme dev, a push in the docs repo, and grep -rn 'push'. A guard that cries wolf gets routed around.
• 5theme-push-guard · permission mode. ask in every mode a human can answer; deny under bypassPermissions, where a prompt reaches nobody and the run would hang on a question no one sees.
• 7git-destructive-guard · history. Always ask, even on a clean repo: reset --hard <ref>, branch -D, stash drop, stash clear, force push.
• 8git-destructive-guard · working tree. Ask only when something is at risk. The same command is a question on a dirty repo and silence on a clean one, which is why the suite needs real repos.
• 10git-destructive-guard · ordinary work. Must pass silently — including git clean -n, a dry run, and git branch -d, the safe delete.
• 4git-destructive-guard · the cd blind spot. The hook payload's cwd is where the shell was BEFORE the command runs, so cd <other repo> && git clean -fd was judged against the wrong repo and waved through. Found by probing, not by reading.
• 5git-destructive-guard · permission mode. The same ask/deny split.

The mechanical tier only, and Juan sits with it. Everything below is a rule; the moment a judgement is required the gate hands it back.

• 1Read. Square card takings, Shopify payouts, and six Xero bank accounts.
• 2Match on rules and dates. Internal transfers, Shopify invoice matches, rule-driven deposits.
• 3Stop at expense coding. Business-versus-personal is a tax position rather than a rule, so a human answers it. This is the boundary, not a gap.
• 4Result. 95 unreconciled items to zero, all six accounts green, receivables $656.65 to $0.00.

Live orders in, one map link out. Two of these four steps exist only because a plausible shortcut was measured and failed.

• 1Pull. Live unfulfilled Shopify orders, addresses as written.
• 2Find the departure time by binary search. The latest you can leave and still make every stop inside the hard 9pm cap.
• 3Check the freezer against capacity before anything is loaded, and make the defer-or-deliver call on a late order.
• 4Emit one Google Maps link with every stop in order. A ZIP-centroid fallback was tested for the geocoding and rejected: four miles off.

A library of 46 raw shoots and 46 finals, each with a textless master, so a cut can be re-subtitled or re-hooked without going back to the footage.

• 1Transcribe. The spoken take becomes an SRT with timings.
• 2Derive the cut list. Offsets differ from month to month, so the timing is measured per shoot rather than assumed — that assumption is what used to put every cut a beat late.
• 3Assemble. One keystroke, and the result is a rough cut plus a textless master.