Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLIPublic
Assigneesskunk-ape

Relationships

#4623 serve: pass swamp-club's links_require_plan refusal to the app, and record links ended by a lapsed plan

Opened by skunk-ape · 11/10/2026· Shipped 11/10/2026

Part of #4459. Sibling of #4622, which opens serve links to collectives on an active trial or a paid plan and ends a collective's links when that standing lapses.

Problem

Two things serve will meet once swamp-club ships that change:

  1. A refusal for a collective without standing. swamp-club will answer link start, capabilities and consent with 403 links_require_plan and a message, instead of 404. Today serve reads a 404 from capabilities as "this swamp-club has no link routes". What it does with a 403 hasn't been checked: it must refuse the link and pass the reason to the app, not report swamp-club as down (club_unavailable) or retry.
  2. Links ended because the plan lapsed. swamp-club will end them on the change feed with endedReason: "plan_lapsed". Serve records any reason other than disowned as club_ended, so the end applies, but the cause is lost.

Proposed change

  • On a 403 links_require_plan from swamp-club, serve refuses the link start with its own reason, carrying swamp-club's message, and the app sees it on the delegation routes. The same applies to the capability check, which no longer reads this as an unsupported swamp-club.
  • Record plan_lapsed as its own end cause, in audit and in access delegation list and show.
  • First check and report what today's released serve does on that 403, so swamp-club's change can ship knowing the behaviour of serves already deployed.
  • Update design/enablers/access-control.md and swamp-uat's strict schemas.

Done when

  • A link start against a collective without standing is refused with a distinct reason and swamp-club's message, on every transport, and isn't retried or reported as swamp-club being down.
  • A link ended on the feed with plan_lapsed is recorded with that cause, and refused like any other end.
  • The behaviour of the current released serve on that 403 is recorded on this issue.
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 2 MOREREVIEW+ 8 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/10/2026, 11:51:37 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
skunk-ape assigned skunk-ape11/10/2026, 10:47:53 PM

Sign in to post a ripple.