Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneesstack72

#203 Docs: extension commands reference

Opened by stack72 · 5/1/2026· Shipped 5/1/2026

Problem

content/manual/reference/ currently has no page documenting the swamp extension <list|update|outdated> family of commands. This is a pre-existing gap — extension list and extension update predate this issue — but the freshness UX added in swamp/swamp PR #1276 (issue #199) is a good moment to close it.

Proposed page

A new content/manual/reference/extension-commands.md (or similar) covering:

swamp extension list

  • What it shows (installed extensions with version, pulled time, files).
  • TTY-aware side-by-side latest column.
  • --check-updates / --no-check-updates flag semantics.
  • 24h cache cooldown matching CHECK_INTERVAL_MS.
  • JSON shape, including the optional latestVersion / updateStatus fields and the unknown_offline status.

swamp extension update

  • Update mode (default) vs --check mode.
  • Per-extension vs all-extensions behavior.
  • Interaction with the upstream_extensions.json lockfile.

swamp extension outdated (new)

  • Strict semantic: exit 1 only when at least one extension has update_available; not_found / failed are rendered but do NOT fail the exit code.
  • Suitable for CI gates: swamp extension outdated && deploy.
  • JSON shape: { extensions, hasUpdateAvailable }.

Cache and registry behavior (cross-cutting)

  • 24h cooldown rationale (matches datastore auto-update).
  • Cache-stamp-on-failure semantics: registry failure stamps latestVersion: installedVersion to suppress retries for 24h. During that window, the entry reads as up_to_date even after registry recovery — this is by design (advisory not transactional).

References

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 8 MOREREVIEW+ 3 MOREPR_MERGEDSHIPPED

Shipped

5/1/2026, 6:30:29 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack725/1/2026, 3:48:06 PM

Sign in to post a ripple.