Lab: Extension bundle cache does not invalidate on source edits

Problem

When a local extension source is registered with swamp extension source add <path>, swamp builds a .js bundle at <repo>/.swamp/bundles/<hash>/<model>/<model>.js. Subsequent edits to the source .ts files do not invalidate this bundle — swamp model type describe and swamp model method run keep loading the stale .js even though the source has changed.

There is no documented way to force a rebuild:

swamp extension source rm <path> followed by swamp extension source add <path> does not rebuild the bundle.
The cache-key hash (e.g. e9c5c01e) is stable across source edits.
The only working invalidator I found is manually rm'ing the bundle .js. The next type-describe / method-run then rebuilds correctly from source.

Reproduction

swamp extension source add /path/to/dev/checkout
swamp model type describe @hivemq/mymodel --json — bundle gets built at .swamp/bundles/<hash>/mymodel/mymodel.js
Edit extensions/models/mymodel/mymodel.ts to add a new method foo
swamp model type describe @hivemq/mymodel --json again — methods does not include foo
swamp model method run my-instance foo → "method not found"
Workaround: rm <repo>/.swamp/bundles/<hash>/mymodel/mymodel.js and retry — now foo is registered

Impact

This bites hard during local development of pull-based extensions where the user's swamp repo (e.g. ~/.mudroom) has a dev checkout registered as a source and is expected to pick up edits. The failure is silent: wrapper scripts hit "method not found" and exit non-zero, often with the error swallowed by >/dev/null in shell glue.

We hit it twice on @hivemq/mudroom — once on the publisher's checkout, once on the consumer's ~/.mudroom repo. Both times the only repair was manually rming the bundle file.

Proposed solutions (any of these would resolve)

Source mtime check: when loading a bundle, compare its mtime against the max mtime of source .ts files under the registered source path; rebuild if source is newer.
Content-hash key: derive the bundle dir name from a hash of the source tree contents, so any edit naturally produces a fresh bundle and the old one becomes garbage.
Explicit subcommand: swamp extension rebuild <type> or swamp extension cache invalidate <type> for users who want manual control.
Make swamp extension source rm/add invalidate the relevant bundles as a side effect — this matches the existing mental model of "I removed and re-added the source".

Option 1 or 2 would be the most ergonomic. Option 3 is a fine stopgap.

Environment

swamp version: 20260506.233640.0-sha.5729ac50
Platform: macOS arm64
Affected workflows: local extension development, dev/consumer parity testing, mudroom-style "pulled by user, edited by maintainer" loops

swamp issue get should rate-limit unauthenticated users instead of blocking

swamp issue get should not require authentication

telemetry: emit child entries for follow-up action method invocations

Publish release-candidate / unstable extension versions

extension source rm leaves stale @local/. rows in catalog, blocking later pulls of registry types

extension push drops binaries: field from re-emitted archive manifest.yaml

macOS launchd autoupdate (club.swamp.autoupdate) silently fails — binary stays stale

Clicking @hivemq/honeycomb extension card on /extensions shows 'Something went wrong'

Docs: Update model-definitions.md and workflows.md for direct type execution

Docs: document binaries manifest field in extension-manifest.md

Add an official @swamp/ssh extension for general-purpose SSH (brownfield-friendly)

Accept and display binaries field from extension push metadata

Direct type execution: collapse model create + method run into one command

Per-method telemetry events for workflow runs

Workflow run liveness: orphaned 'running' records when originating CLI process dies mid-run

Provide a CLI-shape primer for AI agents to reduce rediscovery overhead

quality rubric: don't penalize extensions whose upstream constrains them to a single platform

Extension update rejects multiple .ts files extending the same target type within one local extension (regression)

swamp extension push deadlocks when invoked from inside a swamp workflow step

Collective-scoped auth keys + OIDC federation for CI publishing

forEach self.* in modelIdOrName not resolved in runtime execution path

Award leaderboard points for referrals and collective invites

Add agent harness detection and AiTool to telemetry

