feat(clickhouse): tracked archive→CH backfill tooling (backfill.sql)

Thanks for the quick turnarounds on #666 and #788 — both landed fast and have already helped. Here's a follow-on I turned up while profiling that looks worth addressing on its own.

What I found

Every swamp model method run emits two auto-generated report artifacts — report-swamp-method-summary and report-swamp-method-summary-json — and each is retained as a new data version indefinitely. For high-frequency runners these accumulate steadily and end up dominating the datastore index that gets pulled/pushed under the lock on every write.

Profiling one busy namespace (related to #666): of 109,152 catalog rows / 156.6 MB tracked, only 13,884 rows (7.1 MB) were current state — ~95% was non-latest versions. The auto-generated method-summary artifacts alone were roughly half the manifest:

one frequently-run model: ~67.6 MB of method-summary versions
a polling model: ~37.8 MB
another: ~3.3 MB

These are generated automatically rather than written by the user, so an unbounded version history of per-run summaries is probably not what anyone wants.

Why it matters

It sits upstream of (and independent from) the lock-scoping in #666 and the gc/S3-delete fix in #788:

The full ~110 MB index is pulled/pushed under the lock on every write, so manifest size gates the lock-hold for all writers in the namespace — even a trivial vault write or a 7-entry gc pays the full-index cost.
swamp data gc is the natural mitigation, but on S3 datastores it prunes the catalog without deleting backing objects (#788), so it doesn't shrink the manifest today — and even once that's fixed, a default cap keeps the manifest from re-bloating between gc runs.
Ephemeral lifetime also doesn't appear to be implemented yet, so tagging these artifacts ephemeral isn't currently an escape hatch.

A few directions that could work

A default retention cap on the auto-generated method-summary artifacts (e.g. keep the last N versions or N days), configurable per repo.
Implementing ephemeral lifetime and defaulting these auto-generated artifacts to ephemeral, so they auto-collect.
An opt-out for a model to disable method-summary artifact emission where it isn't useful.

Whichever fits the architecture best — I can share more profiling data if it'd help. Thanks again.

Environment

swamp: 20260624.181631.0-sha.aa2ae00f
@swamp/s3-datastore@2026.06.24.1 (MinIO backend)
OS: darwin (aarch64)

02Bog Flow

Closed

6/25/2026, 9:54:24 PM

No activity in this phase yet.

03Sludge Pulse

stack72 assigned stack726/25/2026, 8:54:08 PM

stack72 commented 6/25/2026, 9:54:23 PM

Hey @mgreten — we've consolidated this with #806 (optional scheduled/automatic datastore GC) into #823, which covers opt-in automatic GC for datastore data. During triage we found that the core issue is the catalog export (.catalog-export.json) serializing all versions on every push — your profiling showed 95% of the 109K catalog rows were non-latest versions. We explored inline GC, latest-only export, and overwrite semantics, but landed on opt-in auto-GC as the cleanest approach that keeps data and catalog in sync without orphaning remote data. #823 captures all of this. Thanks again for the thorough profiling data and the clear write-up — really helped us understand the impact.

feat(clickhouse): tracked archive→CH backfill tooling (backfill.sql)

feat(clickhouse): idempotent DDL migration path for running prod (#859 deliverable 2)

chore(clickhouse): retire S3-backed v1 + s3 objects after #859 cutover

Decouple prod ClickHouse from S3 (drop storage_policy=s3_main) + add a DDL migration path

Epic #847 · Unit 6: Document the Mongo-vs-ClickHouse storage-architecture split in scoring.md

Epic #847 · Unit 5: ClickHouse materialized-view projections + atomic leaderboard read-flip + delete Mongo OLAP

Epic #847 · Unit 4: Stream confirmed grants into ClickHouse score_grants (ReplacingMergeTree)

Epic #847 · Unit 3: Migrate the 5 recompute contributions to per-event grants; delete the recompute path

Epic #847 · Unit 2: score_grants append-only ledger write-model in Mongo (shadow, no read flip)

Epic #847 · Unit 1: Land the ClickHouse projection foundation (schema + init SQL + compose service)

Global skills should auto-sync when binary version advances

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

Extension publish score is non-monotonic: yanking versions lowers a user's score

Live Swamp Club event console on /feed — scrolling stream of all non-sensitive events

Docs: add --ws-idle-timeout to serve flags reference

copy/rsync ignores transport extraOptions (and proxyCommand), unlike exec/script

Remove feed comments — consolidate discussion in Discord

Make serve WebSocket idle/keepalive timeout configurable (untunable default aborts runs when serve's loop briefly blocks)

Docs: update extension info reference with content metadata output

serve startup time regression: synchronous catalog init delays WebSocket listener by ~4.5 minutes

Expose run/job/step identifiers as SWAMP_* env vars + CEL values, and template placement selectors (extends #331's run.id)

fix: add .namespace.json to isInternalCacheFile() in datastore extensions

docs: document swamp serve daemon enable/disable/status subcommands

docs: document execution cancellation commands and cancelled status

docs: document autoGc config option for automatic garbage collection

Docs: document @env= and @file= webhook secret indirection in swamp-serve reference

fix: datastore sync --push deletes the namespace registration manifest (canonical namespace flow un-registers itself)

docs: bundled swamp agent skill lacks datastore-namespace guidance (giga-swamp)

data query --select crashes on BigInt: "Do not know how to serialize a BigInt" when CEL size() reaches the JSON renderer

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

Telemetry recoverOrphaned startup race with multiple replicas (created_at-based)

Telemetry retry/failed path has the same non-atomic claim as #820

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

Surface extension type+method detail in CLI to eliminate expensive discovery loops

Skill guides lack progressive reveal boundaries — agents over-read by 4x

Opt-in automatic garbage collection for datastore data

UAT: swamp workflow evaluate/run with forEach dynamic workflowIdOrName targets

Telemetry watcher has no replica coordination: N replicas double-process the same batch (non-atomic find→updateMany claim)

Telemetry drain still capped ~80-100/s in prod: per-username full-history re-aggregate is O(users) sequential per batch (deferred #817 fix #4)

Telemetry ingest is consumer-bound: counter & stats dedup via O(N) sequential insertOne, throughput stuck ~20 events/s regardless of BATCH_SIZE

Resolve dynamic workflow task targets inside forEach

Leaderboard and profile streak not reporting

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

Docs: update vault inspect output in manual reference

Execution cancellation: abort stuck workflow runs and model method runs, bulk cleanup, and daemon-restart reaping

Docs: document .? optional select for null-safe CEL data access

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

Batch step 2 of enrichAuthorPlans (per-collective subscription reads)

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

Add SWAMP CLUB wordmark logo next to sc-mark.png in TRADEMARKS.md

Add SWAMP CLUB wordmark logo next to sc-mark.png in TRADEMARKS.md

pushChanged does not implement absence-on-disk deletion (markDirty contract rule #2)

pushChanged does not implement absence-on-disk deletion (markDirty contract rule #2)

Add `vault delete` support to @swamp/aws-sm extension

Add `vault delete` support to @swamp/azure-kv extension

Add `vault delete` support to @swamp/1password extension

Leaderboard window baseline: 90-day cutoff zeroes returning-dormant users (latent, 0 impact today)

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

SKILL.md Common Commands: model type search uses wrong command and syntax

SKILL.md Common Commands: model create uses wrong @<type> prefix

swamp issue bug times out posting to the Lab while swamp-club.com returns HTTP 200

telemetry stats fatally fails to load an installed datastore extension (auto-resolve path); all other commands load it fine

tf plan: FETCH_BUNDLE PAGE_FETCH_ERR / NO_STATES on cleanup-only plan (no resource changes)

Add deleteResource to MethodContext and document dataRepository.delete in skills

Homebrew formula

Yank semantics inconsistent: all-versions-yanked acts as a free hidden/private extension; extension-level yank hard-blocks re-push

Extension search returns edit-distance noise for short queries ("asdl" → "AWS DEADLINE")

workflow resume holds the global lock across the resumed step, deadlocking any datastore op the step performs

Trajectory chart: current-day x-axis label is clipped at the right edge

Telemetry not synced to swamp-club: local queue accumulating ~3 days despite valid auth

extension pull serves a stale version that disagrees with search (honors a legacy per-extension serverUrl)

serve --webhook usage string makes <header> look optional for generic scheme

serve: webhook scheme not surfaced in startup event, health endpoint, or log line

Slack webhook pre-body gate only checks signature header, not timestamp

Dead code: verifySignature in webhook.ts superseded by verifier abstraction

extension source: install skills from source-path extensions

Data-driven webhook signature verifiers (avoid a code change + release per provider)

swamp.club extension view: multi-line code fence in manifest description renders each line as a separate inline code span

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