chat: implement the sandbox dangerous-command authority (dashboard and Telegram approvals are both unwired) #1574
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1574
Reference in new issue
Block a user
/rollback and /stop approvals cannot work in ANY process, because the authority
they depend on has no production implementation.
EVIDENCE (all verified by hand at
8d3925a8, not inferred)production callers: rg --glob '!*_test.go' returns only the definition.
answer 501 Not Implemented with body "dangerous sandbox actions are not
configured".
but NO production construction of telegramSetup ever sets Dangerous. The only
two non-test literals are bootstrap.go (setupGateways) and
gateway_runtime.go:62 (setupGatewayChat), and both omit it.
been supplied in any commit.
anywhere -- only webDangerousStub / dangerousStub in tests, no
var _ messaging.DangerousCommandAuthorityassertion, and no [dangerous]config key.
881b2c80("delete unwired Router.Dangerous approval path") because all fourproduction Router constructions left it nil.
WHY THIS IS NOT A WIRING FIX
Wiring webui.NewDangerousService(nil) would yield a byte-identical 501 --
internal/webui/dangerous.go enabled() returns that same error for a nil
authority -- so it would be a no-op dressed as a fix. The missing piece is the
capability: a sandbox checkpoint/rollback authority owning checkpoints, pending
actions and decisions.
WHAT IT NEEDS
A decision on where the authority lives (it owns sandbox checkpoints/rollback,
so the container or daemon package is the natural owner) and how it crosses the
UI-service boundary. internal/app/archieui/compose.go:44-47 records that
Events/Curators/Workflows and friends have "no contract exists for these yet"
pending archie-core-8cda.5.3; dangerous actions are in the same class.
SCOPE NOTE
This is larger than the finding that surfaced it. .local/issue-tracker webui-1
framed it as "webui.DangerousService is never constructed" (a webui wiring
defect); the real gap is the absent authority, which leaves BOTH the dashboard
and Telegram's /rollback + /stop approval paths unwired.
Close reason
Obsolete: the dangerous-command authority no longer exists in the tree.
Imported from beads
archie-core-sod1· GitHub #939 · type feature · priority P2 · created 2026-09-18 · closed 2026-10-10