devlog-protocollisted

# DevLog tag protocol — full reference Place tags at the **end** of your response. The Stop hook captures them; the dashboard renders them. Don't write tracking files or `queue.json` by hand — tags replace all of that. Format: `-(tag) content` (case-sensitive). Append `!` after the tag for a breaking change: `-(built!) X`. Multi-line content allowed (up to 2000 chars; 5000 for `about`); the first line is the headline. Write content in the user's language. **Raw lines only.** Emit tags and commands as plain lines at line start. Anything wrapped in backticks or a code fence — like every example in this document — is treated as an EXAMPLE and ignored; the hook nudges you once if a whole line is a backticked command. ## Enforcement (automated) These hooks enforce the rules mechanically — you don't need to remember, the harness refuses to end the turn or run the command until you comply: | Hook | Fires on | Blocks when | |---|---|---| | **Stop closure-check** | every turn end | a `-(built)` / `-(refactor)` fuzzy-matches an open `#N` and you didn't emit its closure. Exit 2 → re-respond with the closure. | | **Stop untagged-guard** | a tag-less turn end | code files — or manual tracking files (tasks/TODO/decisions/CHANGELOG/plans `.md`) — were written this session and NOT ONE tag was ever stored for it. Blocks once per session — re-respond ending with tags that describe the work. Mute: `DEVLOG_UNTAGGED_CHECK=0`. | | **PreToolUse tracking-gate** | `Write`/`Edit` of a manual tra