fix: modified curl commands for X-5 UAT#11
Conversation
There was a problem hiding this comment.
Pull request overview
Updates the X-5 manual UAT runbook to reflect the updated invoke API shape by including request_id in example requests and aligning the verification/comparison steps with the new response fields.
Changes:
- Add
request_idto all curl request payload examples. - Update verification expectations to use
timestamp(instead ofexecuted_at). - Update determinism diff instructions to ignore volatile response fields.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| jq 'del(.trace_id, .timestamp, .execution_time_ms)' r1.json > c1.json | ||
| jq 'del(.trace_id, .timestamp, .execution_time_ms)' r2.json > c2.json |
There was a problem hiding this comment.
In the determinism comparison, the two requests use different request_id values (req-005 vs req-006), and the response contract indicates request_id mirrors the request. As written, diff c1.json c2.json will almost certainly show a difference purely due to request_id. Update the jq filters to also remove request_id (and any other per-request identifiers present in the response) so the comparison actually validates deterministic output.
| jq 'del(.trace_id, .timestamp, .execution_time_ms)' r1.json > c1.json | |
| jq 'del(.trace_id, .timestamp, .execution_time_ms)' r2.json > c2.json | |
| jq 'del(.trace_id, .timestamp, .execution_time_ms, .request_id, .session_id)' r1.json > c1.json | |
| jq 'del(.trace_id, .timestamp, .execution_time_ms, .request_id, .session_id)' r2.json > c2.json |
This pull request updates the
docs/uat/X5_Evidence_Attachment_UAT_Runbook.mdto reflect changes in the API request and response structure for UAT scenarios. The main focus is on adding therequest_idfield to all request examples and updating the expected response fields and comparison logic to use the new structure.API Request Updates:
"request_id"field to all example request payloads to demonstrate its required presence in API calls. [1] [2] [3] [4] [5] [6] [7] [8]API Response & Verification Updates:
timestampfield (server-generated execution timestamp) instead ofexecuted_at, and clarified the presence ofrequest_idandresult.trace_id,timestamp, andexecution_time_msfrom diff checks, instead of the previousrequest_idandexecuted_at.