[ricardozanini]

Fixes #1203.

Clarifies how HTTP response headers and other response metadata can be accessed in workflow definitions.

Changes:

• Update dsl-reference.md with an example and a note showing how output: response under with produces the full HTTP response object (including headers), which can then be projected using output.as or export.as
• Add a CTK scenario in ctk/features/call.feature testing output: response combined with output.as
• Add examples/call-http-output-headers.yaml demonstrating this pattern

[Copilot]

🟡 Changes recommended

Active critical and moderate issues leave the strict output.as examples and scenario functionally incorrect, with an additional weak header assertion.

4 open issues

• Wrap output.as projections in runtime-expression delimiters · New
• Use runtime-expression delimiters for output.as projections · New
• Use runtime-expression delimiters for output.as projections · New
• Assert that projected headers contain a response value · New

What changed in this PR

This pull request documents how workflows can access HTTP response metadata, including headers, by selecting output: response and projecting response fields. It also adds a reusable example and CTK coverage.

Changes:

• Documents response content and header projections in dsl-reference.md.
• Adds an example workflow demonstrating HTTP response header access.
• Adds a CTK scenario covering output: response with output.as.

This pull request requires changes.

File	Reviewed changes and findings
examples/​call-http-output-headers.yaml	Demonstrates extracting response content and headers. Moderate finding (2 votes): .content and .headers must be wrapped as ${ .content } and ${ .headers } runtime expressions.
dsl-reference.md	Documents response metadata access. Moderate finding (2 votes): the example must delimit .content and .headers as ${ .content } and ${ .headers }.
ctk/​features/​call.feature	Adds conformance coverage for response filtering. Critical finding (1 vote): object-form output.as values require ${...} delimiters. Nit (2 votes): strengthen the header assertion to verify an actual header value or non-empty headers map.

_{Review effort: Lite}

[cdavernas]

LGTM, aside from Copilot's review

[Copilot]

🟢 Approval recommended

The review status records no active issues remaining for the documented response projections, conformance coverage, and example.

4 open issues

• Wrap output.as projections in runtime-expression delimiters
• Use runtime-expression delimiters for output.as projections
• Use runtime-expression delimiters for output.as projections
• Assert that projected headers contain a response value

_{Review effort: Lite}

[Copilot]

🟡 Changes recommended

A moderate conformance-test issue remains because the header assertion assumes one casing for a case-insensitive HTTP header name, potentially rejecting conforming runtimes.

1 open issue

• Avoid assuming response header names preserve their casing · New

4 resolved since last review

• Wrap output.as projections in runtime-expression delimiters
• Use runtime-expression delimiters for output.as projections
• Use runtime-expression delimiters for output.as projections
• Assert that projected headers contain a response value

_{Review effort: Lite}

[Copilot]

🔵 Needs a closer look

The CTK assertion incorrectly requires the exact Content-Type casing even though conforming runtimes may normalize HTTP header names differently, potentially rejecting valid implementations.

1 open issue

• Avoid assuming response header names preserve their casing

_{Review effort: Lite}

[Copilot]

🔵 Needs a closer look

Human assessment is needed because a moderate hidden compatibility issue in the CTK assertion can cause false failures across conforming runtimes due to case-insensitive HTTP header handling.

1 open issue

• Avoid assuming response header names preserve their casing

_{Review effort: Lite}

[Copilot]

🟢 Approval recommended

No active review issues remain, and the change includes the requested documentation, example workflow, and conformance coverage for HTTP response metadata and header projections.

No open issues 🎉

1 resolved since last review

• Avoid assuming response header names preserve their casing

_{Review effort: Lite}

[Copilot]

🟢 Approval recommended

The review records no active issues, with the documentation and added CTK coverage supporting the intended HTTP response projection update.

No open issues 🎉

_{Review effort: Lite}