# reference/ — reference, development & ops-staging material

Everything in this folder is **tracked in git** but is **NOT consumed automatically by
the app's build or runtime**. It is reference docs, manual dev/diagnostic tools, and
ops-staging copies. Removing any of it will not break the build, the dev server, or
production.

This folder is deliberately excluded from the Nuxt/Vite **file-watcher** (via
`.nuxtignore` and the `nuxt.config.ts` watch-ignore) so it never slows the dev server —
even though it is version-controlled.

## Contents

- `dpd/` — DPD Parcel API reference (developer-guideline PDFs + WebConnect XML samples),
  kept handy during the DPD integration work. Vendor reference only.
- `ci/` — production deploy scripts. These are **copied into Jenkins manually** —
  they are NOT pulled or run from the repo. Convention:
  - `latest-working-jenkins-production.sh` — snapshot of the script **currently in
    Jenkins** (copy it FROM Jenkins before touching anything; it is the rollback copy).
  - `deploy-production.sh` — the **next version to paste INTO Jenkins**. Edit this one.
    After a successful deploy, copy it over `latest-working-jenkins-production.sh`.
- `test-scripts/` — manual dev/diagnostic scripts (Synology recording tests, ZUGFeRD
  inspector). Run by hand when debugging; not part of any build.
- `dev-notes/` — ERP dev/debug notes (`AUTH_ERROR_HANDLING.md`,
  `PUSH_NOTIFICATIONS_DEBUG.md`, `VAPID_WEB_PUSH.md`, `laravel-fix-plentyone-confirm.md`).
  Reference docs only.
- `Surveillance_Station_Web_API-.docx` — Synology Surveillance Station Web API vendor
  doc (reference for the surveillance / commissioning-recording feature).

## What does NOT belong here

Anything the build or runtime depends on. For example `scripts/generate-icons.js` stays
in `/scripts` (not here) because `npm run build` runs it via the `generate:icons` step.