# ROOST — end-of-day report > [!danger] This file is public > This vault publishes to the web. **Write this report as something a stranger will read.** > No client names. No project or repository names from other work. No revenue, rates or hours. No contact details. > If a day's work here can only be described using any of those, write "no public report today" and put the detail in the private vault instead. *Collected into the private admin vault by the `roost` command, along with every other project's report. That collection is private; **this file is not**.* _Snapshot: 2026-08-26 · project: egg_ ## Done today - **Brought into the daily reporting routine.** This vault is now one of the projects whose end-of-day report gets collected automatically. This file was created for that purpose — there wasn't one. - **New reference note: [[The Home System]]** — a public description of how the private working vault is organised: the two layers, the hub-and-spoke arrangement, the single-note root, and the rules. Structure only; no contents. - Linked it from [[Claude Code Integration]] under `## Related`. - `vault-check.py` run clean: 31 notes, 0 errors. ## Open / in progress - **Dormant since 10 July** — roughly seven weeks. Ten modified files and several untracked paths are sitting in the working tree uncommitted, including `CLAUDE.md`, `README.md`, [[Vault Schema]] and [[Claude Code Integration]]. - `.obsidian/plugins/obsidian-local-rest-api/` is untracked — decide whether plugin code belongs in the repo or in `.gitignore`. - Journal gap: the last committed daily note is 10 July, with an untracked note from late July and an untracked August folder. ## Blocked / needs Jeff 1. **Review and commit the working tree.** Ten modified files is a lot of unreviewed drift for a vault that publishes publicly. 2. Confirm whether the untracked journal notes are meant to be published or kept local. ## Notes for next session - **Pre-publish check.** A deny-list scan runs from the private vault against this one before anything goes live. Pattern-based linting covers emails, phones and keys; proper nouns need an explicit list, and that list belongs on the private side. - Publishing is manual and independent of git — commits are staging for the public site, not private storage.