#2572 data.latest/data.findBySpec/data.query cannot see data from pulled extension model types in workflow expressions

Summary

data.latest(), data.findBySpec(), and data.query() all fail to find data produced by models of type @evardjp/github-local-mirror when used in workflow step input expressions. The same queries work fine via swamp data get and swamp data query CLI commands.

Repro

1. Create a model of type @evardjp/github-local-mirror:

   swamp model create @evardjp/github-local-mirror test-mirror      --global-arg owner=X --global-arg repo=Y      --global-arg gitObjectPath=/tmp/test.git      --global-arg workspaceRoot=/tmp/worktrees      --global-arg artifactRoot=/tmp/artifacts

2. Run sync — data is produced with specName: syncRunSummary etc.

3. In a workflow step input, reference:

   inputs:
     path: ${{ data.latest("test-mirror", "syncRunSummary").attributes.anything }}

4. Expression fails: data.latest("test-mirror", "syncRunSummary") found no data record

What works

• swamp data get test-mirror sync-<timestamp> — CLI finds data
• swamp data query "modelName == 'test-mirror'" — CLI query works
• data.latest("code-workspace", "workspace") — works for @shelson/git-workspace models in same expression context
• data.latest("clean-code", "review-latest") — works for @swamp/clean-code-review models

What doesn't work

• data.latest("test-mirror", "<anySpec>") — never finds data
• data.findBySpec("test-mirror", "worktreeSnapshot") — never finds data
• data.query("modelName == 'test-mirror'") — never finds data

All three work for the same model+spec when called from CLI.

Impact

Cross-step data chaining is impossible for @evardjp/github-local-mirror models. Workaround is vault-bridging via command/shell steps.

Workaround

Use command/shell model to find data on disk and write to vault, then read from vault in downstream steps via vault.get().