Correct store phrasing — a module gets a database only if it asks

Not "every module's database"; a module requests one via requires
postgres-database. The one server holds the controller's contexts and the
database of each module that asks for one.

Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx

internal/bootstrap/bootstrap.go

@@ -589,7 +589,8 @@ func Run(ctx context.Context, o Options, d Deps, say func(string)) (Result, erro
 
 	// ---- 14. store ------------------------------------------------------------------------
 	// The foundation's own store, ADOPTED as the `postgres` module (novox/hq issue 051): one
-	// server holds the control plane's contexts and every module's database, rather than the
+	// server holds the control plane's contexts and the database of each module that asks for one,
+	// rather than the
 	// foundation's store beside a second one a module raised. Adopted in place — the module names
 	// the container the foundation is already running, and the applier leaves it be (phase3.go).
 	say("store — the foundation's store, adopted as the postgres module: one server, not two")

internal/bootstrap/phase3.go

@@ -16,7 +16,7 @@ import (
 // (novox/hq ADR 0006). That leaves two servers behind: the foundation's, and a second one the
 // `postgres`/`lavinmq` modules used to raise for other modules to use. This turns the foundation's
 // own servers into those modules, so a mesh runs ONE postgres and ONE lavinmq — the control plane's
-// contexts and every module's database in the same server (WBS 3.1/3.2).
+// contexts and the database of each module that asks for one, in the same server (WBS 3.1/3.2).
 //
 // **Adopted in place, not replaced.** The control plane is stateless and is swapped for a fresh
 // container (control.go); the store and broker hold the mesh's memory and its bus, so they are kept.