#521 Workflow engine resolves extension methods against base type, ignoring extension-registered methods

Summary

When a workflow step calls a method provided by a local extension (not the base type), the workflow engine intermittently resolves the method against the base type only — reporting "Unknown method" — even though the same method works when called directly via swamp model method run. This indicates a race condition between bundle registration/loading and workflow method validation.

Environment

• swamp version: 20260530.005533.0-sha.1c117111
• OS: Linux (WSL2)
• Base type: @webframp/gitlab (6 original methods)
• Extension: local model extending the base type with ~45 additional methods

Steps to Reproduce

1. Extend a base type with additional methods via export const extension in extensions/models/.
2. Create a workflow YAML that calls one of the extension methods.
3. Run the workflow. It will succeed sometimes, fail other times.
4. Under concurrent load (multiple workflows + model method calls in parallel), the failure rate increases.

Observed Behavior

ERR workflow·run·daily-summary·overview·list-todos Step failed:
  "Unknown method 'list_todos' for type '@webframp/gitlab'.
   Available methods: list_projects, get_project_info, list_merge_requests,
                      list_issues, list_releases, list_pipelines"

The base type has exactly 6 methods. The extension adds ~45 more (including list_todos, list_groups, list_runners, etc.).

When the same methods are called directly:

swamp model method run <model> list_todos state=pending

They always succeed — even during the same concurrent stress test.

The error occurs:

• Intermittently across all workflow types
• Across independent workflow runs
• Throughout a 70-minute parallel stress test across 3 concurrent workflow subagents
• Never when calling methods directly via swamp model method run

The swamp summarise command also reports these as last errors, confirming persistence.

Impact

• Workflows that depend on extension methods are unreliable — they randomly fail
• No feedback on why the extension wasnt loaded (no bundle loading error, just "unknown method")
• Forces users to either only use base type methods in workflows or accept random workflow failures

Root Cause Hypothesis

The workflow engine evaluates methods against the base type definition (the type as published in the registry), which knows about only the base methods. The extensions methods are registered at bundle time but the workflow engine reads the cached type definition before the extension bundle is loaded.

Direct model method calls always work because they resolve at execution time against the loaded extension bundle, not the cached type definition.

Suggested Fix

• Workflow method validation should use the same method resolution path as swamp model method run at execution time
• Or eagerly resolve extension bundles before workflow validation
• Or add retry logic in the workflow engine if a method is not found on first lookup