extension unyank needs -y/--yes flag for non-interactive use

When iterating on a TypeScript extension model loaded via a local source path (a .swamp-sources.yaml path: entry), edits to the source .ts file don't reliably trigger a rebundle. The model continues to execute with code from a stale bundle even after the source has been modified.

The freshness check uses source mtime plus a stored fingerprint in the extension catalog, but in practice these can get out of sync with the actual source contents. Result: editing a model and re-running its method still executes the old code.

Steps to reproduce

Configure a local source in .swamp-sources.yaml with a path: entry.
Run any model method from that source — bundle is created and cached.
Edit the model's .ts file (any non-comment code change).
Re-run the same model method.
Observed: the model executes pre-edit code; the cached bundle is still loaded.

Workaround

All three cache layers must be wiped manually:

Deno transpile cache: rm ~/.cache/deno/gen/file/<absolute-source-path>/<file>.ts.js
Swamp bundle: rm ~/.swamp/repos/<repo-id>/bundles/<hash>/<file>.js
Catalog row: sqlite3 .swamp/_extension_catalog.db "DELETE FROM bundle_types WHERE source_path LIKE '%<file>%';"

Only after wiping all three does the next invocation rebundle from the edited source. Skipping any one of them (most commonly the deno gen cache) leaves the bundle stale.

Environment

Source loaded via .swamp-sources.yaml with path: (not a pulled extension)
Edits made directly to the .ts file in that path
Catalog source_fingerprint was observed to be stale (didn't match the source file's actual sha256) even though source_mtime had advanced

Impact

Adds a multi-step manual workaround to every iteration of local extension development. Easy to forget a layer and waste debugging time on a fix that already worked but isn't loaded.

02Bog Flow

Closed

5/7/2026, 5:18:18 PM

No activity in this phase yet.

03Sludge Pulse

stack72 commented 5/7/2026, 5:17:54 PM

Thanks for the detailed reproduction @keeb — closing this as a duplicate of swamp-club#274.

Same bug class: source-mounted extension's bundle silently fails to rebuild when source edits should trigger it. Root cause is the isExpectedBundleFailure fast-path returning stale cached bundles for user-developed extensions. The stale source_fingerprint you observed is the visible symptom of that path firing without a rebuild attempt.

#274 is in implementation now with two coordinated fixes:

Path-based bypass of isExpectedBundleFailure for non-pulled origins (locals + source-mounted), so user-developed extensions actually attempt to rebuild on every staleness check
One-time BUNDLE_LAYOUT_VERSION bump to repair any catalogs poisoned by the pre-#265 fingerprint bug

After #274 ships (likely within ~3-5 days), please re-verify on current main:

Configure the same .swamp-sources.yaml path entry
Run a method (materializes bundle)
Edit the source file
Re-run — confirm the new code executes without manual cache wiping

One observation worth flagging for the post-#274 re-verification: your workaround wiped the Deno gen cache (~/.cache/deno/gen/...) in addition to the swamp bundle + catalog row. Layers 2 and 3 are what #274 fixes. Layer 1 (Deno gen cache) is unlikely to be load-bearing — deno bundle reads source files directly and shouldn't hit the gen cache. But if after #274 ships, you find the Deno gen cache wipe is still needed to pick up edits, that's a separate concern (likely Deno import-cache aliasing, which is W5's territory in the rearchitecture). File a fresh tracker in that case.

Most likely outcome: #274 fully closes this. The Deno gen cache step turns out to be a red herring from debugging.

Tracking via swamp-club#274 from here. Apologies for the multi-step workaround — visibility on what's actually load-bearing during these failures is exactly what the rearchitecture is supposed to clean up.

extension unyank needs -y/--yes flag for non-interactive use

Step key parsing in execution_service uses naive split(":") and silently truncates colon-containing step names

Workflow-scope report artifacts unreachable via `swamp data get --workflow`

Add --stdin support to method run and workflow run for Unix pipe composition

Docs: add run namespace to CEL expressions reference

Fix invalidate-then-reconcile sequencing in doctor extensions; failure-mode RowStates unreachable in sourceDetails

doctor extensions invalidateAll does not trigger fingerprint recheck for existing Indexed rows

Extension failure recording has dual write paths (legacy buildIndex vs W3 reconcile)

Expose workflow run ID in CEL so resource keys can be run-scoped

Add `swamp doctor workflows` subcommand to surface workflow YAML parse errors during preflight

Add 'swamp issue comment' command for updating existing issues

Close #327 — fixed in 20260511.160514.0-sha.9d03b09a

Nested workflow task fails with 'Bad resource ID' when workflowIdOrName uses @collective/ prefix

Detect stale skill directories and prompt for repo upgrade

Improve skill trigger routing for cross-model edge cases

Add type search for driver, datastore, and report kinds

Surface ReconcileFromDisk dryRun transitions in swamp doctor extensions

Docs: update doctor extensions reference for W6 aggregate-state rendering + repair flags

swamp issue: check if reporter is on an outdated binary before opening

Implement W6: swamp doctor extensions aggregate-state rendering + repair surface (extension catalog rearchitecture)

extension pull fails referencing removed source after extension source rm

Investigate whether allExtensionMethodsAttached guard can be removed via registration-path consolidation

Trace context is lost: CLI ignores inbound TRACEPARENT and raw driver doesn't propagate active context into in-process methods

swamp model create --global-arg KEY=VALUE doesn't coerce strings to z.number() schemas

swamp model create --global-arg KEY=VALUE doesn't coerce strings to z.number() schemas

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

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