Follow-up to #869 (marked shipped, but this still reproduces — I added a fresh repro as a comment there: https://swamp-club.com/lab/869). Filing a distinct, open bug for the specific unresolved path: swamp extension update does not migrate an existing model instance to the new typeVersion, so methods/reports shipped in the new version never become available on that instance.

Description

Methods are resolved from the compiled bundle keyed by the instance typeVersion. swamp extension update advances the extension (pulled code + lockfile) but leaves existing instances pinned at their creation version, and there is no swamp model upgrade. Consequence: a newly-shipped method is Unknown and report/bundle resolution keeps using the old version's code, on any pre-existing instance.

Steps to reproduce (clean; no force-pull, no S3)

Instance ingest of @vcjdeboer/session-ingest created at typeVersion 2026.07.12.1.
Publish 2026.07.15.2, adding a new method status (with an upgrades[] identity entry).
swamp extension update @vcjdeboer/session-ingest → real update reported: v2026.07.15.1 -> v2026.07.15.2, "1 updated".
swamp model get ingest still shows typeVersion: 2026.07.12.1; swamp model method run ingest status → Unknown method 'status'.
Bump the definition file typeVersion to .15.2 + swamp model evaluate ingest: evaluated definition now reads .15.2, but status is still Unknown and the instance is still .12.1.
swamp doctor extensions only lists (... @2026.07.15.2 [pulled] 2 source(s)); no recompile/rebuild in this build.

Expected

A non-destructive way to advance an existing instance's typeVersion (e.g. swamp model upgrade <name>, or extension update migrating instances via the upgrades[] chain) so new methods/reports load without delete+recreate (which loses the instance).

Workaround

Only two, both poor: delete + recreate the model (loses the instance/state), or hand-overwrite the specific cached bundle .js under .swamp/report-bundles/<hash>/ (fragile; breaks on cache clear).

Corroborating signal

Unrelated user models fail to load on every run with Last upgrade toVersion X does not match model version Y (@alvagante/content-blog-post, @magistr/obsidian/vault) — same model-versioning-mismatch family.

Environment

swamp 20260711.205210.0-sha.c8b5c983; macOS (darwin 25.2.0); local repo; extension @vcjdeboer/session-ingest (locally developed, installed/lockfile at .15.2, instance frozen at .12.1).

02Bog Flow

Closed

7/17/2026, 3:34:59 PM

No activity in this phase yet.

03Sludge Pulse

vcjdeboer commented 7/15/2026, 8:35:08 PM

Confirmed: still reproduces after swamp update to the latest build 20260715.175955.0-sha.4d2897c1 (was 20260711.205210.0-sha.c8b5c983). On the new binary the full ladder was tried and none migrate the existing instance:

swamp extension update @vcjdeboer/session-ingest → no-op ("already up to date v2026.07.15.2")
swamp model evaluate ingest → rewrites the evaluated definition only
swamp repo upgrade → updates repo settings/skills only

Instance remains typeVersion: 2026.07.12.1; swamp model method run ingest status still returns Unknown method 'status'. So the instance-migration gap is not addressed in 20260715.

stack72 commented 7/17/2026, 3:34:42 PM

Thanks for the detailed repro @vcjdeboer — this helped us track down what's happening.

There are two separate things going on here, and only one of them is a bug.

What we fixed in https://github.com/swamp-club/swamp/pull/1882

The "Unknown method" problem after extension update is caused by local source shadowing. When you have an extension both locally developed (source in a local models dir or .swamp-sources.yaml mount) and installed via the lockfile, resolveOriginConflicts silently clears the pulled entry's type in favor of the local source. So after swamp extension update pulls the new version, the local (old) source still wins — new methods aren't visible, and you get no feedback about why.

swamp extension update now warns when this happens, showing which types are shadowed and which local source is winning. The fix is to update your local source or remove it so the pulled version takes effect.

What's by design (for now)

The typeVersion on the model instance not advancing after extension update is intentional — extension update and model upgrade are separate concerns. extension update pulls new extension code. Model upgrade (advancing the instance's typeVersion and running upgradeAttributes on globalArguments) is opt-in and currently triggers as a side effect when you next run a method via swamp model method run, provided the extension model has an upgrades[] stanza.

There's no standalone swamp model upgrade command today. We may add one in the future, but it's not blocking method availability — new methods load from the model type registry regardless of the instance's stored typeVersion. The typeVersion field only controls the upgradeAttributes migration chain for globalArguments. There is work planned for this soon(ish)

The "corroborating signal"

The Last upgrade toVersion x does not match model version y errors from other users (@alvagante/content-blog-post, @magistr/obsidian/vault) are a different issue — that's a validation failure where the extension author's upgrades[] stanza doesn't match their model version field. Those models fail to register entirely. We can track that separately if it's still reproducing.

vcjdeboer commented 7/17/2026, 3:47:20 PM

Confirmed resolved on this machine following your guidance — swamp 20260717.145236.0-sha.d0b3b256. Root cause was exactly local source shadowing. A few details that may be useful:

It was TWO shadows, per source-kind — and fixing one leaves a confusing half-working state. The suite is split (published + lockfile) but this repo also keeps pre-split local copies. There were two stale .12.1 shadows of @vcjdeboer/session-ingest:

extensions/models/ (the default local models dir) shadowed the methods → the newly-published status method was Unknown method.
extensions/reports/ (the local reports dir) separately shadowed the report → @vcjdeboer/capture-report kept rendering the wrong session.

Updating only extensions/models/ made status resolve correctly — but capture-report still ran the stale code from extensions/reports/. So a user can fix the models shadow, watch methods start working, and be baffled that a report (or other source-kind) is still stale. What fully worked: sync both local source dirs to the published version, then rm -rf .swamp/report-bundles/<hash> to force a recompile. Methods + report then both correct.

On the #1882 warning: I didn't see it fire here — swamp extension update @vcjdeboer/session-ingest printed "already up to date (v2026.07.15.2)" and no-op'd, because I'd pull --forceed the new version into the lockfile earlier, so update had nothing to pull. The shadow warning seems tied to an actual pull; when the lockfile is already current but a stale local source shadows it, extension update stays silent. A shadow check that also runs on the "already up to date" path (or in swamp doctor) would catch that variant.

Confirming your typeVersion point: the instance is still typeVersion 2026.07.12.1 and never advanced, yet every method incl. the new status is now available — so "methods load from the type registry regardless of the stored typeVersion" holds exactly here. 👍

Unrelated FYI (separate, not asking you to chase it): on this build swamp data query / swamp data list return 0 rows for models that demonstrably have data (swamp data get still works) — it surfaced as "0 local" in the new status output. Happy to open a clean repro if that's useful; otherwise ignore.

Thanks for the quick turnaround on #1882.

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`