0.11.7 — the mark survives the jump

The previous version was meant to rescue a mark granted just before a jump to another page. It rescued it only when nothing was happening — that is, exactly when there was no need.

**The pending flag was cleared at the moment of the click.** The result: it could not be seen here, because the page was vanishing, and on the next page there was nothing left to show. The mark existed in the database and nowhere else.

**The flag is now cleared only after the animation has had time to run.** If nothing took the page away, the animation finished and the flag goes — all is well. If something did, the flag stays in browser storage and the mark floats up on the next page.

The whole fix is one instruction moved two seconds later. It is worth describing precisely because it is so small: **the fault came not from missing knowledge but from an assumption that a click and a navigation are one event.** They are two, and the entire problem fits between them.

Three releases in a row about the same mechanism — 0.11.5, 0.11.6 and this one. Each corrects the last, and none is a rewrite of a number that already shipped. A changelog should show how something reached a usable state, not pretend it arrived there at once.