Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
AssigneesNone

Relationships

#2203 Publishing manual contradicts registry omission defaults and supported visibility values

Opened by swamp_lord · 9/16/2026· Shipped 9/16/2026

The swamp-club Publishing Commands manual contains a pre-existing paragraph at content/manual/reference/extensions/publishing.md:154-156 claiming that new extensions default to private and that visibility: public can be set in the manifest. The same page now documents the deployed optional registry API contract from Lab #2200: omitted visibility preserves collective-based defaults (public collective -> public; private collective -> private), and the only supported explicit API value is private. This is reproducible at https://swamp-club.com/manual/reference/extensions/publishing: compare the paragraph below successful push output with Registry publication API / Omission and confirmation. Reconcile the CLI-facing claims with the actual supported/released CLI behavior and CLI follow-up #2198; clearly distinguish any future CLI defaults from the backward-compatible server defaults. The stale paragraph predates PR https://github.com/swamp-club/swamp-club/pull/1215. This is a documentation follow-up, not a request to change the preserved service behavior.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPEDTRIAGE+ 2 MOREREVIEW+ 4 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/16/2026, 9:41:06 PM

Click a lifecycle step above to view its details.

03Sludge Pulse

Sign in to post a ripple.