Lab #1312: Issue filing inherits most-recently-created collective's scope and privacy, with no way to choose

After creating a new collective and marking it private, all subsequent swamp issue bug and swamp issue feature commands file issues under that collective with private visibility — even when the issue has nothing to do with that collective.

The behavior appears to depend on the most recently created or joined collective, rather than the user's personal collective or an explicit choice. There is no flag to specify which collective context an issue should be filed under.

Current behavior

swamp issue bug and swamp issue feature file issues against whatever collective the system considers "current" (seemingly the last one created or joined).
If that collective is marked private, the issue inherits private visibility.
No CLI flag or prompt lets the user choose a different collective context at filing time.

Expected behavior

Issues should default to the user's personal collective unless explicitly scoped otherwise.
A flag like --collective <name> should let the user choose the filing context.
Privacy/visibility should be an explicit property of the issue itself (or inherited from a deliberate collective choice), not silently inherited from the most-recently-touched collective.
The CLI should make the filing context clear before submission (e.g., "Filing under @kneel (public)" or "Filing under @myorg (private)").

Why this matters

Users who create or join multiple collectives end up with issues scattered across the wrong scopes, sometimes with unintended privacy. A bug report meant for the public Lab ends up private and invisible to the team that could fix it. A feature request meant for a specific collective ends up filed against the user's personal namespace instead.

Steps to reproduce

Create a new collective (e.g., @myorg) and mark it private.
Run swamp issue bug --title "Test" --body "Test body".
Observe that the issue is filed under @myorg with private visibility, even though the user's personal collective is @kneel.

Environment

swamp CLI version: 20260720.142822.0-sha.0caa5556
Platform: linux

images list pulls full public catalog and crashes on duplicate names

issue --extension: documented example @adam/cfgmgmt is unroutable (no repo), so -x against it no-ops at exit 0

S3 datastore: model method run & datastore sync deadlock in commit/lock phase (anon_pipe_read), no self-heal

swamp extracts embedded deno into $HOME → unexecutable under SELinux Enforcing; all user extensions fail to load

Scheduled workflow runs (via swamp serve) don't count toward the streak

Extension runtime grants --allow-run but denies in-process Deno.open of a device node (blocks hardware I/O extensions)

Run-context variables (run.id, workflowRunId) undefined in step-input CEL after suspend+resume

`datastore setup filesystem` never transfers content when leaving a sync-based (remote) datastore — copies only the catalog and hardcodes `filesPulled: 0`

--server wss:// client offers h2 ALPN then fails the WebSocket upgrade over HTTP/2 (should pin http/1.1)

HTTP egress does not honor Happy Eyeballs (RFC 8305) on dual-stack DNS responses — IPv6 blackhole hangs the request

Documentation gives conflicting behavior for pulling yanked extension versions

Issue filing inherits most-recently-created collective's scope and privacy, with no way to choose

Extensions page: Search bar missing on mobile

swamp extension version crashes with 'Invalid CalVer version: "null"' when only a prerelease (beta/rc) version is published

gcp/calendar events.list reads wrong array field ('defaultReminders' not 'items') → always returns 0 events

@swamp/gcp/calendar: service-account & ADC auth mint cloud-platform-scoped tokens → 403 on Calendar API

export const extension can graft methods onto foreign-collective types, undisclosed in extension info / contentMetadata

Interactive finder silently drops the preview pane on narrower terminals, and layout selection is unstable

Interactive finder preview corrupts: overlapping/stale lines when preview content overflows the pane

vault edit resolves wrong path (.swamp/vault/ instead of repo-root vaults/)

swamp auth login prompts are confusing — "username" only accepts email, and --username is re-prompted

swamp issue get exposes commentCount but no way to read ripple bodies

No way to log in on a headless host or with an OIDC-only account — please allow an API key

readResource + vaulted sensitive fields: cross-run reads return the unresolved ref, and per-instance vault keys appear to collide

Blocked model methods are uninterruptible: SIGINT/SIGTERM don't force-exit; no cancellation signal for execute()

Surface the bundled deno path in the first-loaded extension guide + expose it via CLI

Pin the deno runtime for extension checks — bare `deno` is a PATH-hijack surface for the test/lint runtime

[@adam/cfgmgmt] ssh-exec models uninterruptible: SIGINT/SIGTERM ignored, child ssh not aborted (only SIGKILL works)

Stripe checkout product description says '2–20 portable seats' but platform allows 1–20 for Team

Tracing ignores OTEL_RESOURCE_ATTRIBUTES — only service.name reaches the Resource

Drag Windows into the Swamp

Relationships

#1312 Issue filing inherits most-recently-created collective's scope and privacy, with no way to choose

Open