feat: deliver module database ABI by manifest

docs/architecture/platform-architecture.md

@@ -609,7 +609,7 @@ a sandbox: it is `open` precisely because module code is trusted, same-realm cod
 
 [ADR 0041](decisions/0041-module-browser-contributions.md) lets one module contribute a browser
 renderer to a capability another module provides — the browser half of the capability system Core has
-had since ADR 0006. `manifestVersion: 7` declares a namespaced id, its own version, a target
+had since ADR 0006. `manifestVersion: 8` declares a namespaced id, its own version, a target
 capability, a compatible range, and one artifact. That is the complete list: there is no payload
 schema, slot, ordering, or rendering hint anywhere in the platform, so Core cannot learn what a
 "slide" is because the declaration cannot express it. Discovery resolves the artifact through the
@@ -687,6 +687,8 @@ Module Package v1, a deterministic `.tar.gz` with its SHA-256.
   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. Core's ABI v1 executor
-  (`createModuleDatabaseExecutor`) exists and is proven against PostgreSQL. No module can declare the
-  ABI or receive the executor yet: that needs manifest version 8.
+  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.