extension push: adversarial-review report hash is platform-dependent (macOS vs Linux), so committed reviews never match a cross-OS runner

Design proposal (no implementation yet) for extending swamp serve beyond its single-host trust model into a network-exposable server with a coherent authentication and authorization posture. Written up as design/serve-auth.md, building on the existing orchestrator/worker remote-execution machinery.

Branch / PR

Draft PR: https://github.com/swamp-club/swamp/pull/1587 (marked draft + hold label)
Branch: design-serve-auth
Doc: design/serve-auth.md

What it proposes

TLS — static certs and Let's Encrypt ACME (HTTP-01). Binding off-loopback without TLS is a hard startup refusal.
Authentication — swamp serve as a generic OAuth 2.0 client; swamp-club.com as the default provider (better-auth's OAuth module + device authorization grant). Identity is established via a userinfo exchange rather than offline ID-token validation, sidestepping the JWT-validation footgun class; the one correctness item is verifying the token was issued for swamp's own client. SAML is brokered, never in-codebase. The server mints its own revocable tokens; the provider is consulted only at login.
Admission policy — restrict login to particular collectives and/or whitelisted users (matched on stable subject).
Mandatory configured admin — any enforcing mode requires at least one configured admin principal (granted admin on access:*), materialized at boot from config as the fail-safe root of who may change the rules. Off-loopback with auth disabled is also a hard refusal.
Authorization — a new domain/access/ bounded context: grants and groups persisted as built-in models, deny-by-default with deny-wins precedence, IdP-asserted groups as first-class grant subjects.
CEL grant conditions — uniform with swamp's existing CEL surfaces, evaluated in a permanently sealed, deterministically cost-bounded environment.
Rule packs — a tier-1 policy extension point shipping grants-as-data; context enrichers and external deciders scoped as later/non-goals.

Open questions

Whether swamp-club will expose a public OAuth 2.0 authorization server with the device grant + collectives on userinfo (lynchpin; lives in the swamp-club repo).
Default server-token lifetime vs. revocation latency for IdP-group membership.
Break-glass locally-minted tokens under OAuth mode.
Which deterministic predicate libraries the sealed CEL baseline launches with.

Feedback on the design doc is welcome on the PR.

02Bog Flow

Open

6/16/2026, 6:46:41 PM

No activity in this phase yet.

03Sludge Pulse

Support epoch seconds as the version suffix to avoid push collisions

Implement ephemeral data as in-memory repository

Design: serve authentication & authorization (TLS, OAuth, access control)

Private collectives

extension push: adversarial-review report hash is platform-dependent (macOS vs Linux), so committed reviews never match a cross-OS runner

Can't click on repository from swamp extension search.

extension pull: detect ghost-row conflicts and suggest swamp doctor extensions

`extension quality` false-positive bare-import detection on string literal "flexible"

Remote Execution tutorial

SQLite run tracker subsystem for in-flight run lifecycle

Honour AWS profile default region when 'region' globalArg is omitted

swamp serve does not open the UI

Docs: document --compact flag for model type describe

datastore setup migration relocates and deletes repo-root .swamp/secrets, breaking all local_encryption vault.get

Registry content-type search filter can match versions absent from the displayed extension

Docs: document reports.require failure semantics in the manual (unresolvable required report fails the run)

Reports tab on extension page is non-functional

vault read-secret mixes log output into stdout

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