`respect` doesn't resolve `$outputs.<name>` references

[sww-at-work]

Describe the bug

respect doesn't resolve $outputs.<name> references in arazzo workflows.

To Reproduce

1. have a workflow or step produce an output called accessToken.
2. in a subsequent step reference $outputs.accessToken (e.g. Authorization header)

name: Authorization
      in: header
      value: Bearer {$outputs.accessToken}

3. The step using the $outputs.<name> reference will fail as the reference is sent as unresolved plain text (see log output)

Request Headers:
      accept: application/json
      authorization: Bearer {$outputs.accessToken}

Expected behavior

As the arazzo specification outlines the possibility to reference $outputs.<name> (although not clear which scope this refers to - I'm assuming global across all outputs of the current execution), such references should be resolved accordingly and replaced with the latest value before request execution.

Logs

There is currently no log output for what outputs were captured during workflows/steps, but the following is an excerpt from a log output of the subsequent request:

Request Headers:
      accept: application/json
      authorization: Bearer {$outputs.accessToken}

OpenAPI description

N/A

Redocly version(s)

2.54.2

Node.js version(s)

v24.21.0

OS, environment

Linux, Ubuntu 24

Additional context

I would like to re-use workflows in multiple places and across different arazzo files in order to avoid duplicate code. Currently the output reference only works when specifying a local workflow ID. $outputs and $sourceDescriptions.<..>.outputs.<name> don't seem to work.

[DmitryAnansky]

Hi @sww-at-work .
Could you please provide a small Arazzo file example that can be shared?
You could probably build one using our public Redocly Cafe API.

If I may guess, it looks like your output references are missing the corresponding step or workflow IDs needed to identify the source of each output. Like $steps.[STEP_ID].outputs.[YOUR_OUTPUT_NAME] or $workflows.[WORKFLOW_ID].outputs.[YOUR_OUTPUT_NAME].
`$outputs.[NAME] works only in current execution context, like inside step before you remap it.

[DmitryAnansky]

You can also find some examples of output usage in Arazzo official repo, like here.

[sww-at-work]

I will come up with a minimal example, but this is basically the same flow that I'm trying to do which doesn't seem to resolve:
https://github.com/OAI/Arazzo-Specification/blob/12aa8bcb07a2df0719afd1f1f3d18334012a5172/examples/1.0.0/oauth.arazzo.yaml#L51

The specification itself only states the following (afaik), which would suggest that it can resolve the outputs of any executed workflow:
Workflow output value: $outputs.bar or $workflows.foo.outputs.bar (Arazzo Specification)
Does this currently not apply to the respect implementation?

[sww-at-work]

Here is my issue verbally explained... maybe I missed something and could/should do it differently.
I have several APIs secured by the same OAuth provider. Therefore I would like to write a single oauth.arazzo.yml and reference it in the different API arazzo workflows.
The APIs would share a common parameter: the authorization header with access token.
Additionally they would share a failure action to renew the token (referencing the clientCredentialFlow defined in oauth.arazzo.yml which creates the output named "accessToken")
Therefore the common header is defined as component with the value
"Bearer {$sourceDescriptions.oauth.clientCredentialFlow.outputs.accessToken}" <-- fails with unresolvable error although the workflow was run in a previous step successfully
or
"Bearer {$outputs.accessToken}" <-- gets sent as is - not raising an exception of being unresolvable

I would like to avoid any file specific workflow or step reference in such a common header (which would be ideally externalized in another file and sourced via $ref ).