---
name: verify-cra-build
description: Verify the CRA app's build path by running the repository's prebuild checks, production build, and artifact validation before deploy or handoff.
---

# Verify CRA Build

Use this skill when the task is to confirm that the CRA app still builds cleanly or to debug build regressions.

## Workflow

1. Start from the repo root:
   - `C:\Users\Administrator\Desktop\Dev_App\CRA_Local_W2026\CRA_Local_W2016_Server`
2. Run the standard verifier:
   - `npm run verify:build`
3. Classify the failure before editing code:
   - `prebuild` failure: fix the specific guard script output first.
   - `build` failure: fix the Vite, TypeScript, import, or runtime bundling error.
   - artifact failure: inspect `scripts/write-build-info.mjs` and `dist/build-info.json`.
4. After changes, rerun `npm run verify:build`.

## Repo-specific expectations

- `prebuild` already chains the i18n, token coverage, mojibake, and NDA template integrity checks.
- `build` must regenerate `dist/build-info.json`.
- A successful verification means:
  - `npm run prebuild` passed
  - `npm run build` passed
  - `dist/build-info.json` exists
  - `dist/build-info.json.builtAt` is a valid timestamp
  - if a git hash is present, it is a full 40-character SHA

## Guardrails

- Do not remove or bypass existing prebuild checks just to get a green build.
- Prefer fixing the underlying broken input, import, or script behavior.
- Keep changes scoped to build health unless the user asks for broader refactors.