What GitDoctor will and won't do

These are the rules the product is built to, stated plainly so you can hold it to them.

• Read-only until you say otherwise. The inventory reads schedules, run history, function logs, and queue counts. It changes nothing.
• Nothing is stored. Your Supabase token lives only in an encrypted cookie in your browser. There is no database of accounts, tokens, or snapshots on our side. Sign out and it is gone.
• Secret values are never read out. Only a fingerprint (a hash suffix) is selected, so the same key in two projects shows as the same fingerprint. Bearer tokens embedded in cron commands are redacted inside the database before the result leaves it.
• Plan before apply, undo for everything. Every action is proposed first, applied only when you confirm it, and its reverse is recorded in your session before success is reported. Loops are paused, never deleted. Where a runtime has no API lever, you get the instruction, not a button that pretends.
• The engine is open. The analysis you see is the same code as loopmath. Download your snapshot and reproduce the report locally.
• It says what it can't see. A project that can't be read is listed with the reason. A busy loop that is momentarily empty is noted, not flagged. Scenarios are labelled as scenarios.

GitDoctor is not affiliated with the Git project. “Git” is a trademark of Software Freedom Conservancy.