feat: multi-worker instance_id presence + claim routing

janpeter commented

2026-05-27 10:26:15 +02:00

Owner

Bumps vendor/scrum4me-shared submodule to multi-worker-aware version. Updates registerWorker (composite-key UPSERT), startHeartbeat (composite-key WHERE), tryClaimJob (writes worker_instance_id), rollbackClaim (clears worker_instance_id — Codex P1-3), resetStaleClaimedJobs requeue path (clears worker_instance_id; FAILED path retains for forensics). Adds 4 tests, 522/522 pass.

janpeter added 3 commits

2026-05-27 10:26:15 +02:00

feat(schema): bump shared submodule + multi_worker_instance migration 519a5a3843

Bumps vendor/scrum4me-shared to 1446d2c (feat/multi-worker-
instance-id) which adds instance_id/hostname/pid to ClaudeWorker,
drops @@unique([token_id]), adds composite unique, and changes
ApiToken back-relation to one-to-many ClaudeWorker[].

Regenerates prisma/schema.prisma and adds migration multi_worker_instance:
- Three new claude_workers columns (additive, default 'legacy')
- Drops single-token unique index
- Adds composite unique (user_id, token_id, instance_id)
- Adds claude_jobs.worker_instance_id + index

Migration is NOT applied — to be deployed in sub-step 3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

fix: remove misplaced migration 14ba8acd38

Migrations are managed in the Scrum4Me main app repo, not in
scrum4me-mcp. The submodule-bump + regenerated schema.prisma stays
(needed for prisma generate to produce up-to-date types for the
runtime), but the migration SQL file belongs in
Scrum4Me/prisma/migrations/.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

feat(workers): instance_id in registerWorker, tryClaimJob, rollback 772bbc377b

- registerWorker UPSERTs by composite key (user_id, token_id, instance_id)
  with hostname/pid on create-only; heartbeat update by composite key.
- startHeartbeat takes instanceId and uses it in the updateMany WHERE.
- unregisterWorker scopes delete by composite key so only the exiting
  instance is retired (was: deleteMany by token_id alone).
- src/index.ts reads SCRUM4ME_INSTANCE_ID via new getInstanceId() helper
  (default 'legacy' to match the DB column default for back-compat) and
  threads it through registerWorker/startHeartbeat/registerShutdownHandlers.
- tryClaimJob accepts instanceId and writes worker_instance_id on claim.
- rollbackClaim clears worker_instance_id (was missing - Codex P1-3).
- resetStaleClaimedJobs requeue path clears worker_instance_id; FAILED
  path retains it for forensic diagnosis (unchanged).

Tests:
- registerWorker writes row via composite-key upsert with given instance_id
  and hostname/pid present in create payload, absent in update payload.
- Two (user, token, instance_id) rows coexist (blocked previously by
  @@unique([token_id])) - now allowed by composite unique.
- tryClaimJob writes worker_instance_id, rollbackClaim clears it, a
  second claim by another instance rotates the value cleanly.
- Stale requeue clears worker_instance_id; stale FAILED leaves it intact.

run-one-job.ts in scrum4me-docker wiring (setting SCRUM4ME_INSTANCE_ID
when spawning Claude) is deferred to Phase 3 Task 3.3.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

janpeter merged commit 159b0b5d83 into main

2026-05-27 10:26:16 +02:00

janpeter referenced this pull request from a commit

2026-05-27 10:26:17 +02:00

Merge pull request 'feat: multi-worker instance_id presence + claim routing' (#17) from feat/multi-worker-instance-id into main

janpeter referenced this pull request

2026-06-14 16:33:06 +02:00

feat(mcp): update_idea tool + update_idea_grill_md productgrens (slice-1 Laag B) #54

janpeter referenced this pull request from a commit

2026-06-14 16:33:07 +02:00

chore(mcp): bump shared submodule -> A1-merge-commit (update_idea RO-entry + content-policy)

Rows
Columns

feat: multi-worker instance_id presence + claim routing #17