Say in the Audience section that the store has not shipped

README.md

@@ -743,8 +743,9 @@ Who depends on this library, and what they may rely on.
 - **The developer building the SMPP edge of something else.** What binds to `server()` in practice is
   an aggregator's customer-facing edge, a bridge putting SMPP in front of a modern transport, or a
   test double standing in for an SMSC. This is not a store-and-forward SMSC and will not become one:
-  spooling, scheduling, retry policy and billing belong to whatever this is the edge of, and state
-  shared between instances goes through the store in goal 9.
+  spooling, scheduling, retry policy and billing belong to whatever this is the edge of. State shared
+  between instances is for goal 9's store, which has not shipped: today every session keeps its own,
+  in memory.
 - **Pre-1.0, so the minor is the breaking unit** and a patch never breaks. What a 0.4.0 consumer has
   to change is in [MIGRATION.md](https://gitea.larvit.se/larvit/smpp-js/src/branch/main/MIGRATION.md);
   what each later minor changes is in

todo.md

@@ -724,5 +724,5 @@ Each lands under goal 7: an option or a hook, with the call that passes none unc
         memory. Either way, an application that supplied no store never waits on one.
       - **One spelling.** A store-backed cap and the limiter hook both reach a limit shared between
         processes; settle which owns that case before building the second.
-      - **Restore the store operator to README's personas when the store ships.** Removed
-        2026-09-28, maintainer's call, because nothing in the README could serve them yet.
+      - **Restore the store operator to README's personas, and drop "which has not shipped" from the
+        Audience bullet, when the store ships.** Removed 2026-09-28, maintainer's call.