swamp data prune (from #1009) reclaims data whose owning model definition no longer exists. Retyping a model instance produces a different orphan that falls through it: the definition still exists, so the rows look owned, but .swamp/data is keyed by <collective>/<type>/<uuid> — so changing the instance's type: strands both its data tree and its catalog rows under the old type_normalized.

Those rows are reachable by no management command, while remaining fully visible to data query, which is the one read path workflows actually use.

Reproduction

Have a model instance with data, e.g. type @ourcollective/old-type, name story-analyzer.
Change its type: to another type — for us @twonines/redmine-story-status, same uuid, after adopting a published extension in place of a local one.
Write new data, so a live tree exists alongside the stranded one.
Try to reclaim the old rows.

Command	What happens to the stranded rows	Why
`swamp data prune`	ignores them	it matches on `model_id`, which a retype does not change, so the rows look owned by a live definition
`swamp data delete <model> <name>`	`No data named "<name>" exists for model story-analyzer`	resolves the model name to its current type, so it never looks under the old `type_normalized`
`swamp data list <model>`	hides them	also resolves by current type
`swamp doctor extensions`	`overallStatus: pass`, `orphanFiles: []`	orphan detection covers extension files, not catalog rows
`swamp data query '<cel>'`	returns them	matches on tags (`modelName`, `specName`), which the stranded rows still carry

We hit this with 380 rows across two retyped instances (335 + 45). After deleting the stranded files by hand, data query 'modelName == "story-analyzer"' still answered with all six data names as isLatest: true and content: {}.

Why it is more than cosmetic

Two rows shared a name — the stranded one at v27 and the live one at v1 — and both reported isLatest: true, with the stale one sorting first. So:

data.query('modelName == "story-analyzer" && specName == "analysis"')[0]

selects the dangling row, with empty content, in preference to live data. Our workflow escaped this only because all twelve of its queries also pin workflowRunId == run.id — pinning we had added for an unrelated reason. Anything using the documented [0] shape without a run pin silently reads the wrong row after a retype.

The only cleanup available

Hand-editing the catalog, which is exactly what a datastore command should exist for:

sqlite3 .swamp/data/_catalog.db "PRAGMA wal_checkpoint(TRUNCATE);"
sqlite3 .swamp/data/_catalog.db ".backup '<somewhere safe>/_catalog.db.bak'"
sqlite3 .swamp/data/_catalog.db "DELETE FROM catalog WHERE type_normalized LIKE '@ourcollective/%'; VACUUM;"

Afterwards: catalog 1090 -> 710 rows, integrity_check ok, .swamp/data 68 MB -> 35 MB, data query returning only live rows with content, doctor extensions pass, workflow validate passed, 29 tests green.

Suggested fix

Have prune match on (namespace, type_normalized, model_id) against the registered definition rather than model_id alone, so a retype makes the old rows reclaimable through the command that already exists for this. This is the direct extension of #1009 to the retype case.
Failing that — or in addition — data query should not return rows whose backing file is absent. A row that answers isLatest: true with content: {} is worse than a missing row, because it wins a [0] selection. This half matters even with fix 1, since the window between retype and prune is unbounded.

A --dry-run on whatever form this takes would be welcome, as #1009 suggested.

Environment

swamp 20260809.004828.0-sha.b61c9de2, Deno 2.8.3, Linux x86_64
Filesystem datastore, single namespace, catalog schema as shipped
Follow-up to #1009 (orphaned data from a removed/migrated model — shipped); the retype path is the case its fix does not reach

02Bog Flow

Open

8/19/2026, 9:07:27 PM

No activity in this phase yet.

03Sludge Pulse

vault: audit trail should record put, delete, and annotate operations

ExtensionWorkflowRepository scans manifest.yaml as a workflow, emitting 'Unknown key manifestVersion' warning

--max-run-duration only applies to detached runs, not attached runs

dataOutputOverrides not applied during remote execution — ephemeral resources GC'd before override takes effect

Cancel endpoint reports status: cancelled for runs it did not actually cancel

@swamp/git: no way to amend a commit, but push can --force

Installation with new account creation times out

pre-flight checks run on orchestrator, not on worker — breaks remote execution with filesystem-dependent checks

Docs: update cancel endpoint response statuses in REST API reference and workflows page

serve: triggerSource not persisted to workflow run summary

docs: document --remote-only flag for swamp serve

Swamp serve daemon doesn't run with --hot-reload

serve: include workflowName in HealthSnapshotSchedule

Retyping a model instance strands catalog rows no command can reclaim — prune matches on model_id, delete resolves the current type (follow-up to #1009)

extension rm also deletes the lockfile entry, and install on an empty lockfile is a silent success — rm/install is not a round trip

knowledge-base retrieve persists query output into the state resource, with lifetime infinite and the query text in the instance name

Method-name collision between a base model type and an extending extension silently drops the whole extension file — no error, doctor reports pass

Skip 50MB monolithic index rewrite on v2 shard-first path

Share single AwsS3Client instance across lock, sync, and verifier

Double shard assembly per command lifecycle (pull + push both read all shards)

pullChanged never records commitSeq for shard-first (v2) index

localHasAllRemoteEntries() permanently blocks sidecar update on partial caches

serve: workflow.history.get cannot find CLI-created runs or look up by run ID

"TRIAL ENDED" modal shown to team plan user when toggling extension visibility

Concurrent suspended workflow runs can't be disambiguated from 'approvals'; fresh runs should supersede matching-input suspended runs

I _think_ I might like a guard in the trigger yaml

swamp cmds don't realise the user is sshed into the system

serve dashboard: add cluster.instances and serve.config endpoints

CEL expressions have timestamp/duration but no current-time value, so no guard can express "older than N"

Support direct type execution (@type) with --server

access token mint writes to user vault, not serve's _token-secrets control plane in HA mode

Generic OTLP endpoint appends signal path after query or fragment

Issue lifecycle start drops top-level issue comments

serve dashboard: add instanceId, triggerSource, and step progress to WorkflowRunSummary

Document worker affinity (affinity: true) for workflows and jobs

Datastore MongoDB driver leaks connections — 5960 accumulated over 8 days

workflow approvals displays the latest run's prompt for every suspended run

@swamp/git: add a read-only working-tree diff for pre-commit review

docs: document --oauth-client-name flag for swamp serve

Docs: update workflow reference to include trigger in JSON output shapes

@swamp/git branch and push methods fail data naming when branch contains '/'

Docs: update workflow-placement.md for job/workflow-level placement inheritance

feat(serve): use identifiable OAuth client_name instead of random UUID

@swamp/git does not pass AbortSignal to Git subprocesses

Global Secret Manager methods build an invalid regional parent

Document model.method() support in assert expressions

No way to store code-review results — verdicts, findings, and cost are not persisted for any repo

Redaction regex boundary bug: label_base64 secrets with an unrecognized label pass through unredacted (e.g. swamp_ API keys)

User token page (/u/<user>) shows only "swamp_..." for every API key, making leaked-key identification impossible

upstream_state treats sparse-fetch branches as having no upstream

Add native support for the Pi coding harness

Cloud Build create supplies project instead of required projectId path parameter

workflows: support labels/target/platform at job and workflow level

swamp access grant create never registers the grant — a --deny created this way silently fails open

Support credentials in datastore config (vault-resolvable)

swamp serve OOMs on repos with 2000+ model definitions

Serve telemetry attribution for collectives

Extension workflows: no way to override trigger configuration

Add a list/discover method to the generated @swamp/aws types — no way to enumerate resources in a region

Document @vault= prefix for webhook secrets in serve.yaml

swamp access grant create installs an unrelated extension from the registry

docs: document SWAMP_API_KEY headless OAuth bootstrap for swamp serve

workflow-succeeded selects the globally-latest run, so siblings block each other under parallel use

swamp serve: webhook secrets should support @vault= resolution

Misleading collective_not_trusted auto-resolve error when a local source extension transiently fails to index during workflow validate

datastore setup: symlinks not counted in bytesCopied, causing misleading '(0B)' output

vault.get() CEL error embeds raw newline when wrapped by model resolver, producing broken output

Feature: user-configurable redaction rules (.swamp/redaction.yaml)

Fatal JavaScript out of memory: Ineffective mark-compacts near heap limit

Sync every signup to Attio, and backfill the existing population (#809 follow-up)

@swamp/issue-lifecycle probes /api/health, which swamp-club stopped serving when the Fresh scaffold stubs were removed

Lab lifecycle POST rejects any payload string that starts with a dollar sign, not just operator keys

Feed: detect and gracefully handle dead (404) post links (link rot)

/feed: per-post unread indicators and mark-as-read to track reading progress

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

Add a :micdrop: emoji / reaction shortcode (swamp-native art included)

Push down the two cheap leaderboard scans: ghost-gate dictionary and eventCounts owner filter

$identify events are never consumed — anonymous web history never binds to the account

Finish the swamp_* attribute set on Attio users, and settle the two unprefixed ones (#809 follow-up)

aria-expanded is a raw boolean in 12 places — collapsed state is unannounced to screen readers