Lab #502: Gator-approved feed post did not trigger Discord activity or profile points

Summary

A new writing post was approved by Gator and is visible in the swamp feed, but the Discord auto activity bot did not post about it and no points appear to have been assigned to the mgreten swamp use profile.

Evidence

Feed post is live: https://swamp.club/feed/p/81960084-1959-4277-b5a2-1a10741fa0a5
Profile expected to show points/activity: https://swamp.club/u/mgreten
Local swamp CLI version: 20260521.221703.0-sha.3f2b75f8

Expected behavior

After Gator approves a writing post and it appears in the swamp feed:

The Discord auto activity bot posts about the new activity.
Points are assigned to the author's swamp use profile.

Actual behavior

The approved post is visible in the feed, but no Discord auto activity appeared and points are not visible on the profile.

Steps to reproduce / investigate

Approve or inspect the feed post above.
Check whether the Discord auto activity job emitted a message for post 81960084-1959-4277-b5a2-1a10741fa0a5.
Check whether the points assignment pipeline processed that same post for user mgreten.
Compare against other recently approved writing posts that did trigger Discord activity and profile points, if available.

Impact

Approved writing can appear publicly without the expected community activity notification or profile credit, making it look like the contribution was not counted.

New Release Discord notification links to GitHub Actions run instead of swamp changelog/release notes

/feed: filter and search by author, title/text, and topic

Unclear whether SWAMP_API_KEY auth claims a device's banked "ghost" reputation, or only swamp auth login does

Vault: native secret-read access audit trail

runModel(): options.arguments never reach the child's per-method arguments — merged into globalArgs, then dropped or rejected

runModel(): nested outputs record triggeredBy "manual" with no parentOutputId — docs promise model-trigger lineage

commitPush no-op verification fetches the full monolithic index instead of the v2 shard/commitSeq fast-path (follow-up to #1034)

Catalog export re-uploads the full monolithic object every sync, even with zero changes (sibling to #1034)

Shard-first v2 still re-uploads the full monolithic index + catalog export every commit; silent writeback failure above the 30s request timeout

S3 datastore push walks the entire cache root — nested/foreign namespace dirs become doubled index keys (recurring)

extension update/install reports new version while on-disk pulled files stay old

Orphaned data (migrated-away/deleted model) can't be GC'd or deleted

datastore migrate-index aborts on hardcoded 30s S3 requestTimeout for large shards

datastore migrate-index ignores the repo's configured namespace (migrates bucket-root index instead)

Intra-namespace write concurrency: whole-index sync under the lock serializes fan-out workloads (split from shipped #666)

Pre-sync pull aborts the whole command when an index entry's S3 object is missing — no built-in way to recover

Local model source edit may not change the bundle cache key — rebuilt bundle shadowed by an older same-hash copy on a shared S3 datastore

autoGc emits auto_gc_completed event on --json stdout, breaking single-parse consumers

Batch / prefix delete for swamp data delete (single lock acquisition)

Same-namespace writers fully serialize on the per-namespace lock — could maintenance/append writes avoid holding it?

Could method-summary report artifacts get a default retention cap? They grow to dominate the datastore manifest

Datastore should fail fast on unresolvable credentials instead of stalling on the AWS provider chain

Optional scheduled / automatic datastore GC (retention-policy-driven pruning)

Notify issue author/participants on ripples & status changes — with Discord bot DM as a delivery channel

Single __global__ datastore lock serializes unrelated writes across all repos/namespaces

swamp data gc prunes the catalog but never deletes objects from S3 datastores (markDirty hook not wired) — sync manifest never shrinks

data gc --dry-run ignores the flag and performs a destructive GC

Private / org-scoped collectives with member ACLs

Resident/warm worker mode — `model method run` has ~6s fixed per-invocation overhead that rules out latency-sensitive use

Homepage install command: wrong domain and missing https:// protocol

Homepage install command: wrong domain and missing https:// protocol

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

swamp CLI commands fail silently or hang when invoked from git worktrees via SWAMP_REPO_DIR

Many CLI commands acquire global .datastore.lock unnecessarily, causing 60s LockTimeoutError under any concurrent writer

Relationships

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