Run the forge, on a database the mesh gave it

Everything up to now stopped at composing a declaration. That proves the
control plane and the host agree, and proves nothing about whether the
thing described works — which is how five modules sat pinned to images
that did not exist while parsing and resolving perfectly.

The forge is the right one to run first. It needs a database from
another module, a password it did not choose, and a connection string it
could not have written itself: the address and port come from what the
database serves, the user name from what the mesh decided both ends
would call it. If any of that is wrong it cannot start, and nothing else
in this suite would notice.

The test checks the chain in the order it has to happen — the login
exists, the database it owns exists, the forge answers, and its log does
not say authentication failed. That last one matters: a forge that
started and could not reach its database would still answer on its port.

Rewriting image references is now shared rather than copied from the
bundle, which had the same problem first. A digest is not knowable until
something is built, and when it is, it belongs to whichever registry
served it — so the text says which image and the scenario says which
copy. Matching is on the repository, with a test that a repository
ending in another one is not half-replaced.

Also makes the planning test put the machine back. Tests here share one
mesh, so the five modules it assigned were inherited by whatever ran
next; harmless while nothing pushed, and not harmless now.

test/integration/mesh.test.ts

@@ -21,6 +21,7 @@ import assert from "node:assert/strict";
 import { existsSync, readFileSync } from "node:fs";
 import { loadScenario } from "../../src/declaration/parse.ts";
 import { raise } from "../../src/lifecycle/raise.ts";
+import { pinnedInto, stillUnpinned } from "../../src/pinning.ts";
 import { destroy, exec } from "../../src/lifecycle/operate.ts";
 import { hostBinaryPath, HOST_PATH } from "../../src/lifecycle/place.ts";
 import { labIsUsable, destroyAll } from "./harness.ts";
@@ -1800,4 +1801,75 @@ test("the real modules resolve together, and compose a declaration a host accept
         `${c.name} carries something secret-shaped in env.${key}, which the broker would see`);
     }
   }
+
+  // Put the machine back. **Tests here share one mesh**, so what this one assigns is what the
+  // next one inherits — and this one assigns five modules whose images are mostly not stocked.
+  // Planning them is harmless; leaving them assigned makes the next push try to start them.
+  for (const name of modules) await mesh(`unassign anchor ${name}`);
+});
+
+// The first of the real module descriptions to actually run.
+//
+// **Everything before this stopped at composing a declaration.** That proves the control plane and
+// the host agree, and proves nothing about whether the thing described works — which is how five
+// modules sat pinned to images that did not exist, parsing and resolving perfectly
+// (novox/hq 04-ISSUES/025).
+//
+// The forge is the one worth running first. It needs a database from another module, a password it
+// did not choose, and a connection string it could not have written itself: the address and port
+// come from what the database serves, and the user name from what the mesh decided both ends would
+// call it (04-ISSUES/022 and 023). If any of that is wrong it cannot start, and nothing else in
+// this file would notice.
+test("the forge runs, on a database the mesh gave it", { skip, timeout: 900_000 }, async () => {
+  for (const name of ["postgres", "gitea"]) {
+    const raw = readFileSync(`${process.env["MESH_LAB_MODULES"]}/${name}.json`, "utf8");
+    // An image the mesh builds has no digest until it is built, and one it does not build belongs
+    // to whichever registry served it. Both are answered by this scenario's own registry.
+    const pinned = pinnedInto(raw, stocked);
+    assert.deepEqual(stillUnpinned(pinned), [],
+      `${name} still names an image nothing serves, so it could not start`);
+    await must("anchor", `printf %s ${quote(pinned)} > /run-${name}.json`);
+    await must("anchor", `docker cp /run-${name}.json mesh-control:/run-${name}.json`);
+    await mesh(`module add /run-${name}.json`);
+    await mesh(`assign anchor ${name}`);
+  }
+  await mesh("push anchor", 300_000);
+
+  // The database first: until the provisioner has made the login, the forge has nothing to
+  // connect to and its own start would prove only that it retries.
+  const psql = async (q: string) =>
+    (await on("anchor",
+      `docker exec postgres psql -U postgres -qAt -c ${quote(q)}`, 60_000)).out.trim();
+
+  let made = "";
+  for (let i = 0; i < 40 && made !== "t"; i++) {
+    made = await psql("select true from pg_roles where rolname = 'mesh_anchor_gitea'");
+    if (made !== "t") await new Promise((r) => setTimeout(r, 3000));
+  }
+  assert.equal(made, "t",
+    `no login was created for the forge:\n${(await on("anchor", "docker logs mesh-provision-postgres 2>&1 | tail -20")).out}`);
+  assert.equal(await psql("select true from pg_database where datname = 'gitea'"), "t",
+    "the login exists and the database it owns does not");
+
+  // And the forge itself, answering. Not that its container exists — that it serves.
+  let answered = false;
+  let said = { out: "", ok: false };
+  for (let i = 0; i < 60 && !answered; i++) {
+    said = await on("anchor", `curl -sf -o /dev/null -w '%{http_code}' --max-time 5 http://127.0.0.1:3000/`, 30_000);
+    answered = said.out.trim().startsWith("2") || said.out.trim() === "303";
+    if (!answered) await new Promise((r) => setTimeout(r, 5000));
+  }
+  assert.ok(answered,
+    `the forge never answered (last: ${said.out.trim()}):\n` +
+      `${(await on("anchor", "docker logs gitea 2>&1 | tail -25")).out}`);
+
+  // **The credential actually worked.** A forge that started and could not reach its database
+  // would still answer on its port, so the log is where the difference lives.
+  const log = (await on("anchor", "docker logs gitea 2>&1 | tail -60")).out;
+  assert.doesNotMatch(log, /password authentication failed|connection refused|does not exist/i,
+    `the forge started and could not use the database it was given:\n${log}`);
+
+  await mesh("unassign anchor gitea");
+  await mesh("unassign anchor postgres");
+  await mesh("push anchor", 300_000);
 });