swamp datastore setup filesystem is handled by a dedicated datastoreSetupFilesystem function that does a pure local-disk copy of <repo>/.swamp into the destination and returns filesPulled: 0 unconditionally. It constructs no provider and no sync service for either side, so when the repo is currently on a remote sync-based datastore (content in the backend + the ~/.swamp/repos/<repoId> cache, not under <repo>/.swamp), the content is never read and never relocated. The operation reports success with only the catalog moved.

The repo bootstrap may hydrate the source cache as a side effect (running a pullChanged against the outgoing datastore), but datastoreSetupFilesystem copies from <repo>/.swamp, not from that cache, so the hydrated content still is not transferred.

Nothing is lost — content remains in the outgoing backend and in the local cache — but the switch does not transfer it.

Repro

Set up a repo on a sync-capable remote datastore; populate it (push content so the remote holds N blobs).
swamp datastore setup filesystem.
Observe filesPulled: 0 and that the new filesystem datastore contains only catalog metadata, not the N content files.

Expected

Leaving a sync-capable datastore should relocate the content (from the hydrated cache / outgoing backend) into the new filesystem datastore — or at least refuse with a clear message and a documented manual procedure — rather than silently completing with a hardcoded filesPulled: 0.

Suggested direction

In datastoreSetupFilesystem, when the outgoing datastore is remote/sync-based, copy the hydrated working copy from the source cache (~/.swamp/repos/<repoId>) into the destination instead of (or in addition to) <repo>/.swamp, and report the real transferred count rather than a hardcoded 0. Alternatively, detect the sync-capable → filesystem transition and emit an actionable error pointing at the manual off-ramp.

Workaround

Manual: hydrate the cache with swamp datastore sync --pull, then cp -a ~/.swamp/repos/<repoId>/. <new-filesystem-datastore-path>/ after the switch, then verify before decommissioning the remote tables.

Discovered while

Building @shrug/rethinkdb-datastore (a sync-based remote datastore) and exercising the off-ramp path during test-drive. Draft write-up and workaround live in that package's docs/off-ramp.md.

02Bog Flow

Open

7/19/2026, 4:20:48 AM

No activity in this phase yet.

03Sludge Pulse

kneel commented 7/20/2026, 6:56:15 PM

Another repro path for the same root cause — and it's not limited to leaving a sync-based remote; it also bites filesystem → filesystem when you try to move an external filesystem datastore back into the repo.

Second repro (filesystem → filesystem, same-path collision)

Repo currently on a filesystem datastore at an external path (mine: /mnt/swamp/, same local xfs volume — not a remote backend). Has real content: namespaced data dirs, 684 KB catalog, 4 models visible via swamp model list.
swamp datastore setup filesystem --path <repo>/.swamp (to relocate back into the repo).
Every file errors: Failed to copy _catalog.db: Source and destination paths refer to the same file: copy '<repo>/.swamp/data/_catalog.db' -> '<repo>/.swamp/data/_catalog.db'. Same for _catalog.db-wal, _catalog.db-shm, audit/commands-*.jsonl.
Result: filesCopied: 0, bytesCopied: 0, directoriesMigrated: [], config rolls back to the external path. The actual external data at /mnt/swamp/ is never even touched as a source.

What this adds to #1271

