Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

Whole-extension yank (swamp extension yank @col/ext --reason ..., no version) sets extension-level yankedAt and removes the extension from search on every channel at once — including beta and rc. So yanking because of a bad stable release also makes the extension vanish for beta/rc testers. There is no way to say "withdraw from stable but keep beta available."
Version yank (yank @col/ext <version>) is the only surgical option, but it targets a single version, not a channel. Yanking the latest stable version usefully rolls the stable pointer back to the previous non-yanked stable version (good — see #624), but a maintainer who wants to pull an extension off stable entirely while keeping a beta track alive has to yank every stable version one by one, and even then the whole-extension yank is the only "remove from discovery" lever and it hits all channels.

yank has no --channel option:

yank: Yank an extension or specific version from the registry.
  <extension> [version]
  --reason   (required)
  -y, --yes

Proposed solution

Add --channel <stable|rc|beta> to swamp extension yank / unyank:

swamp extension yank @col/ext --channel stable --reason ... — withdraw the extension's presence from the stable channel only, leaving beta/rc discoverable and pullable.
Without --channel, preserve today's behavior (or require the flag to avoid surprising all-channel yanks).

This pairs with the demote/withdraw request in #624: channel-scoped yank is the concrete mechanism for "take it off stable, keep it on beta."

Repro

Publish a stable version and a separate --channel beta version of the same extension.
swamp extension yank @col/ext --reason test (whole extension).
swamp extension search <name> --channel beta → the extension is gone from beta too, not just stable.
swamp extension unyank @col/ext restores all channels; there is no way to have scoped the yank to stable only.

#624 (demote / withdraw a version from the stable channel) — same underlying gap, complementary mechanism.

02Bog Flow

Shipped

6/11/2026, 6:52:56 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack726/11/2026, 3:33:22 PM

magistr commented 6/11/2026, 1:14:08 PM

Additional finding: whole-extension yank also blocks republishing (HTTP 410)

Tested the obvious recovery path — yank the whole extension, then push a fresh version to a different channel (beta) instead of unyanking. The registry refuses it:

$ swamp extension yank @col/ext --reason ... -y        # whole-extension yank
$ swamp extension push @col/ext/manifest.yaml --channel beta --yes
Extension API error (HTTP 410): Extension has been yanked

The local --dry-run builds the archive fine; only the real upload is rejected.

Impact: a whole-extension yank is a hard wall. It (1) hides the extension on every channel, and (2) blocks any new publish — even to a channel that wasn't the reason for the yank. There is no "yank off stable, keep a fresh beta alive" path: the only way to publish again is unyank, which restores all channels at once. This is the same channel-blindness as the original report, on the publish side.

Reinforces the ask: yank/unyank (and the republish gate) should be channel-aware, so a maintainer can withdraw one channel while continuing to ship on another.

stack72 commented 6/11/2026, 6:53:05 PM

Thanks @magistr for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

Landing page clips the curl install command instead of rendering the full text

model delete --json output shape doesn't match the documented {deleted, modelId, modelName, artifactsDeleted}

model search --json returns a bare model object instead of {query, results} when exactly one model matches

Extension author gitignore guidance: add .swamp.yaml and CLAUDE.md to recommended excludes

reports.require in workflow YAML does not auto-execute pulled extension reports

Yanked extension version still shown as active on swamp-club.com and in 'extension search'

Add deprecate/yank/unyank actions for own extensions on the web interface

Expose per-run memory/CPU metrics for method & workflow executions

model method run OOMs at 4GB V8 heap on long high-fan-out methods; non-configurable heap + crash leaves run stuck in "running"

Tier-up announcements never fire for direct score contributions (badge awards, feed credits)

CI never runs the discord-bot service test suite

Discord role sync never assigns lower leaderboard tiers (Swamp Baby / Muck Runt / Sludge Whelp)

Docs: document globalArgument input reference validation in workflow validate

Remote execution: UAT coverage for tokens, enrollment, and dispatch

Remote execution: comprehensive reference documentation

doctor extensions: pulled-extension source files reported as orphans that --repair can't evict (nested @swamp/aws/* sibling mis-attribution)

Channel-based publishing for local extension backports

Feature: make extension yank channel-scoped (--channel) so it doesn't nuke every channel

swamp update --setup-auto does not work with bluefin44 (crontab not found, should

Feature: demote / withdraw an extension version from the stable channel

Docs: extension-publish skill guide doesn't cover release channels

workflow validate: resolve model globalArguments expressions against the calling workflow's declared inputs

Add a way to list registered report definitions (report search only lists results)

Inconsistent resource-field accessor: data get returns content, data query and CEL use attributes

Extension API: allow export const extension to add resource specs, or document that it cannot

@swamp/aws/cloudformation: expose StackSet instances, drift, and operations (Cloud Control cannot)

workflow validate: method args with a Zod .default() are treated as required

Profile months overlap in trajectory

model type describe --json: bloated output (40% duplicated specs, no compact mode) and lost method-to-output mapping drive agents to read extension source

UAT: Release channel CLI and adversarial tests

Docs: Add release channel documentation to the manual

Test skill evals with Fable in multi-skill eval tests

Guide users toward filing feature requests when @swamp extensions lack a needed capability

Guide users toward filing feature requests when @swamp extensions are missing features

correcting capitlization of Swamp, Swamp Club, and The Swamp on the swamp-club.com website

API: Add release channel support for extension versions (beta, rc, stable)

Add @swamp/hetzner-cloud/server-types model for availability and project limits

Resident/warm worker mode — `model method run` has ~6s fixed per-invocation overhead that rules out latency-sensitive use

Issue submission returns wrong URL path

Dynamic resource attribute refresh for model instances

`vault put` inside workflow steps still acquires global `.datastore.lock` after #382

extension quality scorer mis-detects quoted phrases in comments as bare imports

extension push: credentials-sensitive-field false positive when .meta({ sensitive: true }) is on a continuation line

Local source-loading should discover a report co-located with its model in a paths.base:manifest extension

extension push: optionally sync the published bundle to the manifest `repository:` (git mirror)

Add 'creek' extension kind for cross-querying external systems alongside swamp data

Docs: vault refresh hooks (--refresh-from, --refresh-ttl, --clear-refresh)

Support CI-friendly adversarial review artifacts for extension push

Deprecate "No slow types" (fast-check) rubric factor on server-side scorer

Registry scorer fails on bare specifiers — mirror CLI fix from #505

Official extension for GitHub repository configuration (environments, variables, secrets)

Feature request: @swamp/tailscale extension

Option to change email in your Swamp Club profile or delete account

Docs: vault reference in manual promotes inline KEY=VALUE as primary example

extension push error for disallowed file types doesn't mention binaries field

swamp help extension omits yank and unyank (machine-readable CLI schema misses real subcommands)

Extension model method execute lacks typed args/context — every author has to use ': any' to unblock tests

@webframp/hashicorp-vault: empty KV engine causes 'data.data.keys is not iterable' on vault put

workflow resume fails to register all extension model types (local and pulled) — "Unknown model type"

model method run: cannot pass arrays, numbers, or booleans via --input

extension push --dry-run --json reports local helper imports as bogus model entries

Extension source: direct-content export scan only reads first 64 KiB, silently drops exports beyond it

Homepage install command: wrong domain and missing https:// protocol

Homepage install command: wrong domain and missing https:// protocol

first-class refresh hook for short-lived vault values (gcloud / aws-sso / kubectl-oidc token UX)

swamp issue ripple logged "Posted ripple on issue #514" but the ripple is not visible on the Lab

vault guide promotes inline secret values (KEY=VALUE) as a primary "swamp vault put" example

swamp-getting-started SKILL.md still references removed swamp-model / swamp-workflow / swamp-vault / swamp-extension / swamp-repo skills

extension rm blocked by stale /workspace bundle_types rows from prior container sessions with host repo bind-mounted

extension search returns null repository fields that extension info populates

Quality rubric: scope "No slow types" for model extensions (consumed via model+CEL, not type imports)

data get/list --workflow and workflow history get/logs cannot resolve extension-delivered workflows (Workflow not found)

Docs: add doctor secrets and doctor vaults to the troubleshooting how-to guide

UAT: sensitive resource output without vault produces clear pre-flight error

Docs: add doctor vaults subcommand and pre-flight vault validation

gcs-datastore: registerNamespace does not detect conflicts with existing registrations

Validate vault availability when model has sensitive output fields

Managed skills ship with dangling reference-doc links

swamp-club: update skill references and CLAUDE.md after superskill consolidation