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

Part of epic #847. Sibling of #853 (Unit 1 — land the local ClickHouse foundation). This issue tracks the prod changes that #853 deliberately does not make.

Problem

Prod ClickHouse (giga-swamp models/@giga-swamp/k8s-manifest/clickhouse.yaml) couples the serving engine to S3 in a way that isn't paying off at our scale, and leaves the schema un-migratable:

1. S3-coupled storage (storage_policy = 's3_main'). CH's own MergeTree parts live in a DO Space (clickhouse-data-swamp-club), fusing two concerns that should be independent failure domains:

serving — hot, latency-sensitive, disposable
durable log — the ndjson archive (events-archive-swamp-club), the real system of record

Consequences: an S3 hiccup degrades queries, not just ingestion; the MergeTree merge engine pays continuous S3 request/egress cost (GET/PUT/DELETE on every merge, insert, and TTL drop — forever, proportional to ingest, independent of query load), plus range-GETs on every cache miss; and it obscures the real DR story ("CH rebuilds from S3" means replaying the ndjson archive, not the s3_disk parts). The dataset is small (~4M LowCardinality rows, a few hundred MB compressed) and TTL-capped at 2 years, so the auto-tiering benefit an s3 storage policy exists for never triggers. The retained PVC + the archive already provide durability — the s3 storage policy is pure tax. S3 should be break-glass only: append one PUT/batch to the archive, read it back solely on a rare rebuild.

2. Schema is a one-shot ConfigMap with no migration path. The init schema is a ConfigMap (clickhouse-init-schema) mounted at /docker-entrypoint-initdb.d, which ClickHouse runs only on an empty data dir. With the retained clickhouse-data PVC, the data dir is non-empty after first boot, so editing the ConfigMap does not re-apply to the running pod. It looks like GitOps-managed schema but is a one-time bootstrap. Epic #847 Units 4–5 (score_grants + materialized views) add DDL that must land in prod, and there is currently no tracked mechanism to apply it. Related: CH MATERIALIZED columns compute at INSERT time only and never backfill, so new dimensions over history require re-ingesting raw properties from the archive.

(Also: the manifest's top comment still claims "emptyDir, no PVC, schema runs on every restart" — stale and contradictory with the shipped retained-PVC spec.)

Proposed solution

Drop storage_policy = 's3_main' — serve from a plain local-disk MergeTree on the existing retained clickhouse-data PVC. Remove the now-unused s3-storage.xml fragment / clickhouse-s3-config ConfigMap / clickhouse-s3-creds env wiring if nothing else needs them. DR path becomes: lose the volume → replay from the events-archive-swamp-club ndjson lake (backfill.sql).
Establish a real DDL migration path so Units 4–5 can ship schema changes to a running prod CH (the ConfigMap edit won't): e.g. a versioned-migration Job applied on deploy, or an idempotent CREATE/ALTER … IF NOT EXISTS apply step that runs against the live server instead of relying on initdb-on-empty-dir. Include a backfill story for new MATERIALIZED columns (re-ingest from the archive).
Fix the stale "emptyDir / no PVC" comment in the manifest.

Alternatives considered

Keep s3_main as a cold tier — only worth it if the dataset outgrows local-disk economics; at current scale + 2-year TTL it won't for years, and you'd still need the archive for DR, so it's redundant.
Bundle this into #853 — rejected. #853 is the local-dev foundation (acceptance criteria are all local), lives in swamp-club2, and prod CH already runs. This is a different repo (giga-swamp) and a different blast radius.

Acceptance

Prod CH serves from local disk; storage_policy = 's3_main' and the S3 disk config are gone (or justified if retained).
A repeatable, idempotent mechanism applies schema/DDL changes to a running prod CH (verified by applying a no-op/additive change).
DR is documented as archive-replay; S3 touched only on append + rebuild.
Stale manifest comment corrected.

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