#2601 Run-scoped data get/list return the latest version, not the version the run produced

Problem

Resolving data through a workflow run returns the latest version of each data item, not the version that run produced. When the recorded artifact no longer matches by id, it can return a same-named item from a different model.

Affected:

• swamp data get <name> --workflow <wf> --run <runId> (and data.get over swamp serve with workflowName + runId)
• swamp data list --workflow <wf> --run <runId>

Cause

WorkflowDataService.findAllForWorkflowRun (src/domain/data/workflow_data_service.ts:62):

1. Loads dataRepo.findAllGlobal(), which holds only the latest version of every data name.
2. Matches each run artifact ref ({dataId, name, version, tags}) by dataId. The comment there notes data ids change per version, so refs from older runs miss.
3. Falls back to the first global item with the same name across any model (lines 131-140).
4. findByNameInWorkflowRun compares an explicit version against that latest item, so asking for the run's actual (older) version returns not_found even when it is still on disk.

The version the run recorded (DataArtifactRef.version) is never used for resolution.

Reproduction

1. A workflow whose step writes data result (or a workflow-scope report report-<name>).
2. Run it twice: run A writes v1, run B writes v2.
3. swamp data get result --workflow <wf> --run <runA> returns v2 (run B's content).
4. swamp data get result --workflow <wf> --run <runA> --version 1 returns not_found.

Expected

Run-scoped resolution returns the exact version recorded on the run:

• Workflow-scope artifacts (run.workflowDataArtifacts) resolve under model type workflow / the run's workflow id at the recorded version.
• Step artifacts use the existing lookup only to identify the owning model, then read that owner's data at the recorded version.
• An explicit version selects that version of the run's artifact.
• A recorded version that has been garbage-collected yields not_found. It must never fall back to newer data or to another model's data.

Impact

Silent wrong content: a link or script that targets a specific run sees a later run's output. This blocks swamp-club#2595 (dashboard deep links to a run's reports), which relies on run-scoped data.get being pinned.

Only two callers are affected: src/libswamp/data/get.ts:244 and src/libswamp/data/list.ts:228. Output without --run (latest run) is normally unchanged.