decision-loglisted

An ADR is for architecture; most decisions are smaller (we will not support IE; the sprint is two weeks; the API uses cursor pagination; the thesis excludes mobile). They still get relitigated when nobody wrote them down. A decision log is the cheapest record that stops that: one file, one line per decision, appended and never rewritten. ## The file `DECISIONS.md` at the project root (or `docs/DECISIONS.md`; match the repo), newest at the bottom so git blame and diffs stay readable: ```markdown # Decision log Format: date | decision | reason | alternatives | who | revisit when - 2026-09-21 | Cursor pagination on all list endpoints | offset breaks under concurrent writes; clients already handle cursors | offset+limit; keyset only for large tables | API guild (A, B) | if a client cannot support cursors - 2026-09-21 | Thesis scope excludes mobile clients | no access to a device lab; desktop covers 80% of sessions | include with emulators | K with supervisor | if the device lab opens before December ``` One line, under 200 words, no nested lists. Long reasoning links to a doc, an ADR, a ticket, or a meeting record. ## When to add a line - A choice between real alternatives was made, by anyone, that others will have to live with. - A scope was cut or a request declined. - A convention was set (naming, process, cadence). - A decision was reversed: add a new line that says "reverses 2026-08-02 ..." and why; never edit the old line. Do not log: the obvious, the trivial, or a