dsc-scenariolisted

# DSC Scenario Composer Produce a plan of SCAPI / OCAPI calls – in order, with scope union, ID threading, and a runnable cURL block – to reach a target state. Every claim backed by a public `developer.salesforce.com` URL. ## When to use The user is trying to reproduce a customer flow on an instance and needs to know: - Which API calls must happen *before* the target operation can succeed. - Which scopes the instance's SLAS/OAuth client must be configured with. - Where each input to the target (basket IDs, customer IDs, line-item IDs) comes from. Or the user pastes a cURL command and asks "what else do I need to call to make this work." ## Inputs Ask for missing bits only when the skill can't proceed: - **Target** – one of: - An operationId (`createOrder`, `shopper-baskets.addItemToBasket`). - A natural-language goal ("registered shopper adds a coupon and checks out"). You resolve this to an operationId by matching against `_index.json.title` + Summary prose across cached references; ask the user to confirm before proceeding. - A sample request (cURL, raw HTTP). Pass it to `scenario.js` as `request` (in place of `target`) and it resolves the slug for you – it parses the request and matches it against the reference `referenceUrl` names, the same `parse-request.js` + `resolve-slug.js` path `dsc-endpoint-help` uses. You still supply `referenceUrl` (deriving it from a bare cURL is out of scope); if the request can't be resolved, `scenario.js` exits non-zero – ask the