file-sharing

## Instructions When you generate any file the controller needs (close pack PDF, variance chart PNG, CSV export), follow this pattern: 1. **Write the file to `/tmp`** with a stable, period-aware name: - `/tmp/close-pack-2026-05.pdf` - `/tmp/variance-2026-05.png` - `/tmp/variance-2026-05.csv` - `/tmp/je-queue-2026-05.csv` 2. **Reference the absolute path** in your chat response. The frontend converts `/tmp/...` paths into download links automatically. 3. **Do NOT** base64-encode the file into the chat. Do NOT inline binary content. ### Common file types in finance-close - `close-pack-<period>.pdf` — the headline deliverable, per close policy §8.1 - `variance-<period>.png` — bar chart of variance % by cost centre, generated by **variance-analysis** - `variance-<period>.csv` — flat export of the variance dashboard for the close workbook - `je-queue-<period>.csv` — every JE in the period, grouped by type - `accruals-<period>.csv` — accruals booked this period with evidence refs ### Constraints - **Mask sensitive PII** — never write full SSN, full bank account, or unmasked vendor tax IDs to a file. - **Files are ephemeral** — they don't persist across container restarts, so if the controller closes the browser and comes back tomorrow, they'll need to be re-generated. - **No `/etc`, no `/`, no relative paths.** Always `/tmp/<filename>`.