Packbase handbook pages

Building and operating Packbase across its web client, API, and data. 14 pages.

1. 01Local developmentHow to install, run, and connect the Wild HQ site and Packbase projects without accidentally using production.
2. 02Products and systemsA map of Packbase, the Wild HQ site, and the boundaries between browser, API, data, and operational work.
3. 03Packbase overviewThe main Packbase concepts, request paths, repositories, and ownership boundaries.
4. 04Packbase webWhere Packbase browser behaviour lives and how routes, components, SDK state, stories, localisation, and the Worker fit together.
5. 05Packbase serverHow the Packbase API is structured, registered, authenticated, tested, and connected to data and background work.
6. 06Admin and moderation workWhere Packbase staff and moderation features now belong, what already exists, and how to preserve server-enforced authority.
7. 07Frontend changesA repeatable Packbase web workflow for routes, components, SDK state, accessibility, localisation, and stories.
8. 08Server and API changesA safe workflow for Packbase routes, schemas, authorisation, domain logic, tests, and public contracts.
9. 09Running PackbaseSafe operational practice for Packbase data, background work, releases, maintenance, and incidents.
10. 10Database and migration changesHow to change Packbase PostgreSQL and Prisma state without treating a destructive sync command as routine development.
11. 11Background workHow Packbase queues, imports, cleanups, retries, and graceful shutdown affect implementation and incident work.
12. 12Releases and deploymentsHow to prepare, authorise, deliver, verify, and recover a Packbase release without guessing its environment.
13. 13Incidents and maintenanceHow to recognise, coordinate, mitigate, verify, and learn from a Packbase service failure.
14. 14Packbase glossaryThe project terms a volunteer will encounter in Packbase tasks, code, interfaces, and operations.