fix leftover 'apply script' wording in ADR and use realistic examples in repl.md table

Agent-Logs-Url: https://github.com/counterfact/api-simulator/sessions/b37bee49-842a-4c64-ad79-e29c8cdd03bb

Co-authored-by: pmcelhaney <51504+pmcelhaney@users.noreply.github.com>

Author: Copilot

docs/adr/001-apply-command-with-function-injection.md

@@ -27,7 +27,7 @@ Three designs were proposed as working documents in `.github/issue-proposals/`:
 
 **Solution 1 (Minimalist Function Injection) is selected.**
 
-An apply script is a TypeScript file with one or more named function exports. When `.scenario <path>` is run, Counterfact splits the argument on `/`, uses the last segment as the function name and the rest as the file path (relative to `<basePath>/repl/`), dynamically imports the module, and calls the named function with a live `ApplyContext` (`$`) object:
+A scenario script is a TypeScript file with one or more named function exports. When `.scenario <path>` is run, Counterfact splits the argument on `/`, uses the last segment as the function name and the rest as the file path (relative to `<basePath>/repl/`), dynamically imports the module, and calls the named function with a live `ApplyContext` (`$`) object:
 
 ```ts
 // repl/sold-pets.ts

docs/features/repl.md

@@ -68,9 +68,9 @@ For more complex setups you can automate REPL interactions by writing _scenario
 
 | Command | File | Function |
 |---|---|---|
-| `.scenario foo` | `scenarios/index.ts` | `foo` |
-| `.scenario foo/bar` | `scenarios/foo.ts` | `bar` |
-| `.scenario foo/bar/baz` | `scenarios/foo/bar.ts` | `baz` |
+| `.scenario soldPets` | `scenarios/index.ts` | `soldPets` |
+| `.scenario pets/resetAll` | `scenarios/pets.ts` | `resetAll` |
+| `.scenario pets/orders/pending` | `scenarios/pets/orders.ts` | `pending` |
 
 A scenario function receives a single argument with `{ context, loadContext, routes, route }`: