Lab #3110: Show signal waits to remote clients and the dashboard

Problem

Split out of swamp-club#3094. A remote client and the dashboard are not told about signal waits:

The signal_wait_requested event is kept off the wire for older clients (LOCAL_ONLY_EVENT_KINDS in src/serve/serializer.ts); a run's own wait reaches the client in the suspended event's wait field. A parent suspended on a child that waits for a signal gets no wait ID in JSON output, and the log hint can only say to approve its gate or signal its wait.
The printed signal and resume commands are the local forms, which cannot reach a run on a server.
The dashboard lists suspended runs as awaiting approval or awaiting resume. A run suspended only on a signal wait is in neither list.
A signal does not show in the run record until the run is resumed, so workflow history and the dashboard cannot tell a signalled wait from an open one.

Proposal

Carry a nested run's open wait to remote clients, so a parent suspended on a child names the wait ID in log and JSON output. Older clients must keep working: new information goes in fields they ignore, never in an event kind they do not know.
When a run is remote, the printed signal command points at the server form added by swamp-club#3094.
The dashboard shows runs suspended on a signal wait, with the wait ID, deadline and schema, and shows receipts.
A wait ID is named only to a caller who may read the workflow it belongs to, as nested runs are redacted today.

Acceptance criteria

A remote workflow run that suspends on a wait, its own or a nested run's, prints the wait ID and a signal command that works from the client.
A client released before this change still parses every event it is sent.
The dashboard lists a run suspended only on a signal wait, and tells a signalled wait from an open one.

Tests

Serializer tests that an older client still parses every event it is sent.
Redaction tests for a nested wait of a workflow the caller cannot read.
CLI journeys in swamp-uat.

Depends on

swamp-club#3094 (the server form of workflow signal and the waits listing). Independent of swamp-club#3108 and swamp-club#3109.

Out of scope

Forms generated from the payload schema.

References

swamp-club#3094, swamp-club#3093, the Limits of this version list in design/primitives/workflows.md.

Session-start 'swamp model search --json' in the AGENTS.md template is unfulfillable - wire it to a hook or drop it

Flaky property test: analyzeExpression dot/bracket agreement fails when the generated model name is a CEL keyword

Accept usernames for user subjects in grant files

Docs: enable-managed-config should say to re-run config migrate when its push fails

Docs: grant file reference shows a stale format and omits resources and subjects

Flaky property test: analyzeExpression hyphenated dot access fails when modelName generates a CEL keyword ("in")

extension quality and push crash with IsADirectory when additionalFiles lists a directory

extension push: a required global argument renders with a stray "" ("text": "string""")

Docs: extension publishing reference is stale on bare specifiers, quality output and fmt config (swamp-club#3022)

swamp-extensions: replace bare import specifiers with npm:/jsr: specifiers in first-party extensions

extension push: 'Requested visibility' line prints to stdout without the logger prefix, twice per run

A nested structural swamp that outlives the run that started it keeps skipping that run's lock while the holder writes

Show signal waits to remote clients and the dashboard

Settle expired signal waits from swamp serve

Resume signalled workflow runs automatically under swamp serve

extension push/quality: structured acceptances for agents, a clearer title than For next time, and an optional reason

extension push: the undecided private-entitlement verdict still says the registry may start a trial at publish

seed:collective cannot produce a superseded personal trial or a returned trial, so the UAT cannot cover them

Replayable state fragments: Git-reviewable desired state for resources changed by model methods

extension push: registry metadata and content hash label files relative to the repo dir, so a push with --extensions-dir records ../ paths

registry: store and show declared acceptances sent in contentMetadata.acceptances at confirm (swamp-club#3021)

extension push --dry-run: authentication verdict prints 'Signed in as .' when the credential is an API key with no username

serve --remote-only: step output from workers is never persisted to the run log (history logs always empty)

serve HA: worker enrollment on a replica that lacks the enrollment token's definition may create a second definition (unverified)

serve HA: pull a token's definition on an auth miss so a peer accepts a new token at once

extension push: version-drift check reports 'no previously published version found' when the registry call failed

Search and list output follows directory iteration order in the definition, workflow, vault and output repositories

extension push: accept attestation-backed adversarial-review evidence (lookup by extension and content hash), generated provenance, and carry the evidence to the registry at confirm (design: Lab #3023)

Workflow load errors print the raw Zod issue dump instead of a readable message

Decide a stricter naming rule for workflow step and job names

serve: run scheduled workflows concurrently (per-workflow serialization), and report queue delay

Show expired approval gates as expired, with a Cancel action in the dashboard

digitalocean codegen leaves an orphaned security_secret.ts model file after its endpoint left the spec

extension promote accepts a yanked version and reports it promoted

Docs: doctor install reports a stale or failing autoupdate scheduler

extension push output: double-quoted adjacent interpolations, repo-relative paths, and --json emits three JSON documents

auto-resolve: the Installing line prints the extension's entire multi-line description

s3-datastore/serve: readResource without a version returns an older version; the latest marker is rewritten backwards

Publish agent-facing projections of the manual: /llms.txt, .md pages, and llms-full.txt

Let agent-runner drive more agent CLIs (Kilo Code and others)

s3-datastore: every fast-path miss re-downloads every _index shard, so a busy serve pulls the whole index every poll (~230 GB/day S3 egress)

Feedback: Swamp as an approval-gated control plane for a small fleet

extension safety analyzer's Deno.Command( warning is a plain substring match

Tell timeouts apart from cancels in method-run records, and review the hidden 30 s fallback timer for step-called model methods

Run from a git worktree: definitions from the worktree, state from the shared repo

S3/GCS datastore: a push that fails after uploading drops its recorded deletes, so the retry brings deleted data back

Tests: bring the in-memory remote's default semantics up to @swamp/s3-datastore and @swamp/gcs-datastore 2026.10.01.1

Tell the pushing client when its extension contentMetadata fails validation

Extension datastore: query still returns an item after its delete is pulled

Cancel, reject and supersede of a parent run should settle its suspended nested child runs

Relationships

#3110 Show signal waits to remote clients and the dashboard