Swamp Club
Narrow, typed Swamp Club Lab issue intake and approved-ripple adapter.
2026.10.21.1
Fixed: The README's swamp model create example omitted the required
apiKey global argument and only said the key "should be supplied from a Swamp
vault". It now stores the key with swamp vault put swamp-club API_KEY and
wires it with ${{ vault.get("swamp-club", "API_KEY") }}. The apiKey
argument now carries a description saying the same.
Upgrade note: Documentation only. No code, schema, or behavioral changes. The model version moves to 2026.10.21.1 with an identity upgrade.
Global Arguments
| Argument | Type | Description |
|---|---|---|
| host? | string | |
| apiKey | string | Swamp Club API key. Supply it as ${{ vault.get("swamp-club", "API_KEY") }}; never pass the literal key |
| maxComments? | number |
| Argument | Type | Description |
|---|---|---|
| issueNumber | number |
| Argument | Type | Description |
|---|---|---|
| issueNumber | number | |
| body | string |
Resources
2026.10.14.1
Added: The manifest now declares license: Apache-2.0 (SPDX). The registry quality rubric scores a declared license separately from the bundled LICENSE.md.
Upgrade note: Metadata only. No code, schema, or behavioral changes.
2026.10.12.1
Fixed: Repeating an idempotencyKey on post_ripple no longer fails the
workflow step. The method returned a handle with only a name when the key had
been seen before. The runtime rejected it
(expected string, received undefined (path: dataId)), so a workflow that
repeated a key reported failure on every run. Dedup itself was unaffected: no
duplicate ripple was ever posted.
Changed: A repeated key now re-writes the existing ripple record
unchanged and returns its full handle. Each repeat adds a version of that
record (retention is still 20 versions) whose 30-day lifetime starts from the
repeat. No Swamp Club API call is made on a repeat.
2026.10.12.1
Fixed: Repeating an idempotencyKey on post_ripple no longer fails the
workflow step. The method returned a handle with only a name when the key had
been seen before. The runtime rejected it
(expected string, received undefined (path: dataId)), so a workflow that
repeated a key reported failure on every run. Dedup itself was unaffected: no
duplicate ripple was ever posted.
Changed: A repeated key now re-writes the existing ripple record
unchanged and returns its full handle. Each repeat adds a version of that
record (retention is still 20 versions) whose 30-day lifetime starts from the
repeat. No Swamp Club API call is made on a repeat.
2026.09.18.1
Upgrade note: Normalized npm:zod dependency version to 4.6.5 across the
repo. No behavioral changes in this extension.
2026.09.15.1
Changed: Bump zod 4.4.3 → 4.6.5
2026.09.08.1
Added: Typed Lab issue collection and explicitly approved ripple posting for cross-provider triage.
2026.09.08.1
Added: Typed Lab issue collection and explicitly approved ripple posting for cross-provider triage.
- Has README or module doc2/2earned
- README has a code example1/1earned
- README is substantive1/1earned
- Most symbols documented1/1earned
- No slow types (deprecated)1/1earned
- Dependencies pass trust audit2/2earned
- Has description1/1earned
- Platform support declared (or universal)2/2earned
- License2/2earned
- Verified public repository2/2earned