Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

swamp extension push currently checks for a content-hash-bound adversarial review report under a system temp directory such as /tmp/swamp-extension-review/<extension>-<hash>.json.

That works for local publishing, but it is awkward to automate in GitHub Actions. A review completed on a developer machine does not survive into a clean CI runner, so CI publishing workflows emit adversarial-review warnings even when the code was reviewed elsewhere.

Evidence from GitHub Actions publish logs

In jentz/swamp-extensions, publishing runs from a clean workflow_run runner after CI succeeds. These publish runs all succeeded, but emitted the same adversarial-review warning:

Run 27119479865, extension @jentz/aws-context-guard, 2026-06-08: /tmp/swamp-extension-review/_jentz_aws-context-guard-92f4990bdd4a480508779a8ecf753d86cd43beaee1b2dafb1587896b42516d68.json
Run 27119507505, extension @jentz/aws-rds-reservations, 2026-06-08: /tmp/swamp-extension-review/_jentz_aws-rds-reservations-8156e657841bca740df52fd2fc18091209953805152db2030567e24681f08baa.json
Run 27104269237, extension @jentz/aws-rds-inventory, 2026-06-07: /tmp/swamp-extension-review/_jentz_aws-rds-inventory-e20d841ef880a275957476c61e8a86cd83f168d48f402825070af7d3b10e3f8d.json
Run 27104121041, extension @jentz/aws-s3-bucket-audit, 2026-06-07: /tmp/swamp-extension-review/_jentz_aws-s3-bucket-audit-b97f39ca9516d1f6f67013e6ae79b478803f01255180b23fa97af1faad30e753.json
Run 27103500808, extension @jentz/aws-rds-reservations, 2026-06-07: /tmp/swamp-extension-review/_jentz_aws-rds-reservations-e2dcd2fb308fc8bd0b702ea78b3fdb44a5ad4cdbfd37ba565d9682583f9c1612.json

The repeated warning text is:

["medium"] "Adversarial review" — "/tmp/swamp-extension-review/<extension>-<hash>.json": "No adversarial review recorded for the current code — perform the review and write the report here (run with --dry-run --json for the fill-in skeleton, or see the swamp skill)."

Current local dry-runs also emit reviewRuleWarnings with ruleId: adversarial-review-report, a temp-path file, and an inline skeleton.

Current CI shape

The publish workflow checks out github.event.workflow_run.head_sha, detects changed extension manifests, then runs:

swamp extension push "<extension>/manifest.yaml" --yes

Because the runner is clean, it does not have any local temp review report from prior human/agent review work.

Why current workarounds are awkward

A repo-local workaround might be possible:

In CI, run swamp extension push <manifest> --dry-run --json.
Extract the expected review report temp path / basename.
Copy or materialize a matching completed review JSON.
Re-run dry-run to verify the warning is gone.
Publish.

But this relies on scripting around an implementation detail: the temp path and content-hash filename. It also leaves extension authors without a documented durable place to store or verify review reports.

Requested improvement

Please provide a first-class CI-friendly way to satisfy the adversarial review gate.

Possible designs:

Add a repo-local review directory flag, for example:
```
swamp extension push manifest.yaml --review-dir .swamp-reviews
```
where review files are keyed by extension content hash.

Provide review lifecycle commands:

swamp extension review init manifest.yaml --output .swamp-reviews
swamp extension review check manifest.yaml --review-dir .swamp-reviews

Allow committed review artifacts using a documented stable naming convention.
Make --json easier for CI to consume by emitting one final structured object that includes:
- reviewRuleWarnings
- expected report paths / basenames
- skeleton content
- whether publish would require confirmation
Document the recommended GitHub Actions pattern if temp-path materialization is intended.

This is separate from Lab #583. #583 was about helper imports being shown as bogus model entries in push preview. This issue is specifically about adversarial-review report persistence and CI automation.

02Bog Flow

Shipped

6/8/2026, 8:04:50 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack726/8/2026, 6:41:20 PM

stack72 commented 6/8/2026, 8:04:59 PM

Thanks @jentz 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