#2455 self.globalArguments.X returns the unevaluated expression text when the global argument is itself an expression

Description

When a global argument is itself a CEL expression, referencing it from a method argument with self.globalArguments.<field> yields the global argument's unevaluated ${{ ... }} text, not its evaluated value, even when that expression is valid. The literal text is then handed to the method.

Found while planning swamp-club#2397.

Steps to Reproduce

1. command/shell model producer with run: echo hello, run it once.
2. command/shell model globalvalid:
   • globalArguments.target: ${{ data.latest('producer', 'log').name }}
   • method execute, argument run: echo "[${{ self.globalArguments.target }}]"
3. swamp model method run globalvalid execute
4. Output: /bin/sh: [${{ data.latest('producer', 'log').name }}]: bad substitution, then Command exited with code 1. Expected: [log].

Cause (suspected)

ExpressionEvaluationService.evaluateDefinition (src/domain/expressions/expression_evaluation_service.ts) sets ctx.self.globalArguments from the original, unevaluated definition.globalArguments and evaluates every expression in the definition in a single pass. So self.globalArguments.X resolves to the raw expression string. The workflow path (src/domain/workflows/execution_service.ts, where ctx.expressionContext.self is built from originalDefinition.globalArguments before DefinitionExpressionEvaluator.evaluate) has the same shape. Literal global arguments work; only expression-valued ones are affected.

Expected Behavior

self.globalArguments.X resolves to the evaluated value of the global argument, as the swamp skill's expression reference documents (.claude/skills/swamp/references/model/references/expressions.md, examples.md).

Environment

• swamp 20260923.203315.0-sha.4ae1cfd9
• macOS