feat: transition module packages to database ABI v1

docs/architecture/platform-architecture.md

@@ -682,13 +682,11 @@ Module Package v1, a deterministic `.tar.gz` with its SHA-256.
   and `THIRD_PARTY_NOTICES`, and writes the archive.
 - **The verifier.** Core's `verifyModulePackage` reads the archive in memory and refuses links,
   special files, and escaping paths. It checks every digest and identity, the target and runtime,
-  and the transitional Drizzle agreement, runs the platform's own module and migration validation,
-  and loads the backend once in a short-lived process with an empty environment. Only then does it
-  extract anything.
-- **What exists today.** Only the `any` target. Drizzle agreement is recorded as transitional, not a
-  database ABI. [ADR 0050](decisions/0050-module-database-abi-v1.md) defines the Module Database ABI
-  that removes it for modules that declare that ABI. Manifest version 8 now lets a module declare
-  `database: { abi: 1 }`; Core gives each such module its own attributed ABI executor and validates
-  its plain schema metadata. A version 8 module that omits `database` remains on the temporary
-  legacy facade. Packaging still uses ADR 0049's transitional Drizzle agreement in this slice; the
-  packager transition and template ABI migration are deliberately next.
+  runs the platform's own module, schema, and migration validation, and loads the backend once in a
+  short-lived process with an empty environment. Only then does it extract anything.
+- **What exists today.** Only the `any` target. A manifest-v8 ABI module carries no
+  `transitional.databaseRuntime`; Drizzle may be bundled as its private implementation detail, and
+  Core validates plain schema metadata without comparing ORM versions. A version 8 module that
+  omits `database` remains on the temporary legacy facade and keeps ADR 0049's exact transitional
+  Drizzle agreement. The canonical template now demonstrates ABI v1. The legacy facade still
+  exists.