Lab #944: Badge for activity on other people's issues

Problem

Swamp currently rewards some kinds of activity, but there is no visible badge or achievement that encourages people to participate in issues created by other community members, especially outside the Swamp Club Inc crew.

This means users may mostly stay within their own issues or familiar discussions, missing chances to browse other people's issues, learn more about Swamp, and learn more about each other.

Proposed solution

Add a community-growth badge for "activity on other people's issues".

One possible metric:

Count unique issues where a person rippled/commented.
Exclude issues created by that same person.
Award badge levels based on the unique count, not raw comment volume, to motivate broad participation rather than piling comments onto one thread.

Motivation

This would motivate people to browse and engage with other people's issues, discover more use cases, learn more about Swamp, and build connections across the community.

Notes / open questions

Should Swamp Club Inc crew-authored issues be excluded entirely, or just counted separately?
Should the badge require substantive ripples, or is any ripple enough for an initial version?
Suggested badge framing: community explorer, issue neighbor, or similar.

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

#944 Badge for activity on other people's issues

Problem

Proposed solution

Motivation

Notes / open questions

Closed