Say that losing the state directory forgets the latest logout (part of #256)

The state directory bullet in README.md and the session package doc now
say that the time of the latest logout is kept in the database, which a
restart without a persistent volume loses.

Model: opus-5-5

README.md

@@ -71,9 +71,10 @@ The state directory (`state_dir`, `/var/lib/pixa` in the container) holds the
 database and the disk cache:
 
 - It needs a persistent volume: without one, every restart starts with an empty
-  cache. In the container, the startup script gives the directory to the user
-  pixa runs as (uid 65532) and sets its mode to `750`; outside it, that user
-  must be able to write the directory.
+  cache and forgets the latest logout, so the login sessions that logout ended
+  work again (see Encrypted URLs). In the container, the startup script gives
+  the directory to the user pixa runs as (uid 65532) and sets its mode to `750`;
+  outside it, that user must be able to write the directory.
 - `cache_max_bytes` limits the source and transformed images together. The
   database, the metadata files, the `.meta` file beside each transformed image
   and files still being written come on top, and eviction runs in the
@@ -359,7 +360,7 @@ nor change what it asks for.
    with the one signing key, so logging out ends every login session, in every
    browser: pixa saves the time of the latest logout in its database and refuses
    a login session made before it, a copy of the session cookie included, also
-   after a restart.
+   after a restart that keeps the state directory (see Deployment).
 2. On the generator page, give the source image's URL, the width and height, the
    format, quality and fit, and how long the URL lasts, then submit the form
    (`POST /generate`). The format is JPEG XL unless another is chosen; a form