# Working on Launch Harness

- Read README.md and docs/ARCHITECTURE.md before changes.
- Worker API lives in src/, browser UI in public/, schema in migrations/.
- One deployment is one organization. Never add external private DB bindings or hard-coded customer accounts.
- All writes require authorization, validation and audit records. Updates use optimistic revisions. Child writes must check the parent is active in the same database statement.
- Approved/published content must return to draft when its payload changes. This app does not send messages to providers.
- Preserve null metrics as unknown; never replace them with zero in totals or charts.
- Keep raw credentials out of output, URLs, source, screenshots and logs.
- Run npm test, npm run lint and npm run check:build. Use npm run demo for isolated UI checks.
- Inspect every route at desktop and mobile widths after shared UI changes. Verify dialogs, keyboard navigation, error preservation and empty states.
- Do not deploy or change cloud resources as part of a test. The setup wizard requires explicit selection of the account and environment.
- Release files are allowlisted by scripts/release.mjs. Test a fresh extracted archive before publishing it.