Autonomous-loop bootstrap gate
The maintainer loop bootstrap requires master (default branch) to have branch protection before running unattended. Currently it has none (GET /branches/master/protection → 404).
Repo is public, so protection is available at no cost.
Requested ruleset
- Require PR before merging (status checks required; approvals per your preference)
- Require status checks to pass: CI workflow (typecheck, lint, test)
- Require branches up to date before merge
- Block force pushes
- Block deletions
Why
Hard rules already forbid the loop pushing to master / force-pushing, but protection is defense-in-depth: it stops accidental direct pushes and enforces CI as a merge gate. Prior cycle noted CI does not currently gate biome (drift) — wiring required checks here fixes that too.
Note
Not auto-applied: enabling protection changes the human maintainer's own push workflow, so it needs a human decision.
@Human needs decision: enable protection with the ruleset above? (or confirm intentional opt-out so the loop stops re-filing)
Autonomous-loop bootstrap gate
The maintainer loop bootstrap requires
master(default branch) to have branch protection before running unattended. Currently it has none (GET /branches/master/protection→ 404).Repo is public, so protection is available at no cost.
Requested ruleset
Why
Hard rules already forbid the loop pushing to master / force-pushing, but protection is defense-in-depth: it stops accidental direct pushes and enforces CI as a merge gate. Prior cycle noted CI does not currently gate biome (drift) — wiring required checks here fixes that too.
Note
Not auto-applied: enabling protection changes the human maintainer's own push workflow, so it needs a human decision.
@Human needs decision: enable protection with the ruleset above? (or confirm intentional opt-out so the loop stops re-filing)