Lab #2459: Docs: document --datastore-poll-interval and the timer duration maximum in serve-flags.md

What changed

swamp-club#2446 adds a setting to swamp serve and a limit to every duration flag that drives a timer. The manual page content/manual/reference/swamp-serve/serve-flags.md documents every serve flag, serve.yaml key and env var, and needs both.

1. New setting: datastore poll interval

Surface	Name
CLI flag	`--datastore-poll-interval <duration>` (also on `swamp serve daemon enable`)
Env var	`SWAMP_DATASTORE_POLL_INTERVAL`
`serve.yaml` key	`datastore-poll-interval` (string)

What it does: how often serve pulls config, access data (grants and groups) and runtime data from a remote datastore. It sets all three pollers (ConfigPoller, AccessDataPoller, RuntimeDataPoller).
Default 30s (unchanged behaviour when unset). Minimum 1s. Accepts seconds (30), or units (30s, 1m, 1h); milliseconds are rejected.
Precedence: CLI flag, then env var, then serve.yaml.
No effect without a remote datastore; serve logs a warning if it is set with a filesystem datastore.
Operator guidance: this is how stale a peer instance can be. Lower values make instances converge faster at the cost of more list/get calls against the bucket. In a MinIO test with two instances, a model created on one appeared on the other in 1.1 to 2.6 s at 2s, against 29 s at the default.

Suggested places on the page:

The flag table (next to --heartbeat-interval and --hydration-timeout, around line 40).
The serve.yaml key table (around line 159) and the example serve.yaml (around line 322).
The env var table (around line 365).

2. Maximum on timer durations

Duration values above 2147483647 ms (about 24.8 days) are now rejected with <flag> (<value>) exceeds the maximum safe timer duration (~24.8 days). Previously Deno fired such a timer after 1 ms, so a timeout aborted at once and an interval loop ran continuously. Affected:

swamp serve: --heartbeat-interval, --reconciliation-interval, --group-refresh-interval, --hydration-timeout, --datastore-poll-interval, --max-run-duration (which already had this limit)
--timeout on swamp workflow run, swamp model method run, swamp workflow resume
swamp worker connect --idle-timeout

A one-line note under the serve flag table would cover the serve flags. The --timeout and --idle-timeout references, if the manual documents them, could carry the same note.

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

Docs: run-workflows-on-a-schedule tells readers to curl /health for queue state, which no longer lists schedules

Collective invite shows "This invitation has expired or has already been used" after a successful join via Google sign-in

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

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

serve: dispatch to an idle worker waits for its worker_busy write on the shared gateway transition tail

serve: worker enrollment resolves and creates the worker definition inside the serialized gateway transition tail

Rescore every extension's current version under rubric v5

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

swamp serve on a v3 datastore never settles a workflow run left running by a stopped instance: boot reaper skips it as belonging to a remote instance

swamp serve on a v3 datastore: a run interrupted at a clean shutdown is never committed when the bucket is slow, and stays running for every other checkout

Support creating 1Password vaults for new clients

Filesystem datastore: an unclean shutdown leaves zero-byte data versions as the latest version, and `doctor datastores --repair` does not detect them

datastore_v3_replica_verify_test stall case flakes under the full integration run: restore.pid is read before the stub writes it

Generated state schemas require every child of nested objects, so normal resources warn on create/get

Add LinkedIn as a login provider

Showcase reward backfill can double-pay 5,000,000 points when replicas start together

Showcase editor: caption counter is not announced to screen readers

Profile showcase read: approved list sorts on review.reviewedAt in memory

Showcase countByStatus: $match live statuses before the $group

Showcase admin queues: index-serve the updatedAt sort on approved/rejected

Annotate and retain past workflow runs and data after the fact

Docs: --trusted-hosts accepts host:port for public addresses on non-default ports

A workflow step's method output is invisible to `data query` and `data list`, and the method summary's retrieval command returns an older run's data

Skill propulsion rule is silent when no transition is satisfied because stage work is outstanding

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

serve shutdown does not wait for worker status writes, and its listener accepts workers after the gateway is disposed

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

auth token create --json fields key and signinToken are undocumented; no token-mode service setup page

trigger.schedule is evaluated in the serve host's local time zone, with no zone field and no doc saying so

workflow validate/run say "Workflow not found" for a file that doctor workflows explains is misnamed

telemetry stats says "No telemetry data found" right after successful sends; say the spool is empty because it flushed

Docs: publish typed-secrets Phase 4.6 expression and delivery semantics

Extension registry page: a supported way to include media (images) in the README

CEL: data.latest(...).version is a double, but data.version() only accepts int, so "version - 1" fails at run time

workflow resume --run refuses workflows with the same step name in two jobs, though validate and run accept them

Update public OpenTelemetry manual for remote waterfalls and execution metrics (#3786)

Server-driven warning and info messages to CLI users, targeted by swamp version (exploration)

Serve: delegate namespace-scoped extension pulls and reload without granting administrator access

workflow cancel --server ignores --ca-cert and SWAMP_CA_CERT

Preserve active worker execution across serve restarts and upgrades; reconnect and reattach dispatches

v3: chunk durability barrier costs a full drive-cache flush per command on macOS; use an ordering barrier

vary/forEach object values with no key/name/id produce data names Windows refuses

issue-lifecycle start drops issue comments: context.comments is always empty

swamp core: a non-string sensitive value reads back as a JSON string

Generated vault keys carry raw data-name and vary characters that strict vault providers reject

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

extension install and extension pull leave different bundles for the same extension version

Registry drops contentMetadata.extensions (method grafts) at confirm-push

Multi-model skill eval: gpt-5.4 and gemini jobs fail preflight every run (OpenAI credits exhausted, Google API key invalid)

local_source_failed drops the indexing error: a transient local extension failure leaves no cause (follow-up to 1672)

Finer-grained method locking: a long-running method on one definition blocks unrelated objects managed by the same definition

Surface (or warn about) values a model method returns besides dataHandles, with sensitive-field support

workflow placement: run a workflow transparently on a specified host, local or via swamp workers (incl. nested child workflows)

issue-lifecycle: pr_merged and ship report success and advance the phase when swamp-club is unreachable, writing nothing upstream

auth login leaves auth.json apiKey empty and stores the key only in ~/.config/swamp/api-key, which the auth gate never reads

swamp-extensions CI: Review Integrity explains a stalled or failed audit (streamed progress, timeout, did-not-finish comment)

Workflow run cancellation on concurrency-key conflict

Read non-string sensitive resource fields back with their type

Run index repair-by-stat misses an in-place, same-size record rewrite that restores mtime within the same second as its entry: ctime is reported in whole seconds

Configurable storage tiers: runs, outputs, data versions and audit move through an ordered list of user-defined tiers, and stay queryable across them

A global argument that evaluates to swamp-namespace expression text is silently dropped, and literal() cannot pass it through

serve: the per-IP WebSocket burst limit can't be configured, so workers behind one NAT IP throttle each other

S3-backed serve: a poll that pulls one file invalidates the whole data catalog, so the next query re-reads every version

extensions_search index is never created if the first attempt fails, until the process restarts

S3/GCS datastore sync: shared sync service lets one sync clear another's dirty marks and pull over unpushed files

swamp-uat: the SIGTERM drain test does not check that the run succeeded

stagecraft: a factory-wide read of work items waiting on a person (no studio, no per-item status loop)

stagecraft: rebind a work item to another tracker (mirrored built-in tickets to Jira)

s3-datastore: first push on a fresh cache prints 'Index merge failed' for a missing local .datastore-index.json

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

stagecraft: studio state_test 'after its event stream reconnects' is timing-flaky under load