#3887 A workflow step's method output is invisible to `data query` and `data list`, and the method summary's retrieval command returns an older run's data

Swamp 20261020.024627.0-sha.26dc044f, macOS, workspace from swamp repo init --tool none, @swamp/git 2026.09.28.1.

Repro, on a scratch git repository with one commit "one":

1. swamp behavior run scratch log twice: data list scratch shows log v1 then v2 (a new version even when the content is identical).
2. Commit "two", run a one-step workflow whose step is scratch.log: the run succeeds and its JSON lists a log data artifact with a new dataId at version 1, tagged source: step-output and the run's workflowRunId.
3. swamp data list scratch still shows log v2, and swamp data query 'modelName == "scratch" && name == "log"' --select content returns the direct run's commits, without "two".
4. No query finds the step outputs at all: tags.workflowRunId == "<run id>", tags.source == "step-output" and tags.workflow == "<workflow>" each return 0, and version >= 0 && name == "log" returns only the direct runs' versions. A second workspace with five runs of a four-step workflow shows the same: 20 step outputs, none in any query.
5. The step's @swamp/method-summary says it produced log version 1 and prints the retrieval command swamp data query 'modelName == "scratch" && name == "log" && version == 1' --select content, which returns the first direct run's data, commit "one" only.

Inside the workflow the data is right: an assert step reading data.latest("scratch", "log") after the log step sees the new commit, and fails with the new commit's message when it expects a different one.

Expected: a workflow step's output is the behavior's next version of log, or at least findable by the run id the summary names, and the summary's retrieval command returns the data the step produced.