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

After PR systeminit/swamp#1288 (fix for swamp-club#212), swamp now self-heals when a cached bundle file under .swamp/bundles/<hash>/<name>.js is deleted while the catalog row in .swamp/_extension_catalog.db still references it. The fix is verified by unit and integration tests inside the swamp repo, but there is no end-to-end coverage in systeminit/swamp-uat exercising the recovery from a real CLI invocation.

The natural home for this test is systeminit/swamp-uat/tests/cli/adversarial/state_corruption_test.ts — that file already covers other "broken on-disk state" scenarios (datastore lock state, partial writes, etc.), and a missing-bundle row is exactly that genre.

Proposed solution

Add an adversarial UAT test that:

Initializes a swamp repo and writes a small user model under extensions/models/<x>.ts.
Runs swamp model type describe @user/<x> to populate the catalog and write the bundle.
Asserts the bundle file exists at the expected .swamp/bundles/<hash>/<x>.js path.
rms the bundle file with the catalog DB intact.
Runs the same swamp model type describe again.
Asserts:
- Exit code 0 (was previously non-zero with NotFound: No such file or directory).
- Stderr contains the recovery warn line (Rebundling "<x>.ts": cached bundle missing from disk) emitted by bundle_freshness.
- The bundle file is back on disk.
- The describe output still surfaces the type/version/methods correctly.

Optionally pair with a sibling-loader variant once swamp-club#214 lands (the import-site fallback for datastore/driver/vault/report).

Alternatives

Leave coverage at the unit/integration layer in the swamp repo. Rejected: this is exactly the kind of "filesystem state that diverges from catalog state" scenario the adversarial suite exists to catch end-to-end. The unit tests inside swamp can't verify the full CLI path including the warn log routing or the user-visible exit behavior.
File against a different test file. Rejected: state_corruption_test.ts is the right home — closer to the existing concurrency/state-corruption neighbors than to the per-command CLI tests.

Context

Fixes in swamp-club#212 / systeminit/swamp PR #1288.
Related: future swamp-club#214 (sibling-loader port).
Convention reference: systeminit/swamp/agent-constraints/planning-conventions.md §UAT — assesses each fix for end-to-end coverage gaps and recommends filing in swamp-uat.

02Bog Flow

Closed

5/6/2026, 10:37:53 PM

No activity in this phase yet.

03Sludge Pulse

stack72 commented 5/6/2026, 10:38:04 PM

Handled as part of the refactor of extensions

stack72 commented 5/7/2026, 10:31:17 PM

Closing — moved to swamp-uat as the test target.

The UAT scenario this issue requested ("missing cached bundle with intact catalog should self-recover across all 5 extension kinds") now lives at systeminit/swamp-uat#200.

W4 (swamp-club#269 — KindAdapter + unified loader) will verify against the swamp-uat scenario as part of its soak gates. Pre-W4, the scenario passes for model only (per PR #1288 / swamp-club#212). Post-W4, it must pass for all 5 kinds (model, vault, driver, datastore, report) — that's the structural fix W4's unified importBundleByPath ENOENT fallback provides.

Pattern going forward: Lab issues that request UAT tests get moved to swamp-uat (where the tests live) and closed here. The Lab tracks swamp itself; swamp-uat tracks user-journey verification.

Thanks for surfacing this — it's the test that closes the structural-fix verification loop for the rebundle-loop bug class.

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