Add two new documentation pages covering the OAuth authentication flow for swamp serve. These extend the existing user guide from #679 with the OAuth mode added in #1015 (swamp-club) and #1016 (swamp).

Pages to create

How-to: Set up OAuth authentication

Location: `content/manual/how-to/swamp-serve/set-up-oauth-auth.md`

Covers:

Starting swamp serve with OAuth mode: ```bash swamp serve --auth-mode oauth --admins swampadmin --allowed-collectives acme-corp ```
First-time bootstrap flow: server displays a verification code, admin approves in browser, client registered automatically, credentials stored in vault. Subsequent starts skip this.
User login: ```bash swamp auth server-login --server wss://swamp-serve.example.com ``` User visits the verification URL, signs into swamp-club, enters code, approves. Token stored automatically.
Collective-based admission: only users in `--allowed-collectives` can connect. Users not in the allowed collectives are rejected with a clear message.
`--allowed-collectives` vs `--allowed-users`: at least one is required for OAuth mode. `--allowed-collectives` checks swamp-club collective membership. `--allowed-users` allows specific user subs.
Admin resolution: `--admins` accepts swamp-club usernames (not raw IDs). Resolved automatically at startup via swamp-club.
Subsequent starts: credentials loaded from vault, admin resolution uses cached mappings, no browser interaction needed.
HTTPS requirement: `--oauth-provider` must be HTTPS except for localhost development.
Comparison with mode: token: token mode is for air-gapped environments or teams without swamp-club. OAuth mode is for teams using swamp-club as their identity provider.

Explanation: OAuth and collective-based admission

Location: `content/manual/explanation/swamp-serve.md` (add a new section to the existing explanation page)

Covers:

