arazzo-specificationlisted

# Arazzo Specification Write, review, and modify Arazzo workflow specifications that describe deterministic, multi-step API workflows on top of OpenAPI. ## Workflow ### Authoring a New Arazzo Document 1. Identify the business outcome the workflow achieves. 2. Collect the OpenAPI spec(s) involved and note the `operationId`s needed. 3. Read `references/01-overview-and-structure.md` for document skeleton and naming. 4. Read `references/02-core-constructs.md` for source descriptions, steps, parameters, request bodies, and runtime expressions. 5. Draft the document using the skeleton below. 6. Define each step: choose `operationId` (preferred), `operationPath`, or `workflowId`. 7. Thread data between steps using runtime expressions and step outputs. 8. Add success criteria to every step — read `references/03-criteria-flow-outputs.md`. 9. Add failure/success actions for known failure modes (rate limits, auth expiry) — same reference. 10. Extract repeated elements into `components` — read `references/04-reuse-and-composition.md`. 11. For sub-workflow composition, read `references/04-reuse-and-composition.md`. 12. Validate with the checklist below and recommend linting tools from `references/06-ai-agents-validation-practices.md`. ### Reviewing an Existing Arazzo Document 1. Validate structure against the skeleton below. 2. Check every item in the best practices checklist below. 3. Read `references/07-pitfalls-tooling-resources.md` and scan for common pitfalls. 4. Verify all `oper