Lab: UAT additions for W2 lifecycle services (Install/Remove/Upgrade)

Context

W2 (swamp-club#231 / PR systeminit/swamp#1310) introduces three lifecycle services owning the catalog-write surface end-to-end: `InstallExtensionService`, `RemoveExtensionService`, `UpgradeExtensionService`. The unit/integration test suite covers the contracts at the lifecycle-service layer (5433 tests passing). The existing UAT at `tests/cli/extension/` exercises CLI-level flows and continues to pass (87/87 with the W2 binary).

Per plan v4's Testing field, UAT additions for the new lifecycle layer are tracked as a follow-up, NOT a merge gate — existing UAT covers the user-visible flows; these proposed additions extend coverage to W2-specific contracts.

Proposed scenarios

1. swamp-club#201 closure at the user-visible layer

`tests/cli/extension/rm_catalog_pruning_test.ts` (new file):

Pull `@swamp/aws/ec2`.
`swamp model type search --json` returns ec2 types.
`swamp extension rm @swamp/aws/ec2`.
`swamp model type search --json` returns 0 ec2 types.
`swamp doctor extensions` reports zero stale catalog rows for ec2.

This is the user-visible #201 closure. Today's UAT covers rm but not the catalog-row-pruning observation via `type search`.

2. Atomic upgrade pattern

`tests/cli/extension/upgrade_atomicity_test.ts`:

Pull v1 of an extension.
`swamp extension pull @` — same name, different version.
Catalog has only v2's rows (no v1 leftovers, no `DuplicateTypeError` in the output).

Pinned by the unit-level upgrade service tests; UAT-level coverage proves the CLI surface honors the pattern end-to-end.

3. Force-pull regression

`tests/cli/extension/pull_force_regression_test.ts`:

Pull v1.
`swamp extension pull @ --force` succeeds (does NOT fail with `DuplicateTypeError`).

Today this scenario is implicitly covered by sibling_coinstall, but a focused test pins the contract.

4. Half-state recovery messages (commit 10's pinned UserError text)

`tests/cli/extension/half_state_recovery_test.ts`:

Construct a fault scenario (process kill mid-saveAll, or use the FaultingStubRepository if exposed via a test seam).
Assert the user-facing message contains the pinned recovery action: `swamp doctor extensions`, retry hint, etc.

This is harder to drive from UAT (needs fault injection). Could defer to integration-level once a CLI-driven fault seam exists.

5. DuplicateTypeUserError JSON shape

`tests/cli/extension/duplicate_type_json_test.ts`:

Construct a cross-extension type collision (two extensions pulled that share a `(kind, type)` — needs a fixture extension or registry mock).
`swamp extension pull --json` exit code 1.
JSON output contains `duplicateType.kind`, `duplicateType.type`, `duplicateType.existing`, `duplicateType.conflicting`.

This tests the structured shape that AI agents and `jq` consumers depend on.

Acceptance

New UAT files in `tests/cli/extension/` covering the scenarios above.
All scenarios pass against the post-W2 binary.
Existing UAT (87 tests) continues to pass.

Out of scope

Cross-process concurrency stress (separate follow-up, swamp-club issue).
Doctor extensions repair path (swamp-club#251).

extension unyank needs -y/--yes flag for non-interactive use

Step key parsing in execution_service uses naive split(":") and silently truncates colon-containing step names

Workflow-scope report artifacts unreachable via `swamp data get --workflow`

Add --stdin support to method run and workflow run for Unix pipe composition

Docs: add run namespace to CEL expressions reference

Fix invalidate-then-reconcile sequencing in doctor extensions; failure-mode RowStates unreachable in sourceDetails

doctor extensions invalidateAll does not trigger fingerprint recheck for existing Indexed rows

Extension failure recording has dual write paths (legacy buildIndex vs W3 reconcile)

Expose workflow run ID in CEL so resource keys can be run-scoped

Add `swamp doctor workflows` subcommand to surface workflow YAML parse errors during preflight

Add 'swamp issue comment' command for updating existing issues

Close #327 — fixed in 20260511.160514.0-sha.9d03b09a

Nested workflow task fails with 'Bad resource ID' when workflowIdOrName uses @collective/ prefix

Detect stale skill directories and prompt for repo upgrade

Improve skill trigger routing for cross-model edge cases

Add type search for driver, datastore, and report kinds

Surface ReconcileFromDisk dryRun transitions in swamp doctor extensions

Docs: update doctor extensions reference for W6 aggregate-state rendering + repair flags

swamp issue: check if reporter is on an outdated binary before opening

Implement W6: swamp doctor extensions aggregate-state rendering + repair surface (extension catalog rearchitecture)

extension pull fails referencing removed source after extension source rm

Investigate whether allExtensionMethodsAttached guard can be removed via registration-path consolidation

Trace context is lost: CLI ignores inbound TRACEPARENT and raw driver doesn't propagate active context into in-process methods

swamp model create --global-arg KEY=VALUE doesn't coerce strings to z.number() schemas

swamp model create --global-arg KEY=VALUE doesn't coerce strings to z.number() schemas

swamp issue get should rate-limit unauthenticated users instead of blocking

swamp issue get should not require authentication

telemetry: emit child entries for follow-up action method invocations

Publish release-candidate / unstable extension versions

extension source rm leaves stale @local/. rows in catalog, blocking later pulls of registry types

extension push drops binaries: field from re-emitted archive manifest.yaml

macOS launchd autoupdate (club.swamp.autoupdate) silently fails — binary stays stale

Clicking @hivemq/honeycomb extension card on /extensions shows 'Something went wrong'

Docs: Update model-definitions.md and workflows.md for direct type execution

Docs: document binaries manifest field in extension-manifest.md

Add an official @swamp/ssh extension for general-purpose SSH (brownfield-friendly)

Accept and display binaries field from extension push metadata

Direct type execution: collapse model create + method run into one command

Per-method telemetry events for workflow runs

Workflow run liveness: orphaned 'running' records when originating CLI process dies mid-run

Provide a CLI-shape primer for AI agents to reduce rediscovery overhead

quality rubric: don't penalize extensions whose upstream constrains them to a single platform

Extension update rejects multiple .ts files extending the same target type within one local extension (regression)

swamp extension push deadlocks when invoked from inside a swamp workflow step

Collective-scoped auth keys + OIDC federation for CI publishing

forEach self.* in modelIdOrName not resolved in runtime execution path

Award leaderboard points for referrals and collective invites

Add agent harness detection and AiTool to telemetry

Workflow-level runtime expressions (env.*, vault.*) not resolved in driverConfig — docker driver receives literal ${{ ... }} strings

Implement W5: Per-fingerprint import URLs + subprocess test harness (extension catalog rearchitecture)

swamp config set crashes with YAML serialization error

datastore compact: VACUUM fails in compiled binary (SQLITE_LIMIT_ATTACHED=0)

Repo-level version gating: minSwampVersion high-water mark for team consistency

Docs: document self.* expressions in modelIdOrName during forEach

Docs: How-to guide for background autoupdating

Manifest version bumps silently ignored for existing local extension aggregates

materialiseExtensions misclassifies pulled rows when manifest name collides with a pulled extension

Local extension edits don't reliably trigger rebundle

Missing unique indexes on user.email and user.username allow duplicate users

Resolve self.* expressions in modelIdOrName during forEach expansion

discord-bot double-sends sign_up notifications

Discord bot sends duplicate signup notifications

Add 'swamp workflow list' as alias for 'swamp workflow search'

Add 'swamp auth status' as alias for 'swamp auth whoami'

Extension bundle cache does not invalidate on source edits

extension pull fails on @local/[email protected] phantom-claim collision when local repo has its own extension

Lab search by numeric issue ID returns no results

W3 sourceToRow writes empty source_mtime — should carry filesystem mtime through Source entity

Warm-start rebundleAndUpdateCatalog should respect terminal RowStates set by reconcile

Implement W4: KindAdapter + unified loader (extension catalog rearchitecture)

Docs: add vault read-secret command to reference manual

Extension layer garbage collection: prune catalog rows + evict orphaned bundles

Docs: document workflow concurrency limits in reference manual

Locally-sourced extension: source_mtime updates without regenerating stale bundle

Extension push: allow shipping executable host helpers (bin/mudroom blocker)

Vault expressions silently deliver __SWAMP_VSEC__ sentinels under the docker driver

First-class shell-shim support for extensions, with registry-level visibility

Local extension model bundles don't rebuild when source changes (no rebuild CLI; manual cache delete breaks the runner)

Configurable concurrency limits for workflow fan-out (forEach, parallel jobs/steps)

feat(security): redact sensitive method arg values from audit log

Workflow-level runtime expressions (env., vault.) not resolved in driverConfig — docker driver receives literal ${{ ... }} strings