Operate and troubleshoot the Patcher API service (`api/patcher_api/`) on its Linux host. Two modes: 1. STATUS SWEEP (`/api-ops`, `/api-status`, "check the api", "is the api healthy", "run a health check") — a read-only pass over the systemd units, cloudflared tunnel, app endpoints, database, disk, and the Healthchecks.io monitors, reporting green/yellow/red per component. 2. TROUBLESHOOTING (a symptom like "502 through cloudflared" / "service won't start", or pasted logs) — walks the known failure modes (KEYRING_BACKEND, cloudflared outbound-only, SQLite locking, systemd perms, deploy-token gating, restart loops, ingest failures). Also helps translate the systemd gotchas to a user's own Docker setup on a best-effort basis (Docker is not officially supported). Invoke on: "/api-ops", "/api-status", "patcher api won't start", "502 from cloudflared", "keyring error on linux", "is the api healthy", "why is patcher-deploy down", "schema-audit keeps flapping", or a pasted systemd / cloudflared /
Scaffold a new MyST documentation page for the Patcher docs site. Picks the right section by topic, generates a page that matches the project's existing template (target anchor, H1, `{rst-class} lead` paragraph, body), wires it into the section toctree in `docs/index.md`, and applies the project's voice rules from the start so a follow-up docs-voice pass isn't needed. Invoke when the user says: "/docs-add <topic>", "new docs page for <topic>", "scaffold a doc for <topic>", "add a usage page about <topic>", "draft a concept page on <topic>", or similar. Topic is required; section is optional (will be inferred or asked).
Review a Patcher documentation file (or glob) against the project's voice rules and propose rewrites that drop robotic patterns: "Patcher is designed to..." preambles, heading-restating lead paragraphs, hedged passive voice, jargon, diminishing language, and em-dashes. Defaults to report-only with suggested rewrites; switches to apply-mode only when the user explicitly says so. Invoke when the user says: "/docs-voice <path>", "voice check <path>", "rewrite voice in <path>", "audit voice in <path>", "fix tone in <path>", or similar. Path is the single required argument; can be a file (`docs/guides/export.md`) or a glob (`docs/guides/*.md`, `docs/**/*.md`).
Given a Mac application name, look up every patching method that covers it across Installomator, Homebrew Cask, and AutoPkg, plus surface official vendor/MDM deployment documentation if it exists. Read-only. No DB writes, no state changes. Useful when adding a new app to the canonical apps DB, debugging an unmatched patch title, or sanity-checking deployment options for a new title. Invoke when the user says any of: "/patcher <app>", "check match for <app>", "patcher lookup <app>", "what patching methods cover <app>", "is <app> in Installomator", "look up <app> across ecosystems", or similar phrasing. App name is the single required argument.