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

3h ago

#3124

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

8h ago

#3123

Accept usernames for user subjects in grant files

9h ago

#3122

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

9h ago

#3121

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

9h ago

#3120

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

10h ago

#3119

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

10h ago

#3118

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

10h ago

#3116

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

10h ago

#3114

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

11h ago

#3112

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

11h ago

#3111

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

11h ago

#3110

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

12h ago

#3104

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

12h ago

#3103

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

12h ago

#3102

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

13h ago

#3100

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

13h ago

#3095

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

14h ago

#3088

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

16h ago

#3080

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

17h ago

#3074

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

18h ago

#3073

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

18h ago

#3069

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

18h ago

#3067

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

19h ago

#3065

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)

19h ago

#3062

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

20h ago

#3060

Decide a stricter naming rule for workflow step and job names

12h ago

#3046

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

1d ago

#3045

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

1d ago

#3041

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

1d ago

#3040

extension promote accepts a yanked version and reports it promoted

1d ago

#3036

Docs: doctor install reports a stale or failing autoupdate scheduler

1d ago

#3017

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

1d ago

#3013

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

1d ago

#3010

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

2d ago

#3004

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

Team3d ago

#3000

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

4d ago

#2998

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)

4d ago

#2993

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

1d ago

#2965

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

4d ago

#2922

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

5d ago

#2908

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

5d ago

#2907

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

5d ago

#2906

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

5d ago

#2900

Tell the pushing client when its extension contentMetadata fails validation

5d ago

#2892

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

5d ago

#2867

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

6d ago

← Back to list

01Issue

FeatureOpenSwamp ClubPublic

AssigneesNone

Relationships

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

Opened by skunk-ape · 10/6/2026

Problem

swamp-club#3021 makes the CLI send the extension's declared acceptances (inline acceptance comments with their reasons, the sidecar acceptances, and the generated declaration) to the registry at confirm, as an optional top-level contentMetadata.acceptances field, so the registry page can show what the author acknowledged.

Today the server's validateContentMetadata (lib/domain/extension/extension-content.ts) rebuilds the stored object from the known keys only, so an unknown top-level key is silently dropped rather than rejected. The CLI change is therefore safe to ship first: nothing fails, but nothing is stored either.

Change

validateContentMetadata accepts an optional acceptances object: inline entries (rule, file, line, reason), sidecar entries (rule, file?, reason) and an optional generated declaration (by, source, commit). Caps on entry count and string length, same style as the existing per-kind validators. Absent field parses as today.
Extension version documents store it; the extension view shows an Accepted findings section listing each acceptance with its reason, and the generated declaration when present.
The field shape is owned by the CLI side (swamp-club#3021); mirror the final shape from that PR.

Acceptance

A confirm with contentMetadata.acceptances stores it and the version detail returns it.
A confirm without it behaves as today.
An oversized or malformed acceptances field is dropped with the same fallback the rest of contentMetadata uses, never a failed confirm.

swamp-club#3021 (CLI side), swamp-club#3065 (reviewEvidence at confirm, a sibling top-level field).

02Bog Flow

Open

10/6/2026, 6:37:36 PM

No activity in this phase yet.

03Sludge Pulse

system commented 10/6/2026, 6:37:36 PM

Classified automatically when this issue was filed.

Source: Swamp Club

If you feel this classification is incorrect, add a ripple to tell us so.

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

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

Problem

Change

Acceptance

Related

Open