0.11.5 — new entry, new counter

The site moves between entries without reloading the page, and that is an advantage — until it turns out that a component meant to live for one page lives for the whole visit, memory included.

**The “already asked” lock from the previous entry stayed on.** The reader moved to the next text, the counter started, the threshold passed — and nobody asked for anything, because the component was sure the matter had been settled. The mark was due and never came.

**The second fault had the same root.** A failed request — a dropped connection, a momentary refusal from the server — blocked the counter for the rest of the visit. One bad second on the network cost everything the reader read afterwards.

The lock now holds for the duration of a single request. If the request does not arrive or the server refuses, the counter tries again in five seconds. A lock should guard against repeating, not against retrying — two different things, and confusing them costs marks nobody will ever hear about.

Both faults were reported by a person reading on a phone, not by a test. Tests check what we wrote; a person checks what happens.