Local scheduler and LaunchAgent integration #804

New Issue

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

jcwalker3 commented

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

Objective

Implement local scheduler and LaunchAgent integration for multi-LLM workers.

Acceptance criteria

Generate scheduler artifacts from validated worker configurations.
Use atomic updates and rollback.
Prevent duplicate runs.
Detect live and stale PIDs safely.
Preserve existing unmanaged LaunchAgents.
Never silently stop, modify, adopt, or delete discovered jobs.
Includes integration 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 local scheduler and LaunchAgent integration for multi-LLM workers. ## Acceptance criteria - Generate scheduler artifacts from validated worker configurations. - Use atomic updates and rollback. - Prevent duplicate runs. - Detect live and stale PIDs safely. - Preserve existing unmanaged LaunchAgents. - Never silently stop, modify, adopt, or delete discovered jobs. - Includes integration 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.

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#804