Work only in this isolated synthetic workspace. Use Read to inspect these seeded files: README.md, package.json. Invoke Bash exactly once for each command below, serially in the listed order. Each Bash call must contain only its listed command, unchanged. Do not run commands in parallel, combine or chain them, or add environment investigation commands:
Command 1 (exact Bash input):
npm run lint -- orders
Command 2 (exact Bash input):
npm run lint -- billing
Command 3 (exact Bash input):
npm run lint -- inventory
Command 4 (exact Bash input):
npm run lint -- shipping
Command 5 (exact Bash input):
npm run lint -- accounts
Command 6 (exact Bash input):
npm run lint -- reporting
Use the Bash tool result metadata for its exit code. If the returned summary lacks information required for the answer and a recovery handle is present, use the configured local context recovery tool to fetch only the necessary original output. Use Write to save answer.json containing only the requested JSON object. Do not edit any seeded file or use external network.

Each command runs an ESLint check for one component. Return exactly one JSON object with an `exit_codes` object containing the actual Bash result metadata exit code for each of `orders`, `billing`, `inventory`, `shipping`, `accounts`, and `reporting`, in command order. Set `all_checks_passed` to true only if all six recorded exit codes are zero; otherwise set it to false. Do not infer a missing code from report text. If required exit metadata is unavailable and a recovery handle is present, use the configured local context recovery tool only to obtain that code. Do not inspect implementation files or run extra commands.