[Reference Only] Upstream PR #141 - feat(antigravity): initial steps for Antigravity anti-ban alignment

[nsalvacao]

Context

This draft PR mirrors upstream branch 'upstream-prs/pr-141' into 'master' for review, provenance, and later decision-making only.
It must not be merged wholesale. If we adopt anything from it, the intended path is commit-level intake only.

Upstream Source

• Original PR: feat(antigravity): initial steps for Antigravity anti-ban alignment decolua/9router#141
• Original author: @LinearSakana
• Original title: "feat(antigravity): initial steps for Antigravity anti-ban alignment"
• Mirrored branch on this fork: upstream-prs/pr-141
• Current divergence snapshot vs master: 7 commits ahead, 143 commits behind

Current Intake Recommendation

• Decision: Reference only / absorbed-noop
• Status: Planned review only, with no integration performed yet
• Credit policy: preserve original author metadata, use git cherry-pick -x for any later intake, and keep any conflict adaptation in separate follow-up commits with explicit upstream attribution

Selected Commits For Any Future Intake

• No direct intake currently selected. This mirrored branch is retained for audit and provenance only.

Skipped / Excluded Scope

• Branch is retained as reference only because the main theme appears already represented upstream.

Acceptance Gates

• Do not merge this mirrored branch as-is.
• If anything is adopted later, intake only the explicitly selected commits or a newly re-validated subset.
• Preserve upstream authorship and provenance in Git history.
• Keep conflict-resolution/adaptation commits separate from upstream-authored commits.
• Reconfirm branch contents against current master at intake time before changing the selected scope.

Verification / Validation Checklist

• Reconfirm current master already covers the useful anti-ban behavior.
• Keep this PR draft and unmerged unless a missing delta is proven.
• If a residual commit is later selected, update the intake manifest first.

Review Focus

• Whether any residual anti-ban behavior is actually still missing from current master
• Whether this branch should remain reference-only and unmerged

Notes

• This PR is intentionally draft and serves as a reviewable reference mirror inside the fork.
• Current recommendation is to keep it unmerged unless a missing residual commit is proven.