Gated worker controls #805

Open
opened 2026-07-22 05:32:56 -05:00 by jcwalker3 · 0 comments
Owner

Objective

Implement gated worker controls in the Web UI.

Acceptance criteria

  • Provide Run now, Pause, Resume, Restart, and Disable.
  • Use POST, CSRF protection, explicit authorization, confirmation where appropriate, and read-after-write verification.
  • Maintain the existing loopback-only protection.
  • Worker mutations are disabled by default unless the documented local control setting is enabled.
  • Browser input cannot execute arbitrary commands.
  • Includes security tests.

Parent Epic

Parent: #797

Issue-First & Safety Requirements

  • Implementation may begin only from an existing open issue.
  • Author implementation requires canonical routing, a durable issue lock, and a validated author worktree.
  • Read-after-write verification is required for all mutations.
  • Wrong-role and ambiguous-ownership operations fail closed.
## Objective Implement gated worker controls in the Web UI. ## Acceptance criteria - Provide Run now, Pause, Resume, Restart, and Disable. - Use POST, CSRF protection, explicit authorization, confirmation where appropriate, and read-after-write verification. - Maintain the existing loopback-only protection. - Worker mutations are disabled by default unless the documented local control setting is enabled. - Browser input cannot execute arbitrary commands. - Includes security tests. ## Parent Epic Parent: #797 ## Issue-First & Safety Requirements - Implementation may begin only from an existing open issue. - Author implementation requires canonical routing, a durable issue lock, and a validated author worktree. - Read-after-write verification is required for all mutations. - Wrong-role and ambiguous-ownership operations fail closed.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#805