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

After removing a local extension source via swamp extension source rm <path>, subsequent swamp extension pull <ext> --force and swamp extension update <ext> invocations continue to fail with a rollback error that references the just-removed source path. swamp extension source list confirms zero sources are configured at the time of the failure. The pull eventually succeeds after several minutes / further commands, but the recovery path is unclear.

Steps to reproduce

Encountered while updating @hivemq/mudroom (registry 2026.05.11.52 → 2026.05.11.53) in a dedicated swamp repo at ~/.mudroom. The repo had previously had /Users/blake.irvin/hivemq/swamp-extensions/extensions/models/mudroom registered as a local extension source (added at some point by the mudroom bash wrapper as a fallback when the type wasn't found locally).

# Confirm source registered
SWAMP_REPO_DIR=~/.mudroom swamp extension source list
#  ✓ /Users/blake.irvin/hivemq/swamp-extensions/extensions/models/mudroom

# Remove the source
SWAMP_REPO_DIR=~/.mudroom swamp extension source rm /Users/blake.irvin/hivemq/swamp-extensions/extensions/models/mudroom
#  Removed extension source: ...
#  0 sources configured

# Confirm zero sources
SWAMP_REPO_DIR=~/.mudroom swamp extension source list
#  No extension sources configured.

# Pull still fails referencing the removed path
SWAMP_REPO_DIR=~/.mudroom swamp extension pull @hivemq/mudroom --force
#  FTL error Error: 'Type "@hivemq/mudroom" (kind=model) is already claimed by
#  @hivemq/[email protected] at ~/.mudroom/.swamp/pulled-extensions/@hivemq/mudroom/models/mudroom/mudroom.ts.
#  Cannot install @local/[email protected] at /Users/blake.irvin/hivemq/swamp-extensions/extensions/models/mudroom/mudroom.ts
#  — filesystem changes rolled back. Run `swamp extension rm @hivemq/mudroom` first if you intended to replace it.'

# swamp extension update produces the same error
SWAMP_REPO_DIR=~/.mudroom swamp extension update @hivemq/mudroom
#  WRN extension·update '@hivemq/mudroom: Update failed: ... same message ...'

The pull eventually succeeded after additional read-only commands (extension trust list, model type search, sqlite inspection of the catalog) and a retry. Whether the recovery was due to stale catalog state aging out, a lock timeout, or some other side effect is unclear.

Expected

After swamp extension source rm reports success and source list shows zero sources, swamp extension pull should not attempt to install from the removed path.

Observations

The rollback always wipes the freshly-pulled .53 files, leaving the repo with the prior .52 files (or, after enough rollback cycles, no files — see warning below).
After the rollback, every subsequent swamp command on this repo prints: WRN swamp·cli "2 pulled extension(s) have missing source files: @bixu/mudroom, @hivemq/mudroom. Run 'swamp extension install' to restore them."
The @local/[email protected] synthetic name (namespace = repo basename) suggests swamp is auto-discovering the dev path during install via something other than the source list.
Inspecting ~/.mudroom/.swamp/_extension_catalog.db after the source-rm shows no entries pointing at the removed path; bundle_meta source_dirs_fingerprint only references in-repo paths.

Environment

swamp: 20260509.235714.0-sha.7ace6b02
macOS: 26 (Tahoe), arm64
Affected repo: ~/.mudroom (dedicated mudroom repo created by the @hivemq/mudroom wrapper)
Cross-referenced extension: @hivemq/[email protected]

02Bog Flow

Closed

5/11/2026, 5:36:19 PM

No activity in this phase yet.

03Sludge Pulse

stack72 assigned stack725/11/2026, 5:26:41 PM

stack72 commented 5/11/2026, 5:36:08 PM

Thanks for the detailed report, @bixu — the steps to reproduce and observations were really helpful for tracing this.

This is the same root cause as swamp-club#310, which was fixed in PR #1356 (commit dc987cbf, merged May 10). Your build (20260509.235714.0-sha.7ace6b02) is from May 9 — two commits before that fix landed.

What was happening: Before the fix, swamp extension source rm removed the path from .swamp-sources.yaml but didn't purge the corresponding rows from _extension_catalog.db. Those stale rows were still materialized as @local/[email protected] during pull, colliding with the freshly-pulled @hivemq/[email protected] in the I-Repo-1 uniqueness check.

Why it eventually recovered: Some CLI commands (like model type search) trigger a reconcile on startup that re-scans disk against .swamp-sources.yaml. Since the source was already removed from the YAML, the reconcile cleaned up the orphaned rows — unblocking the retry.

Fix: source rm now purges catalog rows by source-path prefix immediately after removing the source from the config, so stale rows can't survive to conflict with a subsequent pull.

Running swamp update to pick up the latest build should resolve this. If you hit it again after updating, please reopen and we'll dig further.

bixu commented 5/12/2026, 11:07:07 AM

Nice, thanks!

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