Worker readiness and doctor checks #801

New Issue

2026-07-22T05:32:01-05:00

jcwalker3 commented

2026-07-22 05:32:01 -05:00

Objective

Implement worker readiness and doctor checks for multi-LLM workers.

Acceptance criteria

Validate executable, authentication, MCP namespace, identity/profile, repository binding, canonical workflow, runtime parity, and scheduling conflicts.
Return actionable readiness failures.
Activation remains disabled until mandatory checks pass.
Unavailable providers remain visible.
Includes tests for every readiness state.

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 worker readiness and doctor checks for multi-LLM workers. ## Acceptance criteria - Validate executable, authentication, MCP namespace, identity/profile, repository binding, canonical workflow, runtime parity, and scheduling conflicts. - Return actionable readiness failures. - Activation remains disabled until mandatory checks pass. - Unavailable providers remain visible. - Includes tests for every readiness state. ## 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.

jcwalker3 referenced this issue

2026-07-22 06:11:34 -05:00

feat(webui): worker registry and configuration schema (Closes #798) #810

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

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