feat(scheduler): capability-aware tryClaimJob + registerWorker

janpeter commented

2026-06-01 15:27:38 +02:00

Owner

Phase A.3 of 5 (final mcp-side change). Bumps scrum4me-shared submodule to PR #6 merge (96612d4) which adds the WorkerCapability enum + ClaudeWorker.capability field. Adds buildHigherTierIdleFragment helper (Prisma.Sql NOT EXISTS clause) and wires it into tryClaimJob: a worker only claims if no other alive idle worker exists with strictly higher capability for the same user+runtime. registerWorker now accepts the capability so scrum4me-docker can pass WORKER_CAPABILITY in Phase B.

Backwards-compatible: capability field is nullable, the NOT EXISTS uses NULL semantics so unpopulated workers behave as today.

DEPENDENCY for merge: Scrum4Me PR #62 (Phase A.2 — the Prisma migration) must be deployed to Neon prod before this PR can safely be released to workers in production. Until then, queries reference a column that does not exist.

Spec/plan: scrum4me-docker docs/superpowers/specs/2026-05-31-worker-capability-scheduling-design.md and docs/superpowers/plans/2026-05-31-worker-capability-scheduling.md (Phase A.3).

Phase A.3 of 5 (final mcp-side change). Bumps scrum4me-shared submodule to PR #6 merge (96612d4) which adds the WorkerCapability enum + ClaudeWorker.capability field. Adds buildHigherTierIdleFragment helper (Prisma.Sql NOT EXISTS clause) and wires it into tryClaimJob: a worker only claims if no other alive idle worker exists with strictly higher capability for the same user+runtime. registerWorker now accepts the capability so scrum4me-docker can pass WORKER_CAPABILITY in Phase B. Backwards-compatible: capability field is nullable, the NOT EXISTS uses NULL semantics so unpopulated workers behave as today. DEPENDENCY for merge: Scrum4Me PR #62 (Phase A.2 — the Prisma migration) must be deployed to Neon prod before this PR can safely be released to workers in production. Until then, queries reference a column that does not exist. Spec/plan: scrum4me-docker docs/superpowers/specs/2026-05-31-worker-capability-scheduling-design.md and docs/superpowers/plans/2026-05-31-worker-capability-scheduling.md (Phase A.3).

janpeter added 4 commits

2026-06-01 15:27:38 +02:00

feat(scheduler): bump scrum4me-shared for ClaudeWorker.capability bfcbd41ad9

feat(scheduler): registerWorker accepts capability tier e19cee637b

feat(scheduler): add buildHigherTierIdleFragment SQL helper f81441dac3

feat(scheduler): tryClaimJob honors caller capability tier 2631776b47

janpeter added 1 commit

2026-06-01 15:42:33 +02:00

fix(scheduler): drop out-of-scope tsconfig path workaround 032c20bce3

Commit e19cee6 added a path mapping for @prisma/client as a workaround
for type resolution in the sparse worktree node_modules. That workaround
was never necessary in the final code — worker.ts uses a local string-union
type for WorkerCapability instead of importing from @prisma/client.
Reverting per Phase A.3 spec which forbade tsconfig changes.

The worktree-local @prisma/client wrapper that makes types resolve cleanly
is created on developer machines by 'npm install --no-save @prisma/client'
in the worktree (or 'npm ci'), not by a committed config change.

janpeter added 1 commit

2026-06-01 15:51:34 +02:00

fix(scheduler): registerWorker propagates null to clear capability c67723fc11

Previously `opts.capability ?? undefined` collapsed null and undefined
to the same outcome, so callers passing null (to clear the field) had
no effect on the UPDATE branch — the existing DB value persisted. This
bites in the Phase B rollout window: a worker container restarting
without WORKER_CAPABILITY env-var receives null, but the DB silently
keeps its previous tier, so the claim filter routes against stale
data.

Distinguish null (clear) from undefined (omit) explicitly. Adds a
regression test for the null path.

janpeter merged commit 319a3bc6c1 into main

2026-06-01 17:27:11 +02:00

janpeter referenced this pull request from a commit

2026-06-01 17:27:12 +02:00

Merge pull request 'feat(scheduler): capability-aware tryClaimJob + registerWorker' (#31) from feat/worker-capability-scheduler into main

Rows
Columns

feat(scheduler): capability-aware tryClaimJob + registerWorker #31