Why OAuth: replaces manual token minting with self-service login. Users authenticate themselves through swamp-club. No tokens to distribute.
The device grant flow (RFC 8628): why device grant (CLI + browser on different machines), how it works (code displayed in terminal, user approves in browser, CLI polls until approved), why it's the standard for CLI tools (GitHub CLI, Claude Code use the same pattern).
The bootstrap client: a well-known public client ID baked into the binary. Same pattern as GitHub CLI. Security is in the browser approval step, not client ID secrecy.
Collective-based admission: collectives in swamp-club are the admission boundary. The admin says "members of acme-corp can connect" and swamp-club membership controls who gets in. No user management in swamp serve.
Collectives on the token: collective memberships snapshotted at login time on the server token. Used for `idp-group:` grant matching. Stale until re-login (token expiry forces re-authentication).
Two authentication targets: `swamp auth login` authenticates to swamp-club (platform). `swamp auth server-login --server` authenticates to a specific swamp serve instance (team's server). They're different trust relationships.
Flow diagram: the complete device grant flow from CLI → swamp serve → swamp-club → browser → approval → token

Cross-links

From `set-up-token-auth.md` — link to OAuth as the alternative for teams using swamp-club
From `swamp-serve.md` parent how-to — add OAuth auth to the "In This Section" list
From `serve-flags.md` reference — add `--oauth-provider`, `--allowed-collectives`, `--allowed-users` flags

Scope

Documentation only — no code changes. Both pages should be written after #1015 and #1016 ship.

02Bog Flow

Shipped

7/8/2026, 12:33:20 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/7/2026, 11:54:16 PM

Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

gcp/sheets spreadsheets-values: batch_get crashes with "Request with GET/HEAD method cannot have body"

Token creation API and UI scope selector for collective tokens (phase 4 of #960)

Make Cloudflare CRUD methods factory-aware so list-discovered resources can be managed in-place

[sc] quest-grant Mongo ops (recentHeartbeat/signalCounts/countIssueShipped) regressed to ~5s timeouts — missing index

Add @swamp/kubernetes/statefulset model type

serve: workflow.approvals and workflow.run.search still full-scan the workflow-run store after the #1284 data.query pushdown

Sync guard skips bound namespace directory during push — 0 files pushed after namespace migrate

Flaky #1052 preparePush test: mtime-granularity race on Linux tmpfs

command/shell renders JSON-object stdout lines as the literal string 'undefined'

Issue redactor treats the MongoDB authSource parameter as a secret, corrupting reproduction steps

namespace unset --migrate silently deletes artifact history via catalog-rebuild GC (~484k files lost)

Docs: document repo root resolution from subdirectories

Expose the swamp.club feed as an RSS feed

Email invitation is not linked to account created from invite URL

Add serve, datastore, vault, and worker wildcard scopes to token registry (phase 4 prep, #960)

datastore setup extension drops 'namespace' from --config, making extensions that require it impossible to configure

Docs: update manual to document --yes/-y as the standard confirmation-skip flag

Docs: update data.query and CEL expressions references for SQL pushdown

Docs: document collective token CLI usage in API key authentication pages

Add a --release-notes option to `swamp update` (or even make it the default)

Docs: manual should state workflow unknown keys are rejected and placement is step-only (follow-up to #1240)

Make GCP CRUD methods factory-aware so list-discovered resources can be managed in-place

serve: read ops (data.query, workflow.approvals, workflow run.search) linearly scan the whole datastore — ~350–600ms floor regardless of match count

Running "swamp workflow run ..." in a subdir of the swamp repo fails

Guide agents to inspect reports after failed model and workflow runs

serve: main JS thread holds ~40–70% of a core while idle (no clients, no runs, --no-schedule)

Search box collapses to near-zero width on mobile on the Extensions page

Extensions page: Search bar missing on mobile

spreadsheets-values: every method fails with 'Missing required path parameter: spreadsheetId' — implementation reads a global argument the schema does not declare

namespace migrate/set workflow broken for extension datastores: migrate skipped by sync guard, set not idempotent, migrate-index empties shards

ExtensionInfo.latestVersion typed 'string' but registry returns null; harden pull/resolve for prerelease-only extensions

workflow.run: relay a custom model method's output as method_output (command steps already do)

promptChoice infinite-loops on non-interactive stdin

gcp _lib: unconditional x-goog-user-project header causes USER_PROJECT_DENIED (403) for service accounts without the serviceUsageConsumer role

extension push: issue-verdict review is indistinguishable from missing/stale

swamp extension version crashes with 'Invalid CalVer version: "null"' when only a prerelease (beta/rc) version is published

Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

`datastore setup filesystem` never transfers content when leaving a sync-based (remote) datastore — copies only the catalog and hardcodes `filesPulled: 0`

Scaleway models: create methods should not require the resource ID they generate (ipId/gatewayId/serverId/...)

gcp/calendar events.list reads wrong array field ('defaultReminders' not 'items') → always returns 0 events

provisioner.provision fails with 'Cannot read properties of undefined (reading trim)' at method_execution_service.ts:852

method_execution_service.ts:852 crashes on undefined.trim() when writeResource receives undefined instance name

CLI support for collective API tokens (phase 3 of #960)

@swamp/gcp/calendar: service-account & ADC auth mint cloud-platform-scoped tokens → 403 on Calendar API

Scope enforcement and whoami introspection for collective tokens (phase 2 of #960)

fix(software-factory): DeclaredSchemaSchema.enum rejects boolean literals

Surface cloud-provider labels (scaleway, digitalocean, oracle/oci) as first-class search/filter facets on the Extensions page

Profile link in genesis subdirectory does not navigate back to main profile

Profile stats: per-user daily rollup table + MV in ClickHouse

Reconcile collective-token CLI activity to members (attribute → bonus → stamp → even-split)

Telemetry stats consumer: unsanitized subcommand in Mongo update path drops user metrics silently

Telemetry stats consumer: insert_id dedup commits before the write it guards — any upsert failure is silently swallowed on retry

Job-level labels: block is silently ignored, not rejected

Issue submission redactor silently corrupts report bodies

CLI telemetry: fold third-level verbs into subcommand + canonicalize aliases

Docs: update extension info reference to document extensions (type grafts) in content metadata

Docs: swamp skill repo-structure reference still documents repo-local .swamp/telemetry/ as live

Add safe adoption and lifecycle methods for existing Hetzner resources

Docs: update manual telemetry reference for user-global spool and telemetry.yaml opt-out

export const extension can graft methods onto foreign-collective types, undisclosed in extension info / contentMetadata

Add lookup support to the Cloudflare DNS records model

Expand token scope registry to full taxonomy (phase 1 addendum, #960)

Docs: document user-global telemetry (telemetry.yaml opt-out, spool location, telemetry stats behavior)

score_daily rollup strands stale grains when a day-less grant re-stamps onto a later day

swamp-club: global rate limiter runs pre-auth and collapses all direct clients into one per-IP bucket — 429s authenticated CLI traffic

Collective API token scopes: domain, persistence, and auth threading (phase 1 of #960)

Telemetry migration from ~/.swamp/telemetry should auto-detect home-as-repo

feed_post_score_events queue grows unboundedly (no TTL, no delete-on-delivery)

Issue-filing skill should require ownership classification before submitting a bug

Interactive finder silently drops the preview pane on narrower terminals, and layout selection is unstable

@-mention autocomplete for users when writing lab ripples

Remove comments from /feed and redesign the page

Interactive finder preview corrupts: overlapping/stale lines when preview content overflows the pane

Score-refresh consumer: harden coalescing against a diverse backlog (bistability)

Remove feed comments — consolidate discussion in Discord

Add a 'my collective extensions' filter to extensions page

Relax the profanity filter

Extension search returns edit-distance noise for short queries ("asdl" → "AWS DEADLINE")

Telemetry recoverOrphaned startup race with multiple replicas (created_at-based)

Grant revoke is never applied to the running server — under `--grant-reload auto` and `manual` alike, a revoked grant stays in force until an explicit `access reload`