Scope: the hardcoded-source bug isn't "sync-based remote → filesystem only." It's "any case where the outgoing datastore's real path isn't <repo>/.swamp." When outgoing is remote/sync-based, it silently copies an empty skeleton (this issue). When outgoing is a different filesystem path that happens to collide with the target, it hard-errors and rolls back. Both are the same defect: datastoreSetupFilesystem resolves the source from a hardcoded path instead of the current datastore's actual location.
Symptom axis: the existing repro produces a silent incomplete migration (config switches, content missing). This one produces a loud failure (config rolls back). The loud variant is arguably more recoverable for users because it self-blocks — but the silent variant is the scarier default because it looks like success.
Workaround (matches #1271's direction, adapted for filesystem): rsync -a --delete /mnt/swamp/<dir>/ <repo>/.swamp/<dir>/ for each subdir in datastore.directories, verify checksums, then swamp datastore setup filesystem --path <repo>/.swamp --skip-migration to flip config. Same shape as the existing workaround but no cache hydration step needed (content already on disk at the outgoing path).

swamp version hit: 20260716.194319.0-sha.df9fc306, Linux.

Bundled extension model cannot deserialize AWS SDK S3 XML that works in direct Deno

gcp/sheets spreadsheets-values: batch_get crashes with "Request with GET/HEAD method cannot have body"

Token creation API and UI scope selector for collective tokens (phase 4 of #960)

Make Cloudflare CRUD methods factory-aware so list-discovered resources can be managed in-place

Add @swamp/kubernetes/statefulset model type

serve: workflow.approvals and workflow.run.search still full-scan the workflow-run store after the #1284 data.query pushdown

Sync guard skips bound namespace directory during push — 0 files pushed after namespace migrate

Flaky #1052 preparePush test: mtime-granularity race on Linux tmpfs

command/shell renders JSON-object stdout lines as the literal string 'undefined'

Issue redactor treats the MongoDB authSource parameter as a secret, corrupting reproduction steps

namespace unset --migrate silently deletes artifact history via catalog-rebuild GC (~484k files lost)

Docs: document repo root resolution from subdirectories

Expose the swamp.club feed as an RSS feed

Email invitation is not linked to account created from invite URL

Add serve, datastore, vault, and worker wildcard scopes to token registry (phase 4 prep, #960)

datastore setup extension drops 'namespace' from --config, making extensions that require it impossible to configure

Docs: update manual to document --yes/-y as the standard confirmation-skip flag

Docs: update data.query and CEL expressions references for SQL pushdown

Docs: document collective token CLI usage in API key authentication pages

Add a --release-notes option to `swamp update` (or even make it the default)

Docs: manual should state workflow unknown keys are rejected and placement is step-only (follow-up to #1240)

Make GCP CRUD methods factory-aware so list-discovered resources can be managed in-place

serve: read ops (data.query, workflow.approvals, workflow run.search) linearly scan the whole datastore — ~350–600ms floor regardless of match count

Running "swamp workflow run ..." in a subdir of the swamp repo fails

Guide agents to inspect reports after failed model and workflow runs

serve: main JS thread holds ~40–70% of a core while idle (no clients, no runs, --no-schedule)

Search box collapses to near-zero width on mobile on the Extensions page

Extensions page: Search bar missing on mobile

spreadsheets-values: every method fails with 'Missing required path parameter: spreadsheetId' — implementation reads a global argument the schema does not declare

namespace migrate/set workflow broken for extension datastores: migrate skipped by sync guard, set not idempotent, migrate-index empties shards

ExtensionInfo.latestVersion typed 'string' but registry returns null; harden pull/resolve for prerelease-only extensions

workflow.run: relay a custom model method's output as method_output (command steps already do)

promptChoice infinite-loops on non-interactive stdin

gcp _lib: unconditional x-goog-user-project header causes USER_PROJECT_DENIED (403) for service accounts without the serviceUsageConsumer role

extension push: issue-verdict review is indistinguishable from missing/stale

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

Pushing an extension after creating a public git repo that is the same as other previously pushed extensions doesn't update the "Verified public repository"

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

Scaleway models: create methods should not require the resource ID they generate (ipId/gatewayId/serverId/...)

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

provisioner.provision fails with 'Cannot read properties of undefined (reading trim)' at method_execution_service.ts:852

method_execution_service.ts:852 crashes on undefined.trim() when writeResource receives undefined instance name

CLI support for collective API tokens (phase 3 of #960)

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

Scope enforcement and whoami introspection for collective tokens (phase 2 of #960)

fix(software-factory): DeclaredSchemaSchema.enum rejects boolean literals

Surface cloud-provider labels (scaleway, digitalocean, oracle/oci) as first-class search/filter facets on the Extensions page

Profile link in genesis subdirectory does not navigate back to main profile

Profile stats: per-user daily rollup table + MV in ClickHouse

Reconcile collective-token CLI activity to members (attribute → bonus → stamp → even-split)

Telemetry stats consumer: unsanitized subcommand in Mongo update path drops user metrics silently

Telemetry stats consumer: insert_id dedup commits before the write it guards — any upsert failure is silently swallowed on retry

Job-level labels: block is silently ignored, not rejected

Issue submission redactor silently corrupts report bodies

CLI telemetry: fold third-level verbs into subcommand + canonicalize aliases

Docs: update extension info reference to document extensions (type grafts) in content metadata

Docs: swamp skill repo-structure reference still documents repo-local .swamp/telemetry/ as live

Add safe adoption and lifecycle methods for existing Hetzner resources

Docs: update manual telemetry reference for user-global spool and telemetry.yaml opt-out

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

Add lookup support to the Cloudflare DNS records model

Expand token scope registry to full taxonomy (phase 1 addendum, #960)

Docs: document user-global telemetry (telemetry.yaml opt-out, spool location, telemetry stats behavior)

score_daily rollup strands stale grains when a day-less grant re-stamps onto a later day

swamp-club: global rate limiter runs pre-auth and collapses all direct clients into one per-IP bucket — 429s authenticated CLI traffic

Collective API token scopes: domain, persistence, and auth threading (phase 1 of #960)

Telemetry migration from ~/.swamp/telemetry should auto-detect home-as-repo

feed_post_score_events queue grows unboundedly (no TTL, no delete-on-delivery)

Issue-filing skill should require ownership classification before submitting a bug

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

@-mention autocomplete for users when writing lab ripples

Remove comments from /feed and redesign the page

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

Score-refresh consumer: harden coalescing against a diverse backlog (bistability)

Remove feed comments — consolidate discussion in Discord

Add a 'my collective extensions' filter to extensions page

Relax the profanity filter

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

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

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

Grant revoke is never applied to the running server — under `--grant-reload auto` and `manual` alike, a revoked grant stays in force until an explicit `access reload`