Resource-leak test failures on main: extension_rubric_scorer_test and worker_gateway_test

The recommended .gitignore in the repo structure skill (references/repo/references/structure.md) covers .swamp/ secrets and .claude/, but not .swamp.yaml or CLAUDE.md. Extension authors following the skill docs will accidentally commit both files.

.swamp.yaml contains a machine-specific absolute path (written by swamp repo init) and behaves like a .git directory marker — it should be regenerated on each clone, not checked in. CLAUDE.md is agent instructions generated for the local developer environment, also not meaningful to share.

The swamp-extensions reference repo excludes both in practice, but this convention is nowhere in the published skill docs. Discovered while publishing a first extension (@josephholsten/freebsd/appjail) and comparing the resulting .gitignore against what swamp-extensions does.

Proposed Solution

Update the recommended .gitignore in references/repo/references/structure.md to:

# Swamp managed defaults
.swamp/
.swamp.yaml
.swamp-sources.yaml
CLAUDE.md
.claude/

And add a rationale row to the "Files to Never Commit" table:

Path	Reason
`.swamp.yaml`	Machine-specific absolute path; regenerated by `swamp repo init`
`CLAUDE.md`	Agent instructions for local dev environment; not shareable

The same note would be useful in the extension publishing pre-push checklist in references/extension-publish/references/publishing.md.

Alternatives

Leave it undocumented and rely on authors discovering it by reading swamp-extensions. This is how the current situation arose.

02Bog Flow

Open

6/12/2026, 5:02:49 PM

No activity in this phase yet.

03Sludge Pulse

josephholsten commented 6/12/2026, 5:17:29 PM

Additional scope: the SWAMP_EXTENSION_REVIEW_DIR override and its effect on .gitignore guidance.

The adversarial review docs note that SWAMP_EXTENSION_REVIEW_DIR can be set to store review reports inside the repo (for CI, so reports survive across runners). When set, review files land at e.g. .swamp-review/swamp-extension-review/<hash>.json inside the working tree.

This creates a second gitignore decision that the docs don't address:

If SWAMP_EXTENSION_REVIEW_DIR is set intentionally for CI, the review directory should be committed — that's the whole point.
If it's set by accident or the author switches back to the temp-dir default, .swamp-review/ becomes untracked noise that should be gitignored.

Found this in a sibling extension repo (swamp-zfs) where .swamp-review/ exists on disk, is untracked, and the .gitignore has no entry for it — a half-state with no guidance on which way to go.

Suggested addition to the gitignore guidance: a note explaining the two cases and a recommended default (gitignore .swamp-review/ unless you're explicitly using SWAMP_EXTENSION_REVIEW_DIR for CI, in which case commit it).

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