Idea: default-allow sponsorship so contributor PRs do not stall on hygiene-blocked

[agentHits]

Hi @lidge-jun — process idea, not a code change.

Many contributor PRs pile up under intake: hygiene-blocked, waiting for a maintainer to apply maintainer-sponsored before CI can fully run. While they wait, dev moves fast, branches go stale, each rebase resets review readiness, and authors burn out — several branches look abandoned at exactly this stage.

Proposal: make sponsorship the default path instead of a gate. For example, auto-apply the equivalent of maintainer-sponsored when a PR (a) passes the deterministic hygiene checks, (b) touches no sensitive paths (workflows, release automation, auth/secrets), and optionally (c) comes from an author with previously merged PRs. Everything else keeps manual review. Alternatively, run CI in a restricted mode by default and require the label only to merge, not to test.

Effect: contributors can verify and test while waiting instead of stalling; you still have the final say at merge time; less stale-branch churn and rebase fatigue for everyone.

Would you consider it? Happy to help scope the path allowlist or draft the workflow change.