Lab #4223: Hot reload can keep an old local behavior registry and memoized bundle after external catalog indexing (1602; e459 regression passes)

Observed on Linux with Swamp 20261028.205235.0-sha.1602a617, using repo-local behaviors, a shared extension catalog, and serve --hot-reload --remote-only.

Minimal reproduction (disposable repository):

Start serve with a repo-local behavior @example/reload-probe at version 1; describe it remotely (and warm its method bundle if testing dispatch).
Edit its entry to version 2 and change a validator in an imported helper. Add a second local behavior.
Run a separate local CLI model type description to index the edited source into the shared catalog.
Send an acknowledged swamp serve reload --server <loopback endpoint> request. Without running a workflow first, describe the original behavior remotely.

Expected: after successful reload, the existing serve process reports version 2 and future dispatches use the updated validator/bundle, including newly discovered behavior metadata. Actual on 1602a617: disk/indexed catalog have version 2, but the warm serve registry still reports version 1. In production, @nckrtl/tool-direct remained 2026.10.30.3 while disk/catalog were 2026.10.31.1; a subsequent dispatch failed the removed agent_sha256 validator before effects. The old worker-cached JS still declared the old version. We did not establish a cache-key collision or the exact production command that advanced the catalog.

Two full restarts were needed to recover observed stale registries on 2026-10-31, around 08:39Z and 09:43Z. No cache eviction or credential changes were required.

Source investigation: createBundleSourceFactory memoizes bundlePromise and checks sourceSnapshotChanged only during its construction. Catalog state advanced by a different CLI can differ from definitions applied by the warm serve process.

Current release follow-up: serve is now 20261031.063736.0-sha.e459d219. The exact isolated external-index/reload regression fails on 1602a617 and PASSES on e459d219, with the same serve PID throughout and no workflow run required. e459 includes the local-extension reconciliation change associated with PR3523. We have not reproduced this stale-after-successful-reload defect on e459. Please confirm coverage of warm memoized bundles and imported-helper changes, and whether this historical issue is fully resolved by that change.

Worker queryData fails at the fixed 30 s RPC limit while it waits for a full catalog rebuild

cfgmgmt firewall: match rules by destination and comment

Align Caddy reverse-proxy TLS documentation with Kubernetes proxy guidance

Scheduled flaky-test detection is failing

vault put --server: accept the value on stdin (keep secrets out of argv)

swamp serve reaches the V8 heap limit within 2–60 min under a small remote-worker workload (~20 runs, ~3.5k record versions)

Hot reload can keep an old local behavior registry and memoized bundle after external catalog indexing (1602; e459 regression passes)

Add expiring service-account token requests and authorization checks to RBAC

Flaky: v3 replica check stall test reads restore.pid before the stub writes it

Reads other than findById still treat a lapsed temporary ban as active until the operative next signs in

verify-build upgrade gate silently skips models whose version is a constant

@swamp/agent-sessions: explore a decision model (TypeSafe Jev) for call labelling

agent-sessions: follow-ups from the 4211 reviews (repo resolution cache and edge cases)

agent-sessions: revisit the import's remaining review findings (redaction edge cases, import robustness)

Docs: document the datastore durable setting and its macOS ordering in the manual

Docs: working offline against swamp serve (leases, outbox, flush, quarantine) for swamp-club#4195

Swamp Club collective GUI: show the swamp serve instances currently connected to a collective

Docs: swamp data query --sort, --cursor and nextCursor in the data reference

A malformed --ca-cert file is reported as an unreadable OS certificate store

TLS hint blames a missing root CA and macOS for every invalid peer certificate failure

workflow cancel --server does not send SWAMP_SERVE_EXTRA_HEADERS

S3/GCS repairUnpushedFiles: the pull it asks for after a lost last-synced index does not stop it re-uploading copies a peer deleted

swamp-uat private-registry tests leave npm/<port> dirs in the shared Deno cache

Read-model catch-up of many data versions slows sharply under load

swamp serve --groups-field help says group/collective memberships; it names only the collectives field

A resume runs settled work after the teardown gated on it has already run, and nothing tears that work down

A step settled after the abort overwrites the expression-context entry of a same-named step that ran in another job

The extractContentMetadata property test generates invalid source and fails at random

A limited model.output.search copies and sorts the whole listing on the event loop for each request, so that step still scales with the window

Flaky test: access_poll_phase_telemetry_test sees grants_active 1 where the snapshot build read 2 records

A lone step in a job still starts under the aborted signal when another job has suspended the run

CLI command to change an existing extension's visibility (private → public)

Docs: team-mode model leases (swamp behavior lease, lease status in datastore lock status)

serve (token mode): --admins accepts idp-group entries that can never match

build-swamp-extension example: code-review isn't given the quality evidence, so the reviewer reports quality as missing

Filesystem control-plane put races empty-parent cleanup (cron pending-run ENOENT)

deployment: getLogs method (deployment-aware pod log tailing)

Agent sessions extension: import Codex sessions

model.output.search response phase takes 3.9s for 5,000 items with no attribution (redaction vs serialization vs send)

Docs: v3 serve team mode, followers forward writes and the advertise-address and ca-cert serve flags (swamp-club#4120)

Skill/docs: document registry listing limits, static-extraction rules, and splitting large APIs by domain

Check registry listing limits in extension quality/push and suggest splitting into per-domain extensions

Over-limit contentMetadata publishes a blank extension page; archive fallback extracts nothing

swamp inbox: with a filter active, sitting on the last row pages through the whole inbox in the background

@swamp/video/brand: follow-ups from the initial review (render hang, odd sizes, Chromium errors)

@swamp/video: follow-ups from the initial review (card length, input validation, OCR frames on disk)

@swamp/video/hyprland: recording hotkeys, retake marker and phone-mirror window rules

@swamp/video/obs: optional OBS recording with per-person hardware config for @swamp/video

serve daemon enable: add Windows support (service or startup task)

swamp skill docs: publishing.md contradicts itself on dynamic imports, overstates where git dependencies are listed, and never says consumers keep the publisher's bundle

Relationships

#4223 Hot reload can keep an old local behavior registry and memoized bundle after external catalog indexing (1602; e459 regression passes)

Open