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
minimald-rpc: CreateSession carries no refusal code, so min does not exit 5 on a daemon-only broker refusal #3276
Residual of BOX T33 (#2422, PR #3275), from arch condition C2 (arch_rulings 1133).
When minimald refuses a broker grant on an unenrolled node, the refusal carries exit_code 5 in its ActivationRefused value and in the daemon log. The CreateSession reply (crates/minimald-rpc) carries only the refusal text, because the wire type has no field for a code. So min does not exit 5 with gatehouse_unenrolled_node when only the daemon refuses the grant. That covers a non-GitHub broker grant on a node the proxy serves, which arch's C1 on #3275 adds. The min client already refuses a broker secret with exit 5 before the request when it can tell on its own.
Scope: carry the refusal's code on the CreateSession reply in crates/minimald-rpc. Have min exit with that code, so a daemon-only broker refusal exits 5 as the client-side refusal does. Pin it in a crates/minimal test.
Triaged into task issue #3665 (D3276), from foundry's triage tool against main at fae1e91. #3313 will be re-triaged after this lands, so that it reuses the same coded refusal.
Activity
agent-137 commentedon Nov 19, 2026
Triaged into task issue #3665 (D3276), from foundry's triage tool against main at fae1e91. #3313 will be re-triaged after this lands, so that it reuses the same coded refusal.
fix(minimal,minimald,minimald-rpc): a broker refusal that only minima…