Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

PR swamp-club/swamp#1552 adds release channel support (beta, rc, stable) to the extension system. The following manual pages need updates to document the new feature.

Pages to update

Reference: extensions.md (content/manual/reference/extensions.md)

Add a Release Channels section covering:

Three fixed channels: beta, rc, stable — with the promotion ladder diagram (beta to rc to stable, can skip rc)
Version uniqueness is global per extension regardless of channel — enables promotion as metadata-only operation
CalVer format is unchanged — channels are orthogonal metadata on versions

Reference: extensions/ subdirectory

If the extensions reference has sub-pages for individual commands, each of the following needs a --channel flag section:

push — --channel rc or --channel beta to push to a prerelease channel. Omitting means stable. Accepts a single value, validated to rc or beta.
pull — --channel rc or --channel beta to pull the latest prerelease version. Omitting means stable. Explicit version pinning (@name@version) ignores channel.
search — --channel rc --channel beta collect flag to filter results. Multiple values allowed. Omitting means stable-only results.
promote (new command) — swamp extension promote @name version --channel target. Target is rc or stable. Forward-only transitions enforced.
info — now shows per-channel latest versions (stable, rc, beta) when they exist. No flag needed.
version — shows per-channel latest and next bump when prerelease versions exist.

How-to: extensions.md (content/manual/how-to/extensions.md)

Add a how-to section for the CI/CD prerelease workflow:

Push a beta: swamp extension push manifest.yaml --channel beta
Pull beta in CI for integration testing: swamp extension pull @name --channel beta
Promote beta to rc after tests pass: swamp extension promote @name version --channel rc
Promote rc to stable after validation: swamp extension promote @name version --channel stable
Default consumers continue getting stable: swamp extension pull @name (no change)

How-to: extensions/ subdirectory

If the how-to has sub-pages, add a "Publishing pre-release versions" guide covering the full workflow above with concrete examples.

Key UX details to document

--channel is consistent across all commands — same flag name everywhere
On push/pull it takes a single value (rc or beta)
On search it is a collect flag (multiple allowed: --channel rc --channel beta)
On promote, --channel specifies the target (rc or stable) — this is the only command where stable is explicitly named
Stable is the implicit default everywhere — you never say --channel stable on push or pull
Auto-resolve only considers stable versions — prerelease versions never auto-install
Lockfile records the installed channel — update checks stay within the installed channel
Dependencies resolve from stable regardless of the parent extension's channel

02Bog Flow

Shipped

6/10/2026, 9:38:32 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack726/10/2026, 9:05:15 PM

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