docs(ci): record hosted MariaDB runner prerequisite failure

2026-10-24 01:55:56 +02:00
parent e75c4a4775
commit 549b2cba5a
5 changed files with 33 additions and 4 deletions
@@ -104,6 +104,10 @@ admin database in favor of a new schema. Loopback is a guard, never permission t
 locally. Alternate `JOBTRACKER_MARIADB_TEST_VERSION` values label a separate compatibility run;
 they cannot be used to claim12.2.2 parity. The CI workflow uses the Compose command, requires a Docker
 daemon/Compose and preserves evidence. A checked-in workflow is not proof of a successful hosted run.
+The first hosted execution, [run843](https://git.cesnimda.uk/cesnimda/jobtrackingapp/actions/runs/843),
+failed before database tests because the runner job image has no `docker` executable. Hosted CI
+remains blocked pending an isolated Docker/Compose-capable test runner; local Compose32/32 remains
+separate evidence. Do not expose a production Docker socket to resolve this prerequisite.

 The ordinary backend project still contains explicitly transitional SQLite/InMemory unit/legacy
 contracts. The ordinary browser fixture explicitly selects SQLite until its SQL seed/proof helpers