Fix doc drift; document no-enforce-mode and universal publish

Corrections surfaced by doc-auditor + start9-spec-checker:
- testing.md: api suite 47 -> 54
- payments.md: FK enforcement confirmed at db/mod.rs:29
- startos-packaging.md: publish.sh now ships a universal s9pk
- licensing-tiers.md: record enforce-mode retirement and Creator caps
Refresh Current state for the StartOS submission-blocker work.

docs/guides/payments.md

@@ -111,9 +111,11 @@ response carries no parseable positive amount. Regression tests in `tests/api.rs
   `get_merchant_profile_for_product` bug; prefer a subquery or qualify columns.
   `tests/api.rs::merchant_profile_provider_resolution_queries_round_trip` exercises
   the resolution surface — keep it green when touching these queries.
-- FK enforcement is **not** guaranteed at runtime: `PRAGMA foreign_keys = ON` in a
-  migration is connection-scoped. Confirm the pool sets it per-connection before
-  relying on cascade/constraint behavior (e.g. deleting a profile with products).
+- FK enforcement is **ON**: the sqlx pool sets `.foreign_keys(true)` per
+  connection (`db/mod.rs:29`), so cascade/constraint behavior is safe to rely on
+  (e.g. deleting a profile with products). A bare `PRAGMA foreign_keys = ON` in a
+  migration would be connection-scoped and is not what guarantees this — the pool
+  option is.
 - Known: after a `:52`+ install the master Zaprite webhook still points at the
   legacy URL — works via back-compat, needs re-register for per-provider isolation.
 - `unlimited_merchant_profiles` entitlement gates profile count (Creator = 1,