Git-aware Auto Approval for long-running coding tasks

[raylei50653]

TL;DR

Use Git as the code-change approval boundary: reversible local repo changes
can run automatically, while destructive or externally visible transitions
ask first.

The problem

For long-running coding tasks, the permission model often leaves two
extremes, and neither works well for a 30-minute run:

• Ask every time — constant interruptions
• Approve everything — no meaningful safety boundary

The proposal

An Auto mode where a lightweight reviewer checks whether an action is
still within the user's original task. Deterministic policies remain the
real safety boundary; the reviewer only cuts down on prompt fatigue.

For coding work, Git gives a natural line to draw:

Action	Behaviour
Local edits, tests, builds, diffs	Auto
Local commits	Auto (opt-in)
Push / force-push	Ask
Merge, release	Ask
Destructive history changes	Ask
Anything outside the workspace	Ask
External side effects / sensitive access	Ask or policy-controlled

The idea is to treat the local Git workspace as a reversible transaction
boundary.

Git is not the sandbox. The CLI/sandbox still controls filesystem, network,
credentials, and other external capabilities. Git only defines how far
code changes can progress before a human needs to look.

Why it matters

This would make 10–30 minute autonomous coding tasks practical without
turning Auto mode into unrestricted YOLO mode.