forked from longtao.wu/droboticflow
The new 运维助手 page (/assistant) is the third entry point to the ops catalog. "/" runs a catalog action directly; free text goes to a tool-calling model when AI is configured. Every execution is authorized by the action's tier against the caller's current role, recorded as an assistantSteps audit record, and kept honest: - HTTP actions are replayed in-process through the normal router as the user, so route role checks and organization scoping still apply. - Script actions run droctl in an admin-only ops-runner Job (Dockerfile.ops-runner, ServiceAccount droboticflow-ops-runner with a Role limited to what product-surface scripts call: no pods/exec, secrets by name). They stay listed but not runnable until OPS_RUNNER_IMAGE is set. - Mutating actions dry-run by default where the script supports it; confirm-required actions and every real mutation the model proposes wait for the user, and the user is re-loaded before each execution. - Session claims and step finalization are compare-and-set so the two API replicas never double-run a model turn or a completion. poc.configure-fixtures becomes CLI-only because it needs kubectl exec. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>