fix(rest): pin the test double's write verbs and drop two test-layer type errors (#7134)

Two CI gates on the previous head, both in the test file added by this PR:

`check:engine-double-contract` — the stub engine's `delete()` / `update()` did
not route through the producer's own dispatch predicates, so the double was
free to accept calls `ObjectQL` itself refuses. A fake looser than the real
implementation is a defect generator (#4434 shipped a dead REST route with a
green suite that way), which is the exact failure mode this card is about.
Both verbs now open with `assertEngineDeleteDispatch` / `assertEngineUpdateDispatch`
from `@objectstack/metadata-core` — already a dependency of this package, and
the right side of the edge: importing them from `@objectstack/objectql` would
invert a dependency turbo refuses.

`check:type-check-debt --re-measure` — `@objectstack/rest`'s TEST_DEBT records
155 and the branch measured 157. Both new errors came from ONE cause: the
extensionless `./rest-server` import does not resolve under
`moduleResolution: nodenext`, so `RestServer` became `any` and the callback over
it reported TS7006. Adding the `.js` extension takes the package back to exactly
155 — the ledger is untouched, which is what a shrink-only ratchet requires.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LBDWUuXmTrHe1o13eik3bT

Author: claude

packages/rest/src/public-form-routes.stored-row.test.ts

@@ -44,8 +44,24 @@
  * That is a deliberate scope line, not an oversight.
  */
 import { describe, expect, it, vi } from 'vitest';
+// The producer's OWN write-verb dispatch decisions (#4550 delete / #5480
+// update), so this fake cannot accept a call ObjectQL itself refuses — a double
+// LOOSER than the real engine is a defect generator, which is how #4434 shipped
+// a dead REST route with a green suite. That failure mode is this very card's
+// subject, so the gate is defending the thing being fixed here.
+//
+// From `@objectstack/metadata-core` and NOT `@objectstack/objectql`: objectql
+// depends in this direction, and that reverse edge is a cycle turbo refuses.
+import {
+    assertEngineDeleteDispatch,
+    assertEngineUpdateDispatch,
+} from '@objectstack/metadata-core';
 import { ObjectStackProtocolImplementation } from '@objectstack/metadata-protocol';
-import { RestServer } from './rest-server';
+// `.js` extension required under `moduleResolution: nodenext`. Without it the
+// import does not resolve, `RestServer` becomes `any`, and every callback over
+// it reports TS7006 — one broken extension reading as two type errors in this
+// package's TEST_DEBT re-measure.
+import { RestServer } from './rest-server.js';
 
 // ─── the real save path ──────────────────────────────────────────────────────
 
@@ -64,8 +80,14 @@ function stubEngine() {
                 rows.push({ id: `r_${nextId}`, ...data });
                 return { id: `r_${nextId}` };
             },
-            async update() { return { id: null }; },
-            async delete() { return { deleted: 0 }; },
+            async update(_table: string, data: Record<string, any>, options: Record<string, any>) {
+                assertEngineUpdateDispatch(data, options);
+                return { id: null };
+            },
+            async delete(_table: string, options: Record<string, any>) {
+                assertEngineDeleteDispatch(options);
+                return { deleted: 0 };
+            },
             registry: { registerItem: () => {}, registerObject: () => {}, listItems: () => [] },
         } as any,
     };