Mature repos benefit from structured scans (repomix / eza / fd / rg)
over blind Reads; explicit token and wall-clock estimates in the Plan
step let the user redirect early before a scope mismatch burns context.
Why: Charles asked whether I can proactively manage repos on his Gitea.
Define explicit allow / confirm / forbid tiers so I don't accidentally
delete a repo or force-push main.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Why: Charles wants an explicit three-phase workflow alongside the
existing "Think Before Coding" checklist, not a replacement.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Why: keep a single language register for the global guide, and reflect
Charles's updated defaults (push when possible, address as Charles).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
