4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	185d0294eb	Keep the store address's query in every test database's address, so store tests reach a socket-addressed store (issue 1889) ... The checker's integration store answers on a unix socket named in the query of MESH_TEST_POSTGRES (?host=<socket dir>&sslmode=disable). The identity, inventory and licences fixtures cut the address at its last slash and appended ?sslmode=disable, dropping host=, so pgx dialled its default socket where no server is: every store test waited out its 20 s readiness bound, each package ran into go test's 10-minute timeout, and the verdict named only the first failure, identity.TestACertificateChainsToTheMeshsOwnAuthority. store.DatabaseForTest now builds that address for every fixture, keeping the query as the template raise already did; identity's fresh is ForTest rather than a second copy. The readiness bound and its error, which wraps the driver's cause, are unchanged.	2026-10-23 08:55:50 +02:00
jschoubben	7892019d9e	Copy each store test's database from a template migrated once, and hash test bus passwords at bcrypt's least cost ... Running ~90 migrations into a fresh database per store test, and bcrypt at the default cost under the race detector, were most of the controller's check (novox/hq issue 591).	2026-10-12 23:53:06 +02:00
jschoubben	c3b88b9148	Rename mesh-control -> mesh-controller, substrate -> foundation ... One name per thing, per the HQ glossary: the module/container/image/binary/repo becomes mesh-controller, the seat the-controller, and the store+broker pair the foundation (embedded base bundles, default template and example lock renamed with their go:embed directives). No behaviour change — a pure vocabulary rename. Claude-Session: https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-16 18:40:40 +02:00
jschoubben	005b928d36	Test the licence store, and name an unknown licence rather than a constraint ... Its own store, its own test database, the same shape every other context has. Five properties: a key with nobody to seal it to is refused rather than kept readably; a key is sealed once per holder and the blobs differ because they are sealed to different machines; a holder recorded afterwards has none and the existing ones keep theirs; releasing a consumer takes its key; and a licence nobody recorded is refused by name. The last was the only one whose message mattered and whose message was not checked — the database's own foreign-key error is true and mentions a constraint, which sends somebody to read a schema instead of typing the name they meant. Partial sealing now says how far it got. The person holding the key is the only one who can finish, and running it again knowing what it will do is different from running it hoping.	2026-08-31 02:59:39 +02:00