$lambda function call stack bug

There's a little bug with $lambda.

It happens only in a complicated situation so most people probably haven't experienced this yet, but it's important regardless.

Basically happens when a function C triggers function B, which triggers function A. The return value of function A needs to propagate all the way back to function C when using `$return.success`, but that's not how it's working right now.

```
{
"C": {
"trigger": "B",
"success": {
"type": "$render"
}
},
"B": {
"trigger": "A",
"success": {
"type": "$return.success",
"options": "{{$jason}}"
}
},
"A": {
"type": "$network.request",
"options": {
...
},
"success": {
"type": "$return.success",
"options": "{{$jason}}"
}
}
}
```

The issue provides a three-step C → B → A `$lambda` example; start by tracing the `$return.success` entry point and its call-stack handling. Verify that A's network result reaches C's success handler through B, using a regression case for the shown chain.

Written by the indexing model from the issue text.