write-a-requirement-leaf

What problem does it solve? Executable specifications become unreadable when requirement lines mix scannable summaries with long rationale and acceptance notes, making the numbered spine hard for owners to review. ## Core Features & Use Cases - Leaf Line Format: Defines the backtick-wrapped dotted number convention (e.g. 4.2) where each leaf reads as a single scannable one-liner. - Collapsed Detail Blocks: Places rationale, acceptance notes, edge cases, and owner-verification recipes inside a <details> block hidden under the line. - Kind Routing: Routes each leaf to a verification kind — surface snapshot, behavior, logic, saga, per-project extractor/support/server, or a heavy e2e singleton — based on what can honestly observe the assertion. - Use Case: When adding a new requirement to requirements.md for a Chrome extension popup state, write the one-liner leaf and assign it a surface snapshot kind with a committed golden image. ## Quick Start Add a new requirement leaf to dev/requirements/requirements.md following the write-a-requirement-leaf conventions.