Hi! First off — thank you for shipping context.runModel() (#1022 / PR #1810). We audited both of our repos today and it dissolves a whole class of nested-CLI lock workarounds for us; we're already migrating our extensions onto it. Really lovely design, especially the fail-closed cross-extension authorization.

While reading the implementation to plan our migration, we noticed what looks like a small gap between the design doc and the shipped code, and thought you might want to know:

What the docs say — design/models.md (Output lineage section): "Nested invocations produce ModelOutput records with triggeredBy: \"model\", parentOutputId pointing to the caller's output, and callerExtension for provenance tracking."

What we observe at HEAD (fb93097, and in release 20260710.223351.0):

The schema support is all there: TriggerTypes includes "model", and parentOutputId / callerExtension exist as optional fields (src/domain/models/model_output.ts:50,79-80).
But the only ModelOutput write on the nested-invocation path hardcodes triggeredBy: "manual" and sets neither parentOutputId nor callerExtension (src/domain/models/method_execution_service.ts:844). Grepping the tree, nothing ever writes triggeredBy: "model" or assigns parentOutputId — the only writers are "manual" (direct + nested runs) and "workflow" (src/domain/workflows/execution_service.ts:786).
The in-memory nested_model_invocation method event does fire, so the provenance exists at runtime — it just doesn't reach the persisted record.

Why it matters for us (data, not pressure): we're converting an autonomous PR-fix pipeline where a parent method chains worktree + build + test + ship children; the persisted parent↔child link would let our audit artifacts and swamp summarise/output-search views distinguish "this ran because model X called it" from a manual run. Today a chained child is indistinguishable from someone running it by hand.

Might it be worth wiring the invocation context through to that ModelOutput.create call, or alternatively adjusting the design doc if persisted lineage is intentionally deferred? Totally your call on priority, of course — the feature is already a huge win for us as-is. Happy to test a build or provide more detail from our migration if useful. Thanks again!

02Bog Flow

Shipped

7/11/2026, 12:31:58 AM

Click a lifecycle step above to view its details.

03Sludge Pulse

stack72 assigned stack727/10/2026, 11:21:03 PM

stack72 commented 7/11/2026, 12:32:10 AM

Thanks @mgreten for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

mgreten commented 7/11/2026, 10:54:03 PM

Thank you for the quick fix! We updated to 20260711.221640.0 and re-tested against our real chain (adw-phase-runner → cli-agent via runModel, confirmed in-process). One small observation from that verification, in case it's useful: the provenance write itself looks right (method_execution_service.ts now pre-creates the parent output and builds child provenance from context._invocationProvenance), but in our run the child's ModelOutput record still wasn't persisted — the parent output exists, no child record appears.

From reading the release source (f8097a1), it looks like the write is gated on context.outputRepository, and both places that construct ModelInvocationService build commonDeps without an outputRepository: src/libswamp/models/run.ts:654-661 (CLI model-run path) and src/domain/workflows/execution_service.ts:534-540 (workflow path — which interestingly already has outputRepo destructured in scope just above). So the child context never receives a repository and the new provenance branch appears unreachable in practice.

Might passing the output repository through those two commonDeps close the loop? As before, no urgency from our side — and happy to re-verify a build against the same chain within minutes of a release. Thanks again for how quickly you turned the first fix around!

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`