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 build -- orders
Command 2 (exact Bash input):
npm run build -- billing
Command 3 (exact Bash input):
npm run build -- inventory
Command 4 (exact Bash input):
npm run build -- shipping
Command 5 (exact Bash input):
npm run build -- accounts
Command 6 (exact Bash input):
npm run build -- 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 the configured component bundle build and prints bundler output. Build artifacts are generated in the copied workspace. Use actual command output and Bash metadata. Write one JSON object with exactly three top-level fields: exit_codes, mapping all six component names to their Bash exit codes; all_builds_succeeded, true only when all six exit codes are zero; and first_failure, null when all six builds succeed, otherwise an object for the first nonzero command containing component and exit_code, plus diagnostic copied from its first actual error line when one is visible (use null only if no diagnostic line appears). Do not report module counts, bundle byte sizes, inferred totals, or custom summaries.