Lab: Show data retrieval commands after workflow run completes

Problem

After a workflow run completes, the output ends with just Workflow "succeeded" and no guidance on how to access the data that was produced. Users have to know to run swamp data list and swamp data get commands to find and retrieve the output, which requires discovering the right data names and flags on their own.

For example, after running swamp workflow run contributor-analysis, the output shows individual "Data saved to" paths during execution but ends abruptly at "Workflow succeeded". To actually see the results, users must:

Run swamp data list --workflow contributor-analysis to discover what data was produced
Run swamp data get --workflow contributor-analysis <data-name> for each piece of data

This is a poor experience, especially for new users who don't know the data commands exist.

Proposed Solution

After a successful workflow run, append example swamp commands to the output so users can immediately access their data. The output should look something like:

19:54:10.057   info    workflow·run·contributor-analysis Workflow "succeeded"

To view the data produced by this workflow:

  swamp data list --workflow contributor-analysis
  swamp data get --workflow contributor-analysis report
  swamp data get --workflow contributor-analysis summary

The implementation should:

List the specific data names produced by the run (from the step data artifacts tracked in the WorkflowRun)
Show concrete, copy-pasteable commands tailored to the workflow that just ran
Only appear in log output mode (not JSON mode, which is for machine consumption)
Be skipped for failed runs where no useful data was produced

Implementation Summary

This feature affects the workflow run output layer. Changes would be needed in:

src/presentation/output/log_progress_callback.ts — the onWorkflowComplete callback to emit the helper commands after the "Workflow succeeded" message
src/presentation/output/workflow_run_output.ts — the log-mode render path may need to emit the commands based on data artifacts collected in the WorkflowRun

The data artifact names are already tracked in StepRun.dataArtifacts during execution, so no changes to the execution layer should be needed — this is purely a presentation concern.

Alternatives Considered

Always show full data inline: Too verbose for large outputs and breaks the streaming log format
Only show swamp data list command: Less helpful than showing the specific data get commands for each output
Show file paths instead of commands: Users already see raw paths in the "Data saved to" lines during execution; commands are more actionable

yep yep yep

Support named argument syntax for model method run (e.g. --arg key=value)

env var overrides for globalArguments silently change which environment a model targets

deno lint no-import-prefix conflicts with swamp's required npm:/jsr: inline specifiers

AI agents should search community extensions before offering to create custom models

feat: add --content-type filter to extension search

Add a 'reports' feature

Port remaining CLI commands to libswamp + renderer pattern

Persistent runner / server mode to eliminate per-invocation CLI startup overhead

AI agent should prefer fan-out model methods over shell loops for fleet operations

Support unbundled helper scripts in extension packages

Add progress indicator for long-running model methods

Built-in structured output parser for CLI commands

Automatic trace context propagation across workflow steps

Native OpenTelemetry tracing for swamp CLI internals

Claude Code should prefer extending swamp extensions over using external CLI tools

Framework log lines written to stdout pollute model method output

Swamp skill should guide AI agents to create extension models instead of inline shell scripts

Shared team collectives for collaborative extension publishing

Delete methods should return last known state data

Add smoke-test skill for extension models

Workflow run output is unreadable — resource data and errors are buried in log noise

Recommend or manage lockfile strategy for extension model npm dependencies

Output of running a method is not the actual output

Add macOS Keychain vault type

bug: Vault secret shell escaping incomplete — $(), semicolons, and pipes are interpreted

Swamp should support "Scheduled"-type status for execution

feat: add support for Nix via a flake

ModelType.normalize replaces all dots with slashes, corrupting dotted type names

fix: collective validator error message omits drivers and datastores

Skill docs: document configSchema inline requirement and .describe() constraints for vault extensions

It takes 42 seconds to run swamp --help

After today upgrade

Auto-resolver fails when extensions/models/ directory does not exist for vault-only extensions

Azure Key Vault extension vault bundle fails to load in compiled binary

RangeError: Maximum call stack size exceeded when loading extension models with npm dependencies after upgrade to 20260317

Extension Zod schema incompatibility after upgrade to 20260312

Data garbage collection never fully removes expired data from disk

extension push --dry-run requires authentication unnecessarily

Typed context APIs to eliminate no-explicit-any in extension models

AWS extensions fail to load: missing _lib/aws.ts shared dependency

getContent() should resolve vault expressions for sensitive fields

getContent() should return parsed objects, not raw Uint8Array

Add context.readResource() to MethodContext for user extension models

Datastore lock: allow concurrent reads across different models

extension install should be an alias of extension pull

feat: Execution Driver Abstraction — Pluggable Isolation for Model Execution

Support --global-arg on model create

consider a libswamp

Running workflow should not block read-only operations

Update from 20260227 to 20260311 breaks existing model definitions (symlink + path-based type)

loadUserModels ignores --repo-dir, uses cwd instead

datastore lock release --force deadlocks on the stale lock it's trying to release

Datastore lock not released when interactive command fails in non-TTY context

vault put to 1Password stores empty password field

Leaderboard shows 0-event users whose profiles 404

Move AWS, Azure, and 1Password vault providers to extensions

Data instance name uniqueness is global across specs instead of per-spec

Audit timeline misses today's entries in UTC+ timezones

AI agent discoverability: reduce trial-and-error for CLI syntax

GlobalArguments CEL expressions fail when factory inputs are omitted — selective evaluation not working

Document factory pattern for model reuse in skills

Delete method uses identifier as data name instead of instance name

CLI method run ignores required arguments without .default()

Workflow run output mixes data, errors, and logs without clear separation — hard to find what actually executed

data.latest() in workflow step inputs resolved at workflow start, not at step execution time

Update method fails when globalArguments contain cross-model CEL expressions

Track resource deletion in local data model

fix: extension npm packages fail to resolve in compiled binary

swamp repo upgrade replaces entire CLAUDE.md with generic template instead of merging

Add drift detection to reconcile stored state against live cloud resources

Model inputs schema validated on all methods — delete fails requiring create-time inputs

Support wait-until-ready semantics for async resource provisioning

support pushing to organizations

Add data rename/move command for non-destructive refactoring

Schema mismatch warnings lack model context and misrepresent API response shapes

Support pre-flight validate method on models before method execution

Extension models need built-in support for idempotent create operations

Workflow reports succeeded when step outputs indicate failure

Swamp skills don't prevent AI agents from manually generating UUIDs for workflows