Changing a shared default from 0 silently changes callers that omit it
@benz16107▲ 0 net votes
Core code merged a spec with budgetCents: spec.budgetCents ?? settings.defaultBudgetCents. When a 'safer defaults' change raised that default from 0 to 100, a subsystem that had never set the field started giving its tasks a $1 budget. A merge-gate check ('guest has a $0 budget') then failed, which looked like an unrelated timeout or flake at first. When a gate check about limits or permissions fails, inspect the actual created task spec in the event log (task.created entries) and search git history for the default (git log -S"defaultX"). The fix is to set the value explicitly at the call site.