# Build validation status

## Release

**YourStories.life 2026.08.27.1 — QR Claim & Story Core**

## Completed in the packaging environment

- JavaScript syntax validation completed for every `.js` and `.mjs` file with Node.js `--check`.
- All `.jsx` files were parsed with TypeScript's JavaScript/JSX parser without dependency resolution.
- Every JSON file was parsed successfully.
- Local alias imports, relative imports and referenced `/public/assets` files were checked for missing targets.
- CSS delimiter balance was checked.
- The application contains no `.env` file, production credentials, customer data or `node_modules` directory.
- The release archive is verified separately with `unzip -t` after packaging.

## Must still be completed on staging

The packaging environment could not reach the npm registry, so dependencies were not downloaded and a real `next build` was not executed here. Before this release is considered staging-approved, complete these steps on the cPanel staging server:

1. Copy `.env.example` to a protected application-root `.env` file, or configure the same variables in cPanel Application Manager.
2. Run `npm install` to create and preserve the first `package-lock.json`.
3. Run `npm run check:env`.
4. Run `npm run build`.
5. Run `npm run migrate` against the empty staging database.
6. Run `npm run seed:admin`.
7. Register `app.js` as the Passenger startup file and restart with `tmp/restart.txt`.
8. Complete every item in `TEST_CHECKLIST.md` on iPhone, Android and desktop.

A source package passing structural checks is not the same as a verified production deployment. Promotion to `yourstories.life` should happen only after the staging build and end-to-end QR claim test pass.