Lab #4250: The inbox contract fixture and design doc match swamp-club#4241: the CLI inbox carries only messages Swamp Club writes

Summary

Match the swamp side to swamp-club#4241. That change narrows the CLI inbox to messages Swamp Club writes: announcements, direct, system and points messages, issue updates, issue shipped and closed, and the named onboarding kinds. Mentions and other web-only kinds no longer reach /api/inbox/*. This issue updates swamp's copy of the shared contract fixture and the design doc to say the same. The CLI needs no code change: the server decides which kinds it serves.

Merge this before swamp-club#4241. swamp-club's deno task check:inbox-fixture (from #4185) compares its fixture byte for byte with src/infrastructure/http/inbox_responses.fixture.json on swamp main. The #4241 branch has already removed the mention from its copy, so its check fails until this change is on swamp main.

1. The fixture

In src/infrastructure/http/inbox_responses.fixture.json, remove the mention entry (01JBX5Q8ZK0000000000000300) from webKindsPage.messages. Copy the #4241 branch's file (tests/fixtures/inbox_responses.fixture.json on swamp-club branch 4241) over swamp's, byte for byte, and confirm with cmp. webKindsPage keeps the issue_shipped and nurture_stalled entries.

2. Tests that read the mention from the fixture

Three tests currently take the mention from webKindsPage. Keep what they prove, because the CLI still has to handle hostile text and kinds that don't raise the notice. Move their data out of the fixture:

src/presentation/markdown_renderer_test.ts:157 finds the mention and checks that a bare http:// link renders as (link removed) and HTML stays literal. Keep the test, with its message defined inline in the test file.
src/infrastructure/http/inbox_schemas_test.ts:75-80 parses webKindsPage and checks the kinds. Update the expected kind list. Add an inline test that a mention, or any other unknown kind, still parses and keeps its kind as a string: the client stays tolerant even though the server no longer sends one.
src/libswamp/inbox/read_test.ts:70-75 builds pages from webKindsPage. The swamp-club#4109 cases ("the announced message is read before a newer message that doesn't raise the notice") still matter. nurture_stalled is served and never raises the notice, so use it in place of the mention, or define the newer message inline.

3. The design doc

In design/surfaces/inbox.md:

Line 37 (kind in the Message shape): replace "any kind the web inbox carries ("mention", …)" with the kinds Swamp Club serves to the CLI. It stays a string, so new kinds still parse.
Lines 47-50: /messages no longer carries every message the web inbox does. It carries only messages Swamp Club writes. Mentions and comments, whose bodies quote other users, stay on the web inbox and email, so no other user's text reaches the terminal or an agent. /summary still counts only the kinds that raise the notice; onboarding messages are listed but don't raise it.
Lines 328 and 337 (swamp inbox read): drop "such as mentions" and "mentions included". The messages listed but not announced are now onboarding messages.

Keep the wording neutral: say what the CLI inbox carries and that other users' text stays out of it.

Tests

cmp of swamp's fixture with the swamp-club #4241 branch's file shows no difference.
The moved tests pass with inline data, and the new unknown-kind parse test passes.
Run all of integration/ before verifying. The drift test on the notice text is unaffected.

Out of scope

Any CLI behaviour change
The swamp-club side (#4241)

Scheduled flaky-test detection is failing

artifacts.swamp-club.com unreachable in Spain during LaLiga matches (ISP blocking of Cloudflare IPs)

Failed remote methods lose named command-result output handles at Serve

Whole run-index rewrites block serve dispatch as retained inputs grow

Worker control WebSocket reports Frame too large and aborts small native dispatches

Supported binary file ingestion for remote members of swamp serve, without the bytes landing in run history

Worker queryData fails at the fixed 30 s RPC limit while it waits for a full catalog rebuild

vault put --server: accept the value on stdin (keep secrets out of argv)

swamp serve exhausts its heap when a workflow's run history carries large inputs: every run save parses and rewrites the whole .runs-index.json

Hot reload can keep an old local behavior registry and memoized bundle after external catalog indexing (1602; e459 regression passes)

Add expiring service-account token requests and authorization checks to RBAC

Reads other than findById still treat a lapsed temporary ban as active until the operative next signs in

verify-build upgrade gate silently skips models whose version is a constant

@swamp/agent-sessions: explore a decision model (TypeSafe Jev) for call labelling

agent-sessions: follow-ups from the 4211 reviews (repo resolution cache and edge cases)

agent-sessions: revisit the import's remaining review findings (redaction edge cases, import robustness)

Docs: document the datastore durable setting and its macOS ordering in the manual

Docs: working offline against swamp serve (leases, outbox, flush, quarantine) for swamp-club#4195

Swamp Club collective GUI: show the swamp serve instances currently connected to a collective

Docs: swamp data query --sort, --cursor and nextCursor in the data reference

A malformed --ca-cert file is reported as an unreadable OS certificate store

TLS hint blames a missing root CA and macOS for every invalid peer certificate failure

workflow cancel --server does not send SWAMP_SERVE_EXTRA_HEADERS

S3/GCS repairUnpushedFiles: the pull it asks for after a lost last-synced index does not stop it re-uploading copies a peer deleted

swamp-uat private-registry tests leave npm/<port> dirs in the shared Deno cache

Read-model catch-up of many data versions slows sharply under load

A resume runs settled work after the teardown gated on it has already run, and nothing tears that work down

A step settled after the abort overwrites the expression-context entry of a same-named step that ran in another job

The extractContentMetadata property test generates invalid source and fails at random

A limited model.output.search copies and sorts the whole listing on the event loop for each request, so that step still scales with the window

A lone step in a job still starts under the aborted signal when another job has suspended the run

CLI command to change an existing extension's visibility (private → public)

Docs: team-mode model leases (swamp behavior lease, lease status in datastore lock status)

serve (token mode): --admins accepts idp-group entries that can never match

build-swamp-extension example: code-review isn't given the quality evidence, so the reviewer reports quality as missing

Filesystem control-plane put races empty-parent cleanup (cron pending-run ENOENT)

deployment: getLogs method (deployment-aware pod log tailing)

Agent sessions extension: import Codex sessions

model.output.search response phase takes 3.9s for 5,000 items with no attribution (redaction vs serialization vs send)

Docs: v3 serve team mode, followers forward writes and the advertise-address and ca-cert serve flags (swamp-club#4120)

Skill/docs: document registry listing limits, static-extraction rules, and splitting large APIs by domain

Check registry listing limits in extension quality/push and suggest splitting into per-domain extensions

Over-limit contentMetadata publishes a blank extension page; archive fallback extracts nothing

swamp inbox: with a filter active, sitting on the last row pages through the whole inbox in the background

@swamp/video/brand: follow-ups from the initial review (render hang, odd sizes, Chromium errors)

@swamp/video: follow-ups from the initial review (card length, input validation, OCR frames on disk)

@swamp/video/hyprland: recording hotkeys, retake marker and phone-mirror window rules

@swamp/video/obs: optional OBS recording with per-person hardware config for @swamp/video

serve daemon enable: add Windows support (service or startup task)

swamp skill docs: publishing.md contradicts itself on dynamic imports, overstates where git dependencies are listed, and never says consumers keep the publisher's bundle

Relationships

#4250 The inbox contract fixture and design doc match swamp-club#4241: the CLI inbox carries only messages Swamp Club writes