daily-dashboardlisted

# When to Use At the start of a working session, before any task is chosen. Invoked by a person, never by an agent. **Adapting this skill:** filenames below name roles rather than literal paths. `docs/standing-documents.md` describes the document set, what each file does, and how the pieces work together. `db` throughout means whatever your durable store is called. Substitute your own filenames freely. `session-close` writes the day's residue to disk. This skill reads it back. The two are one loop, and the loop only closes if the reading half checks the tree instead of reciting what the last session claimed. Those disagree more often than they agree. The session this skill was reconstructed from found a queue task with no status field and a manifest naming a file that was not on disk, both inside the documents it was quoting. Work the phases in order. Phase 4 is the point of the whole procedure. ## Phase 0: This is chat output, not a document The dashboard is a message. Do not write it to a file, and do not open a daily note, a summary, or a scratch document to hold it, unless asked for one in the same breath. Everything in it worth keeping is already some standing file's job, and a second copy is how two sources of truth get born. This tree also has a standing rule against generating a document without explicit permission, and a dashboard is not that permission. ## Phase 1: Read the standing files `CLAUDE.md` names where the list of must-stay-current files lives. Rea