Lab #3047: extension push: restore --yes waiving warnings (revert the 20261005.154947.0 flag split), keep the accepted-warnings record, --accept-warnings stays as an optional alias

Problem

swamp 20261005.154947.0 (PR swamp-club/swamp#2833, Lab #3015) changed what --yes means on swamp extension push: it no longer waives safety and review warnings, and a non-interactive run (--json, or stdin not a terminal) that meets any warning exits non-zero unless --accept-warnings is passed. Nearly every extension published from a clean runner carries at least one warning (the adversarial-review report is never present there), so every external CI publish that tracks the stable channel fails on its next run. Known exposure: @hivemq, @dataverket, @magistr and @dieter published in the last 30 days; jentz publishes from GitHub Actions; swamp-extensions' own publish.yml. No deprecation notice preceded the change.

Decision (Seth, 2026-10-05): the step was too big. The accountability gain is wanted; the breaking flag semantics are not. The longer-term shape is declared acceptances beside the code and the manifest (a redesigned #3021), not a blanket run-time flag.

Expected

--yes (and --force) waive safety and review warnings again, exactly as before 20261005.154947.0, including for --json and non-TTY runs. No existing CI invocation changes behaviour.
The acceptedWarnings record that #3015 added stays: whenever warnings are waived, by --yes or by --accept-warnings, the log summary prints "Accepted N warnings" with one line per warning and the --json completed document carries the record. Making waivers visible is the part to keep.
--accept-warnings remains accepted as an optional alias so nobody who adapted today is broken twice. It is documented as optional and equivalent to --yes for the warnings prompt.
Interactive behaviour unchanged: two prompts, two answers.

Acceptance

push --dry-run --json --yes on an extension with the adversarial-review warning: exit 0, acceptedWarnings present.
push --dry-run --yes with stdin not a TTY: exit 0, summary lists the accepted warnings.
push --dry-run --json with neither flag: the pre-3015 behaviour.
push --dry-run --accept-warnings: same result as --yes for the warnings gate.
Safety and review-rule errors still fail regardless of flags.
The gate tests in src/cli/commands/extension_push_test.ts updated for the restored matrix; renderer tests for the record kept.

Also in this change

Revert the flag-matrix text in the bundled swamp skill references and design/primitives/extensions.md from PR #2833 to describe the restored behaviour and the optional alias.
Changelog entry naming the two releases and the reason.

#3042 (publish.yml passes --accept-warnings) is cancelled by this.
swamp-uat #528's test for the refusal needs adjusting to the restored behaviour.
Lab #3026 (manual docs for the flag table) follows this, not #3015.
#3021 is being redesigned around declared acceptances (inline swamp-review-ignore comments for site-scoped rules; a sidecar review file beside the manifest for extension-scoped findings); that is where any future tightening of --yes would be decided, with a deprecation window.

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

Tracking: test baseline required before the datastore refactor (commit-log design)

Tests: serve pollers make a peer's writes, deletes and grants visible with a real catalog (before Phase 5)

datastore setup can overwrite an existing remote config tier when it moves an in-repo tier into an extension datastore

serve: define and supply the collective and owner grant condition variables

No first-class workflow primitive for spawning a permission-scoped agent session

Relationships

#3047 extension push: restore --yes waiving warnings (revert the 20261005.154947.0 flag split), keep the accepted-warnings record, --accept-warnings stays as an optional alias

Problem

Expected

Acceptance

Also in this change

Related

Shipped