Lab #638: Add deprecate/yank/unyank actions for own extensions on the web interface

Problem

Publishers can deprecate, yank, and unyank their own extensions via the CLI, but the swamp.club web interface provides no way to perform these actions. This forces users to context-switch to the CLI for lifecycle management tasks that are otherwise discoverable through the UI.

Proposed Solution

Add deprecate, yank, and unyank controls to the extension detail/management page on swamp.club, visible and enabled only for the authenticated owner of the extension.

Scope of Changes

Web frontend: Add action buttons (Deprecate, Yank, Unyank) on the extension detail page, gated by an ownership check against the authenticated session.
API: Expose deprecate/yank/unyank endpoints if not already available over HTTP (the CLI likely calls these internally).
UX: Show current deprecation/yank status clearly on the page so users know the current state before acting.

Alternatives Considered

Continue CLI-only — but this makes lifecycle management invisible to users who discover and manage extensions primarily through the web interface.

First-class scheduled garbage collection policy per datastore namespace

Fine-grained scopes for swamp.club access tokens

Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

Email invitation is not linked to account created from invite URL

Guide agents to inspect reports after failed model and workflow runs

Add a 'my collective extensions' filter to extensions page

Regression: swamp update syncs global skills to unconfigured agent directories

swamp serve crashes with JavaScript heap OOM while running scheduled workflows

swamp serve startup/shutdown is very slow on large repo and lacks diagnostics

swamp serve should survive bad extension failures

[@adam/cfgmgmt] SSH helper can crash swamp serve via unhandled finally() rejection

Allow swamp clients to send custom headers when connecting to swamp serve

MethodContext docs/comments mention context.putSecret but runtime exposes vaultService.put

install.sh still points users to systeminit/swamp

Support user systemd units for 'swamp serve daemon enable'

Support installing swamp via mise GitHub backend

Allow changing an existing issue to security/confidential after submission

Allow dynamic object expressions for workflow task inputs/globalArgs

Login success still shows login tip

Support confidential visibility for non-security issues

swamp update syncs global skills to default agent directories instead of configured custom Pi skillsDir

Badge for activity on other people's issues

doctor extensions reports source-mounted bundles as unreferenced after repair

Agent setup suggests repo init in already initialized repos

repo upgrade reports success but extension commands still warn about pending migration

model evaluate is slow resolving data.latest expressions in large datastores

Add SSH host public key collection for host certificate workflows

Extension detail page shows deno doc module-not-found failure for published extension

Resolve dynamic workflow task targets inside forEach

Can't click on repository from swamp extension search.

swamp serve does not open the UI

Add deprecate/yank/unyank actions for own extensions on the web interface

swamp update --setup-auto does not work with bluefin44 (crontab not found, should

Terminal rendering breaks at large font sizes

Relationships

#638 Add deprecate/yank/unyank actions for own extensions on the web interface

Problem

Proposed Solution

Scope of Changes

Alternatives Considered

Shipped