Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

A swamp model method run (invoked as a workflow step) executing a long-running, high-fan-out extension method crashed with Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit after ~11.5 hours. Memory (RSS/V8 old-space) climbed steadily to the ~4GB V8 ceiling across ~3.7M HTTP calls (1.24M objects x HEAD+GET+PUT). Three swamp-core gaps compounded:

Heap ceiling is not configurable. The compiled binary runs with V8's default ~4GB old-space limit; scripts/compile.ts / deno.json pass no --max-old-space-size or --v8-flags, and there is no env passthrough. Long fan-out methods have a hard, untunable ceiling.
No streaming/batched fan-out primitive. A single method execution processing ~1.24M items must hold its working set for the method's entire lifetime; there is no checkpoint/stream/batch API to bound memory across a long run.
OOM leaves the run record wedged (no reaper). The datastore lock self-heals via heartbeat + TTL (verified reclaimed — swamp datastore lock status reports "no lock held" after the crash), but the workflow run record stays running permanently — there is no TTL/reaper on run status, so a crashed run is indistinguishable from a live one until manually corrected. (It does not block re-runs.)

Steps to reproduce

Author an extension method that fans out over ~1M+ items, making per-item HTTP requests.
Run it via swamp model method run / a workflow step against a real dataset.
Watch RSS climb steadily; after enough iterations the process aborts with the V8 mark-compact OOM.
Observe the run record remains in running afterward (no terminal status written).

Environment

swamp 20260527.193433.0-sha.ec40452d, macOS (darwin 25.5.0)
Workflow sync-events-archive-from-aws, method @swamp/digitalocean/space.sync_from_s3
~1,245,694 source objects; crash at ~4GB heap after 11h35m

Suggested fixes

Expose a heap-size flag / env passthrough (e.g. --max-old-space-size) for model method run.
Provide a streaming/batched fan-out helper so methods need not retain their full working set.
On method-process death, reap the run: mark it failed (TTL/heartbeat on run status, mirroring the lock's self-healing) so stale running records don't persist.

Notes

The triggering extension also contributed a per-iteration leak (undrained PUT response bodies across ~1.2M requests), which we are fixing separately. The swamp-core asks above are about making such a run survivable, tunable, and observable rather than a silent 11.5h march to a hard ceiling.

02Bog Flow

Open

6/12/2026, 9:23:46 AM

No activity in this phase yet.

03Sludge Pulse

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