You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
gate-114 header-action-budget ships advisory: what has to happen before it blocks #724
Gate 114 (header-action-budget) ships advisory. It reports a page whose header actions bar grew against the delta base, and it does not block the merge.
Why it is not blocking yet
This package resolves at @main for all 21 core apps. A blocking gate lands fleet-wide the minute it merges and fails every repository carrying inherited debt.
Census across the fleet's working copies on 2026-09-09:
app
longest bar
page
dossiq
12
CaseDetail
hrmq
3
PayrollRunDetail
hermiq
3
AgentDetail
larpingapp
3
Dashboard
openconnector, pipelinq, shillinq
2
various
the other 13
0
none declare header actions
The ratchet only refuses growth, so nobody is red on day one. It stays advisory until the bars that exist have been looked at, because a warning that has never been read is not evidence that the rule is right.
How to turn it on
Per repo, the gate-112 and gate-113 convention: set HYDRA_GATE_HEADER_ACTION_BUDGET_BLOCKING=1 for that app once its bar is worked down. Fleet-wide promotion means editing the runner and arm 2 of scripts/lib/test_gate114_header_action_budget_scope.sh, which pins that the warning never reaches the failure count.
What has to happen first
dossiq's case page carries 12 actions, and at least one is an exact duplicate of a button already on the page. Work that down.
Decide whether 12 is the outlier or the leading indicator, by reading the census on a few more runs.
Then flip dossiq to blocking on its own, and let the rest follow.
Activity