[Upd4ting]

ANT-2382. Moves dms onto @antelopejs/interface-database 0.4.0, where a query is a plain object that runs only through .run(). Stacked on #888 (fix/interface-dms-stored-row).

⚠ sensitive: it changes the interface-dms contract (peer @antelopejs/interface-database >=0.4.0 <1.0.0) and the database module a deployment must run.

tgz-pending:

• @antelopejs/interface-data-api comes through fix(interface-dms)!: move to interface-data-api 0.7's StoredRow #888's tarball: main 170f079, packed as 0.8.0.
• @antelopejs/interface-dms-builder comes through .tgz-deps/antelopejs-interface-dms-builder-b04af21.tgz: this repo's own builder, packed as 0.4.2. npm's 0.4.1 is not standalone, so a project loading the DMS without a builder module fails with "Unresolved interface dependencies: dms requires @antelopejs/interface-dms-builder".
• swap-tgz.sh restores >=0.8.0 <0.9.0 and >=0.4.2 <1.0.0.

Summary

 packages/dms, packages/dms/playground, packages/interface-dms (peer and dev)
-  "@antelopejs/interface-database": ">=0.3.0 <1.0.0"     (interface-dms peer: >=0.1.11)
+  "@antelopejs/interface-database": ">=0.4.0 <1.0.0"
 test host (src/test/antelope.test.ts), playground (antelope.config.ts)
-  @antelopejs/mongodb 1.6.2 / ^1.4.3
+  @antelopejs/mongodb 1.8.0 / ^1.8.0
 Builder engine (query-emit, query-structure, query-preview, resource-schema, table-readers)
-  return { value: await model.paidRevenue() };
+  return { value: await model.paidRevenue().run() };
 tenant-instances.ts
-  function getTenantSchema(): Schema
+  function getTenantSchema(): NonNullable<ReturnType<typeof Schema.get>>   // Schema.get takes no type arguments

#903 already made the runtime run its own queries through .run(). This PR adds:

• the dependency move;
• the database module the tests and the playground run;
• the code the Builder generates for modules;
• the docs.

packages/dms/docs/02.building/20.migration-interface-database-0-4.md is the deployment and module guide. packages/interface-dms/UPGRADING.md (Unreleased) lists the peer range.

Evidence

• Before: on main with interface-database 0.4.0 and mongodb 1.8.0, the playground does not start. registerExistingTenantInstances builds a Set from a query object ("object is not iterable"). ANT-2375's live run saw "this.table.get(...).then is not a function" with decorators 0.3.1.
  After: dms-control up --prepare boots the playground on mongodb 1.8.0 (loaded from .antelope/cache, version 1.8.0), doctor passes, and the smoke journey passes (15 steps, invite mail captured).
• No query left unrun. A ts-morph scan over dms, interface-dms and interface-dms-builder looks for any expression with run() and no then that is awaited, put in Promise.all/race, given a .then, or returned from an async function. It finds 0 on this head. On main's old tenant-instances.ts it reports the 4 broken sites, so it sees them. Queries typed any would escape it.
• Suites on interface-database 0.4.0 and mongodb 1.8.0 (before the final docs commit):
  • table-view-capabilities 17 (/count/batch answers { mine: 2 }, POST …/new no longer answers 500);
  • test:unit 2629;
  • integration 419;
  • builder 668;
  • pnpm run checks 11/11.
• Consumer resolution. Core's own findUnresolvedInterfaces, run on a fresh npm install of the packed dms:
  • Before: with npm's builder 0.4.1, dms requires @antelopejs/interface-dms-builder is unresolved.
  • After: with the 0.4.2 tarball, the builder is stubbed standalone and nothing is unresolved.

Attention

• Release order:
  1. interface-data-api 0.8.0;
  2. swap and merge fix(interface-dms)!: move to interface-data-api 0.7's StoredRow #888;
  3. swap this PR's data-api pin and merge;
  4. release interface-dms-builder 0.4.2 from main;
  5. swap the builder pin;
  6. interface-dms 0.14.0;
  7. dms 0.20.0.
• dms's interface-dms range stays >=0.13.0 <0.14.0 here. The release validate job requires the interface version in the tree to satisfy that range, and the workspace links interface-dms only while its 0.13.x version satisfies it. So raising it before interface-dms 0.14.0 is bumped breaks install and validation. interface-dms's after:bump runs sync and stages dms's README, but does not move dms's range. The raise to >=0.14.0 <0.15.0 therefore has to be committed right after the interface-dms 0.14.0 release and before dms 0.20.0.
• Module code that awaits queries needs .run(). Builder-generated stats routes written before this PR answer with the query object until .run() is added; the guide says so.

Merge Danger

Door: one-way once released. Deployments must run a database module that implements interface-database 0.4, and modules must run their queries through .run().

Blast Radius: wide. Every deployment's database module, every module that queries the database, and the code the Builder generates.