T22 removed the embedded database provisioner without a replacement decision (high)

[thedancingdeveloper]

stackarr-postgres was an embedded PostgreSQL provisioner, not merely a query layer. It was reduced to a stackarr-mariadb stub while docker/Dockerfile.standalone still references the removed managed-postgres feature.

This silently changes the self-provisioning product behaviour: a standalone build no longer provisions its own database, and nothing says so.

D8 (#29) must decide how MariaDB is delivered before standalone packaging can be called complete.

---

Raised from the handoff register: docs/2026-08-03-handoff-issues.md (NGMS repo).

[thedancingdeveloper]

Blocked on D8 (#29) — a product decision, not an implementation gap.

The substance stands: stackarr-postgres was an embedded provisioner, not a query layer, and reducing it to a stackarr-mariadb stub while docker/Dockerfile.standalone still references the removed managed-postgres feature silently changes what a standalone build does.

The decision D8 needs to make: does a standalone NGMS provision its own MariaDB, or does it require an external one? Those are different products, and the second is a breaking change to the deployment story that should be stated rather than discovered.

Until it is answered, standalone packaging cannot be called complete. Leaving open.