Lab #3073: serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once

Summary

Follow-up to #2481 (fixed in swamp-club/swamp#2861). A running replica now pulls auto-definitions/ with data/ on every poll, so a server token minted on one replica is accepted by its peers within the poll interval. Until a peer's next poll it still rejects the token as unknown.

Why it matters

The default poll interval is 30s, and under steady run load a poller can skip three cycles before it queues for the sync gate, so the window can be about four intervals.
Device login is the case users will hit: device_auth_handler.ts mints the token on one replica and the CLI's next connection can land on another replica straight away, behind a load balancer. The user logs in successfully and is then told authentication failed.
The same window applies to access token mint --server followed by immediate use.

Proposal

On a definition or record miss in readServerTokenRecord (src/serve/token_auth.ts), do one targeted pull of that token's definition and data before failing, then retry the lookup once.

Constraints to design for

The miss path is reachable by unauthenticated callers, so a pull on miss lets anyone trigger datastore reads. It needs a bound: single-flight, plus a minimum interval between miss-driven pulls (per replica, and probably per token name), with a negative result remembered for that interval.
The pull must run under the sync gate like every other pull (gatedPull in src/serve/sync_gate.ts), and must not make connection upgrades wait behind a long-held gate.
Scope the pull as narrowly as the datastore extension allows (the server-token type directory under auto-definitions/ and data/), not the whole subtree.
The client-facing error must stay generic; the reason belongs in the server log only.

Acceptance

With two replicas on a shared remote datastore, a token minted through replica A authenticates on replica B on the first attempt, without waiting for B's poll, and repeated attempts with unknown token names cause a bounded number of datastore pulls.

Reproduction environment

The two-replica MinIO setup used for #2481 is described in that issue's lifecycle record: two repos sharing one S3 datastore, each running swamp serve --auth-mode token --datastore-poll-interval 5s, mint through A with swamp access token mint <name> --principal user:<name> --server <A>, then swamp access can-i --server <B> --token-file <file> --action read --on 'workflow:*'. Read the server log for the result: can-i exits 1 for both an auth failure and an authenticated deny.

Session-start 'swamp model search --json' in the AGENTS.md template is unfulfillable - wire it to a hook or drop it

Flaky property test: analyzeExpression dot/bracket agreement fails when the generated model name is a CEL keyword

Accept usernames for user subjects in grant files

Docs: enable-managed-config should say to re-run config migrate when its push fails

Docs: grant file reference shows a stale format and omits resources and subjects

Flaky property test: analyzeExpression hyphenated dot access fails when modelName generates a CEL keyword ("in")

extension quality and push crash with IsADirectory when additionalFiles lists a directory

extension push: a required global argument renders with a stray "" ("text": "string""")

Docs: extension publishing reference is stale on bare specifiers, quality output and fmt config (swamp-club#3022)

swamp-extensions: replace bare import specifiers with npm:/jsr: specifiers in first-party extensions

extension push: 'Requested visibility' line prints to stdout without the logger prefix, twice per run

A nested structural swamp that outlives the run that started it keeps skipping that run's lock while the holder writes

Show signal waits to remote clients and the dashboard

Settle expired signal waits from swamp serve

Resume signalled workflow runs automatically under swamp serve

extension push/quality: structured acceptances for agents, a clearer title than For next time, and an optional reason

extension push: the undecided private-entitlement verdict still says the registry may start a trial at publish

seed:collective cannot produce a superseded personal trial or a returned trial, so the UAT cannot cover them

Replayable state fragments: Git-reviewable desired state for resources changed by model methods

extension push: registry metadata and content hash label files relative to the repo dir, so a push with --extensions-dir records ../ paths

registry: store and show declared acceptances sent in contentMetadata.acceptances at confirm (swamp-club#3021)

extension push --dry-run: authentication verdict prints 'Signed in as .' when the credential is an API key with no username

serve --remote-only: step output from workers is never persisted to the run log (history logs always empty)

serve HA: worker enrollment on a replica that lacks the enrollment token's definition may create a second definition (unverified)

serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once

extension push: version-drift check reports 'no previously published version found' when the registry call failed

Search and list output follows directory iteration order in the definition, workflow, vault and output repositories

extension push: accept attestation-backed adversarial-review evidence (lookup by extension and content hash), generated provenance, and carry the evidence to the registry at confirm (design: Lab #3023)

Workflow load errors print the raw Zod issue dump instead of a readable message

Decide a stricter naming rule for workflow step and job names

serve: run scheduled workflows concurrently (per-workflow serialization), and report queue delay

Show expired approval gates as expired, with a Cancel action in the dashboard

digitalocean codegen leaves an orphaned security_secret.ts model file after its endpoint left the spec

extension promote accepts a yanked version and reports it promoted

Docs: doctor install reports a stale or failing autoupdate scheduler

extension push output: double-quoted adjacent interpolations, repo-relative paths, and --json emits three JSON documents

auto-resolve: the Installing line prints the extension's entire multi-line description

s3-datastore/serve: readResource without a version returns an older version; the latest marker is rewritten backwards

Publish agent-facing projections of the manual: /llms.txt, .md pages, and llms-full.txt

Let agent-runner drive more agent CLIs (Kilo Code and others)

s3-datastore: every fast-path miss re-downloads every _index shard, so a busy serve pulls the whole index every poll (~230 GB/day S3 egress)

Feedback: Swamp as an approval-gated control plane for a small fleet

extension safety analyzer's Deno.Command( warning is a plain substring match

Tell timeouts apart from cancels in method-run records, and review the hidden 30 s fallback timer for step-called model methods

Run from a git worktree: definitions from the worktree, state from the shared repo

S3/GCS datastore: a push that fails after uploading drops its recorded deletes, so the retry brings deleted data back

Tests: bring the in-memory remote's default semantics up to @swamp/s3-datastore and @swamp/gcs-datastore 2026.10.01.1

Tell the pushing client when its extension contentMetadata fails validation

Extension datastore: query still returns an item after its delete is pulled

Cancel, reject and supersede of a parent run should settle its suspended nested child runs

Relationships

#3073 serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once