paths.base: manifest is not honored for workflows: — bundled workflows only resolve from repo root, blocking self-contained subdir layouts (sibling to #459)

When the CLI is authenticated with a collective/org token (swamp_org_…), the telemetry flush sends that token as x-api-key, but it is not resolvable to a username server-side — so the invocation is recorded without an identity and the user is mis-bucketed as anonymous. Additionally, the telemetry distinct_id is the per-machine ~/.config/swamp/identity.json id (not the .swamp.yaml id), so ephemeral/CI environments mint a fresh unclaimed id on every run.

Impact

Authenticated CLI operators who use collective auth never get linked to their account in telemetry.
CI/ephemeral runs generate a brand-new unattributed distinct_id each time, inflating "anonymous heavy user" counts.

Details (CLI side)

Telemetry sends the stored key as x-api-key on /ingest — src/infrastructure/telemetry/http_telemetry_sender.ts:53.
authToken is loaded from AuthRepository and distinct_id is the user-level identity id — src/cli/mod.ts:984 and src/cli/mod.ts:976 (distinctId: telemetryCtx.userId ?? telemetryCtx.repoId); the .swamp.yaml repoId is sent only as the $repo_id property.
extension push supports publishing under a collective — src/libswamp/extensions/push.ts (whoami / fetchCollectives). In that mode the token sent to telemetry is a swamp_org_… key, which the ingest's personal-key resolver cannot turn into a username.

Reproduction

Authenticate the CLI with a collective token (swamp_org_…).
Run swamp extension push for a @collective/* extension (succeeds).
The publishing distinct_id never appears in any identity_map entry.

Suggested fix (CLI side)

For collective auth, forward an identity the server can attribute (e.g. include the acting member's username in event properties when known from whoami, or send a personally-resolvable credential alongside).
Consider distinct_id stability for CI/ephemeral environments so repeated runs don't each create a new unclaimed id.

Sibling server-side defect: swamp.club Lab #446 (ingest only resolves personal API keys, never the collective resolver).

02Bog Flow

Closed

5/26/2026, 4:32:37 AM

No activity in this phase yet.

03Sludge Pulse

keeb assigned keeb5/26/2026, 4:20:52 AM

keeb commented 5/26/2026, 4:32:36 AM

Disposition: closing — fix belongs server-side (#446)

After triage and adversarial review, this is not a CLI defect and the suggested CLI-side fix should not be implemented.

The suggested fix is spoofable. Forwarding the acting member's username in the telemetry event properties means the identity travels in the attacker-controllable JSON body. Any client could post auth_username: "<someone-else>" and poison another account's attribution. Identity must be derived from a validated credential, never self-asserted by the client.

The server is — and must be — authoritative. The CLI already forwards the only trustworthy identity signal: the validated x-api-key bearer credential (src/infrastructure/telemetry/http_telemetry_sender.ts:53), sent on every authenticated flush. The actual gap is that the ingest's resolver only maps personal API keys to a username and cannot resolve collective swamp_org_… keys. That resolution is server-side work, tracked as the sibling defect #446.

distinct_id is a separate, lesser concern. The per-machine identity.json UUID churns in CI/ephemeral environments, but for authenticated runs the server can alias whatever distinct_id arrives to the account it resolves from the api-key — so no client change is needed for attribution. (Stabilizing the anonymous bucket for unauthenticated ephemeral runs is a minor, independent idea, not part of this issue.)

Action: No CLI code change. Attribution for collective auth is resolved by #446 (server-side resolver). Closing here and routing to #446.

Should be able to see all the issues I created by a filter "submitted by me"

Ability to change the email address associated with my Swamp Club Account

feat: giga-swamp phase 5 — CLI output + namespace management commands

CI review jobs use two-dot diff that includes files the PR never touched

paths.base: manifest is not honored for workflows: — bundled workflows only resolve from repo root, blocking self-contained subdir layouts (sibling to #459)

Lab profanity filter rejects legitimate CLI flag tokens via substring match

Sign and notarize the swamp macOS binary

Add platform type to issue-lifecycle extension model Zod schema

fix: datastoreSetupExtension() ignores namespace config on initial migration push/pull

Remote execution: orchestrator/worker fan-out (replaces execution drivers)

swamp datastore sync --push creates global .datastore-index.json ignoring namespace config

feat: S3/GCS extension namespace-scoped sync support

Copy explicitGlobalArgs before mutation in resolveOrCreateDefinition

vault.get() expressions in extension model globalArguments are not resolved at runtime

swamp-issue skill should scrub secrets and org-specific data before submission

workflow validate: trim stale 'skipped' label from model_not_found warning

Add pi coding agent support

hashicorp-vault should read token from env

swamp-extension adversarial review skill needs mandatory mechanical verification checklist

feat: giga-swamp phase 6 — Namespace-scoped sync

swamp workflow validate emits misleading "Extension failed to load" warning when type resolves locally

Add issue search/list command to discover existing issues

Support vault-resolved private key content in transport auth (not just file paths)

Workflow engine resolves extension methods against base type, ignoring extension-registered methods

Per-model LockTimeoutError at 60s causes cascading failures under concurrent access

Persistent, queryable workflow runs (status / cancel from any shell)

swamp repo upgrade: ERR_SQLITE_ERROR 'attempt to write a readonly database' during extension catalog schema migration

workflow validate: fail on references to unknown model instances (typo'd modelIdOrName)

feat: giga-swamp phase 4 — CEL cross-namespace queries

Docs: document the extension push adversarial-review gate

vault://local_encryption token does not round-trip correctly for GCP OAuth2 access tokens

swamp issue: add ability to edit issue title and body after submission

@swamp/gcp/iam: add WIF pool, provider, service account, and binding support

Support vault-sourced identity keys

copy method reports success when scp exits non-zero (e.g. 255)

Docs: TLS behind inspecting proxies / private CAs (system trust store, DENO_CERT, SSL_CERT_FILE)

Extension quality/adversarial-review: add a 'published-surface hygiene' check for real infra identifiers

Feed-post scoring is a direct domain write, not a consumer of feed_post_approved telemetry

workflow validate silently PASSES steps whose model type is a pulled extension (step-inputs skipped = false pass)

extension quality fails to resolve bare specifiers — contradicts fmt no-import-prefix rule

Allow global arguments in direct type execution (workflow fan-out)

Bundled Deno does not honor the OS/system CA trust store

Gator-approved feed post did not trigger Discord activity or profile points

username_metrics projection backfill does not trigger re-scoring (stale UserScore for dormant users)

Enforce adversarial review gate before extension push

support git forge / web namespaces for collectives

Report type filtering in report search

extension search: empty results from CLI despite known extensions

workflow approve/resume cannot find suspended runs

vault annotate --url fails with query params on @swamp/aws-sm

datastore compact VACUUM fails with ERR_SQLITE_ERROR

workflow approve/resume cannot find suspended run when using S3 datastore

reindexByUsername re-strands pre-association history and wipes sign_in_dates

Telemetry never retroactively credits a device's pre-association history

Docs: document swamp doctor secrets in manual reference doctor.md

Docs: document 'swamp workflow resume --input' in manual reference

Cloudflare codegen: manifest version bumps on every regeneration (README not deno-fmt-clean)

Support dynamic host discovery from external sources

feat: giga-swamp phase 3 — Path resolver + per-namespace locking

@swamp/ssh exec: string host selector only matches 'all', ignores host names and tags

Add integration test for sensitive-arg guard on lazily-loaded extension types (follow-up to #480)

Remediate existing definitions holding cleartext sensitive global arguments (follow-up to #480)

Docs: document refusal of literal sensitive global arguments (follow-up to #480)

Docs: update extension-trust reference for swamp-only default + lockfile version pinning (swamp-club#465)

feat: giga-swamp phase 2 — Catalog schema v4 + repository interface

Support for Custom CA's

Cloudflare: support vault expressions for API credentials instead of env-var-only auth

GCP: support vault expressions for credentials instead of env-var-only auth

AWS: support vault expressions for credentials instead of env-var/SDK-chain-only auth

DigitalOcean: support vault expressions for the API token instead of DO_API_TOKEN env var

swamp model get does not redact `sensitive: true` fields (logs/reports/storage do)

Support vault expressions for API token instead of env var

UAT tests for manual_approval workflow commands

Document manual_approval workflow step type and suspend/approve/resume flow

Stale extension bundles break after swamp upgrade

Support --input flags on workflow resume for elevated permissions and runtime overrides

Add HTTP approval endpoints to swamp serve for manual_approval steps

feat: giga-swamp phase 1 — Namespace value object + config

swamp serve scheduled workflows do not load repo extension registries

ci: aws-check and gcp-check jobs take ~30min — rethink whether full model type-checking is needed per PR