# Repository instructions

## Online and offline parity

- Every user-facing feature, fix, data update, and behavior change must be included in both the online app and the offline app.
- Keep shared behavior in `src/` whenever possible. If an online-only dependency is introduced, add or update the corresponding offline alias or adapter under `offline/`.
- Treat `npm run build:offline` as a required verification step for every repository change, in addition to the relevant tests, checks, and online build.
- Do not commit generated `offline-dist/` or `release/` artifacts unless the user explicitly requests packaged artifacts; these directories are ignored build outputs.