The layer between what was decided and what actually shipped: every rule, why it exists, and its live link to code, tests, and the demo.
when: a timer is active and the display sleeps then: the countdown continues the chime still fires at zero
when: items are checked off and the app reloads then: the list restores with the same items
when: a conversion yields a repeating decimal then: the result rounds to two decimals
when: a share code is older than 24 hours then: the relay rejects it with 410
when → then: it's design taste. Routes to the exploratory track, where a human reviews a demo rather than a generated test. No automated tests are produced.You gate the demo. Approve and the tests get written; reject and the work goes back.
list-core.js (persistence) · + list-core.test.js (5 tests) · 1 file changed, 42 insertionsStart in plain language, shape it into a when → then, and add a note on why it exists, so reviewers can see the reasoning.