Workflow-level runtime expressions (env.*, vault.*) not resolved in driverConfig — docker driver receives literal ${{ ... }} strings

Implement W5: Per-fingerprint import URLs + subprocess test harness (extension catalog rearchitecture)

swamp config set crashes with YAML serialization error

datastore compact: VACUUM fails in compiled binary (SQLITE_LIMIT_ATTACHED=0)

Repo-level version gating: minSwampVersion high-water mark for team consistency

Docs: document self.* expressions in modelIdOrName during forEach

Docs: How-to guide for background autoupdating

Manifest version bumps silently ignored for existing local extension aggregates

materialiseExtensions misclassifies pulled rows when manifest name collides with a pulled extension

Local extension edits don't reliably trigger rebundle

Missing unique indexes on user.email and user.username allow duplicate users

Resolve self.* expressions in modelIdOrName during forEach expansion

discord-bot double-sends sign_up notifications

Discord bot sends duplicate signup notifications

Add 'swamp workflow list' as alias for 'swamp workflow search'

Add 'swamp auth status' as alias for 'swamp auth whoami'

Extension bundle cache does not invalidate on source edits

extension pull fails on @local/[email protected] phantom-claim collision when local repo has its own extension

Lab search by numeric issue ID returns no results

W3 sourceToRow writes empty source_mtime — should carry filesystem mtime through Source entity

Warm-start rebundleAndUpdateCatalog should respect terminal RowStates set by reconcile

Implement W4: KindAdapter + unified loader (extension catalog rearchitecture)

Docs: add vault read-secret command to reference manual

Extension layer garbage collection: prune catalog rows + evict orphaned bundles

Docs: document workflow concurrency limits in reference manual

Locally-sourced extension: source_mtime updates without regenerating stale bundle

Extension push: allow shipping executable host helpers (bin/mudroom blocker)

Vault expressions silently deliver __SWAMP_VSEC__ sentinels under the docker driver

First-class shell-shim support for extensions, with registry-level visibility

Local extension model bundles don't rebuild when source changes (no rebuild CLI; manual cache delete breaks the runner)

Configurable concurrency limits for workflow fan-out (forEach, parallel jobs/steps)

feat(security): redact sensitive method arg values from audit log

docs: document swamp datastore compact and GC WAL behaviour

UAT: swamp datastore compact reclaims WAL and catalog space

Plan v4 step 9 literal test untestable under current catalog PK semantics

Cross-process concurrency stress for W2 lifecycle services

UAT additions for W2 lifecycle services (Install/Remove/Upgrade)

Implement W3: ReconcileFromDisk + freshness-as-aggregate-query (extension catalog rearchitecture)

doctor extensions repair: clean catalog-only orphans

Extensions should be able to ship Claude Code skills

Pre-existing TOCTOU windows in YAML repo walkers (findAll directory level + findById)

`swamp datastore setup` migration is not resumable / leaves the repo in a partial state on failure

Built-in models must honor AbortSignal so --timeout works in practice

Reader-lock or lock-free read path for data list/get/search/query

data search: surface jobTag alongside workflowTag and stepTag (follow-up to #237)

global-arg silently strips unknown keys; should reject via strict Zod schema

redmine extension: adopt state machine patterns from @magistr for agent-driven workflows

performance degrades significantly with large SQLite catalog

summarise: timeout/hang on repos with many workflow runs

extension quality/fmt fail on pulled extensions (path mismatch)

vault: add read-secret CLI command for agent-driven secret retrieval

data query: stepName and jobName fields always empty in CEL results

Extension ecosystem: shared utility library, version sync tooling, and HTTP resilience patterns

Agentic CLI improvements: --json stdout isolation, array inputs, and --repo-dir consistency

data delete fails with "Directory not empty (os error 39)" when concurrent writes are active

Extract LockfileRepository (W2 prequel for swamp-club#231)

Extend DatastoreSyncService.markDirty() with optional relPath argument

Workflow-level runtime expressions (env., vault.) not resolved in driverConfig — docker driver receives literal ${{ ... }} strings