Lab #3994: Five Mongo queues can hand the same row to two replicas

Problem

Five Mongo queues claim work by a find followed by a separate updateMany that marks the rows processing. Every replica runs their watchers, so two replicas that poll between each other's find and updateMany both take the same rows.

lib/infrastructure/mongo-feed-judge-queue.ts
lib/infrastructure/mongo-attio-sync-queue.ts
lib/infrastructure/mongo-resend-contact-queue.ts
lib/infrastructure/mongo-system-message-queue.ts
lib/infrastructure/mongo-returning-trial-queue.ts

Depending on the queue, a duplicate claim judges a feed submission twice, syncs a CRM record twice, or sends a message or email twice.

Expected

Each row is claimed by exactly one replica: one findOneAndUpdate per row, as mongo-inbox-email-queue.ts claimPending already does, keeping the 5 minute stale-processing reclaim. Check each queue's batch size against that window: a batch claimed at once but processed serially can outlast it and be reclaimed while still queued in memory.

Found while triaging swamp-club#3979, which fixes the same race in the extension scoring queue.

judgeRunRecord lets a forged record settle a waiting approval gate to skipped without an approve

Extension dependencies: the shared import scan reads Babel syntax, not tokens (follow-up to #3969)

swamp-extensions: use explicit npm:/jsr: specifiers in root extensions/models

bundleExtension same-cache test can pass with a broken first-bundle gate under CPU load

bundleExtension 'bundles on different caches do not wait for each other' test fails under CPU load

extension pull: safety analysis scans the bundle the extension runs

Extension scoring queue: two replicas can claim the same pending event

Registry: bump @swamp-club/extension-scoring to the version carrying #3983 (and #3845) before the v5 rescore

Five Mongo queues can hand the same row to two replicas

Registry rescore: secret-safe-docs passes a secret README line on versions whose stored metadata predates the sensitive flag (follow-up to #3783)

Score extensions with @swamp-club/extension-scoring (rubric v5) instead of the registry's own copy

Move the Zod argument-field extractor into @swamp-club/extension-scoring so the CLI and registry read schemas alike

Extension dependencies: one resolver for push, quality and fmt (no behaviour change)

Docs: extension quality scores with the registry formula and reports grade (swamp-club#3845)

Rescore every extension's current version under rubric v5

extension push: a swamp-quality-ignore directive after a comment holding an apostrophe is silently ignored

Share the extension quality rubric between the swamp CLI and swamp-club instead of mirroring it

Manual: the supported extension dependency categories, the canonical form and the lock rule, rewritten once against the final design

Registry audits v2 extension archives as written, and a range costs the loose point only without a valid lock

Extension consumers keep the publisher's bundle: pull, update and auto-resolve stop rebuilding (direction A for #3634)

Extension push: inputs that open up (workspace root lock, ancestor config refused by name, JSR dist-tags) and the skill docs rewritten once

Extension push ships the canonical form: every npm:/jsr: import pinned exact, and a v2 dependency-audit.json

stagecraft studio: show a factory's open tickets that have no work item yet on the Board

stagecraft studio ticket columns: round-5 review lows from #3828 (source watch cost, relationText lookup, cross-instance claim)

A long-lived serve client for extensions, and a stable rate_limited error code

Docs: dependency trust across push, quality, fmt and the registry — Deno-config resolution, read-only lock, package.json mode, the archive's audit record (merges #3728)

extension push (package.json mode): two installed copies under one declared range are audited once, so the second shipped version goes unaudited

cve/emudhra page: Windows and macOS support, and shared CVE layer fixes (follow-up to #3710 and #3766)

@swamp/cve/php-rce-2026-10: match RHEL fixes for the PHP RCEs

@swamp/cve/dirtyfrag: report and README print the old swamp model command spelling

package.json mode: no loose-specifier warning for a range push ships as the exact installed version

extension fmt (and any command) creates or rewrites deno.lock when the extension lives in the repo's loaded extensions/ dir

method run masks a sensitive array from --input element by element, exposing its shape (regression from #3752)

Registry scorecard: score secret-safe-docs (rubric v4) and keep sensitive on extracted arguments

Registry dependency audit: audit the locked version push records in the archive, not the registry's newest match for a range specifier (swamp-club half of #3662)

stagecraft: rename work mode `method` to `behavior`, matching swamp's rename of models to behaviors

extension push: record each dependency's audited (locked) version in the archive, so the registry audits what ships (swamp half; registry half #3778)

main fails type check: query_view_test.ts passes a namespace string where expressionQueryView now takes a NamespaceReader (semantic conflict between #3790 and #3785)

forEachNameWithoutSecrets property test fails intermittently: an empty-string secret and an overlapping recorded value give different names

extension push finds no local modules when a folder above the repo is named node_modules

extension push (package.json mode): audit dependencies resolved through package.json, and leave the author's node_modules/ unchanged (merges #3632)

Local verification docs still tell agents to put ANTHROPIC_API_KEY in verify.env for reviews

@swamp/cve/php-rce-2026-10 follow-ups: dry-run heading, command spelling, Debian 12 fix, podman image scan

extension push resolves the Deno config and import map the way Deno does: deno.jsonc, importMap file references and scopes

extension fmt --check writes deno.lock in deno.json mode, which push and quality then bundle against with --frozen

@swamp/cve/dirtyfrag: scan logs are never saved (file writer handle dropped, data name collides with the status resource)

audit_deps.ts skips cve/ extensions, so their deno.lock files are never dependency-audited

@swamp/cve/dirtyfrag README shows --input targetHost/sshUser/sshKey/dockerContainer, which the CLI rejects

@swamp/cve/dirtyfrag mitigate uses interactive sudo, so it can hang on a password prompt or fail mid-run

extension quality names the wrong cause: a bundle failure prints no reason, the not-audited row always blames an outage, and symbols-docs blames JSDoc when deno doc failed

Relationships

#3994 Five Mongo queues can hand the same row to two replicas

Problem

Expected

Open