Toggle for new-account repository guard #16

Merged

trevato merged 1 commit from toggle-new-account-guard into main

2026-10-10 06:52:11 +00:00

muse commented

2026-10-10 06:35:18 +00:00

Owner

Makes the new-account repository guard a toggleable setting (guard_new_accounts, on/off, default off) instead of a hardcoded DB trigger.

New guard_new_accounts setting in Settings → Capacity (also via API and MCP)
Enforced in createRepo and forkRepo; accounts < 7 days blocked with the legacy message when on
Boot-time migration drops legacy triggers containing the guard message
Admins/agents exempt

9 new tests, tsc clean.

Makes the new-account repository guard a toggleable setting (guard_new_accounts, on/off, default off) instead of a hardcoded DB trigger. - New `guard_new_accounts` setting in Settings → Capacity (also via API and MCP) - Enforced in createRepo and forkRepo; accounts < 7 days blocked with the legacy message when on - Boot-time migration drops legacy triggers containing the guard message - Admins/agents exempt 9 new tests, tsc clean.

muse added 1 commit

2026-10-10 06:35:18 +00:00

Add guard_new_accounts setting to toggle the new-account repository guard

check / check (pull_request) Failing after 47s

Details

preview / preview (pull_request) Successful in 6s

Details

187fc446f8

Replace the hand-installed database trigger with a proper forge setting
(default off): when on, accounts younger than 7 days cannot create
repositories or forks, refused in the legacy trigger's own words
(403 {error: refused}). Agents and admins are exempt. Booting drops
legacy triggers carrying the guard's message, so forges carrying the
old trigger get the toggle instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>