@mcp-b/do-runtime 0.4.0 → 0.5.0

package/dist/src/api/sql.d.ts

@@ -26,14 +26,24 @@
  *     `abstract` in the types — JSG nested types have no JS constructor — so the
  *     faithful shape is a constructor that refuses. `sql.Cursor` exists for
  *     `instanceof`, which is all upstream exposes it for.
- *  3. **The regulator is ported whole; what is missing is the authorizer that
- *     calls it.** All three callbacks are here and none of them needed the
+ *  3. **The regulator is ported whole, and that is not the whole authorizer.**
+ *     Four of its five members are here as callbacks, and none needed the
  *     authorizer to compute anything — `isAllowedName` is a prefix test,
- *     `isAllowedTrigger` is `return true`, `allowTransactions` throws. What the
- *     authorizer supplied was the *identifiers*, not the decisions. With no
- *     authorizer the statement text is the only source, so `exec` tokenizes it
+ *     `isAllowedTrigger` is `return true`, `allowTransactions` throws,
+ *     `shouldAddQueryStats` is a constant. The fifth, `onError`, is not a
+ *     callback at all in this port: it is every `throw new Error(message)`
+ *     below, which is all its upstream body does with a refusal message.
+ *     For those, what the authorizer supplied was the *identifiers*:
+ *     with none, the statement text is the only source, so `exec` tokenizes it
  *     and runs `isAllowedName` over every identifier-shaped token. That is
  *     deliberately STRICTER than upstream — see `SQL_RESERVED_PREFIX_MESSAGE`.
+ *
+ *     But the authorizer also makes decisions no callback ever sees, and those
+ *     do NOT arrive with the regulator: `SQLITE_ATTACH` / `SQLITE_DETACH`, the
+ *     `SQLITE_CREATE_TEMP_*` family and the `temp` schema, `SQLITE_PRAGMA`, and
+ *     the `SQLITE_CREATE_VTABLE` module list. Each is refused from the text in
+ *     `refuseUnauthorizedForms` and `requireAllowedPragmas`. `SQLITE_FUNCTION`
+ *     is the one still unported — see the README divergence row.
  *  4. **`ingest` stays at upstream's SQLite seam.** `SqliteDatabase.ingest()`
  *     executes every complete statement and returns the partial tail, using the
  *     same compiled boundaries and regulator as `exec`.
@@ -73,7 +83,7 @@ export declare const STATEMENT_NOT_CONSTRUCTIBLE_MESSAGE = "Illegal invocation:
  */
 export declare const SQL_RESERVED_PREFIX_MESSAGE: string;
 /**
- * ← `SqlStorageRegulator` (`sql.h:15-22`, `sql.c++:143-173`), whole.
+ * ← `SqlStorageRegulator` (`sql.h:15-22`, `sql.c++:141-165`), whole.
  *
  * Upstream reaches these through the SQLite authorizer while a statement is
  * being compiled. `exec` calls them from the statement text instead, which is
@@ -100,6 +110,7 @@ export declare const SqlStorageRegulator: {
  * byte-identical so a caller matching on it ports unchanged.
  */
 export declare const SQL_NOT_AUTHORIZED_MESSAGE = "not authorized: SQLITE_AUTH";
+export declare const SQL_VACUUM_REFUSED_MESSAGE = "cannot VACUUM from within a transaction: SQLITE_ERROR";
 /**
  * ← the `jsg::Ref<DurableObjectStorage>` `SqlStorage` holds, narrowed to the one
  * member it reaches through (`SqlStorage::getDb`). `DurableObjectStorage`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-b/do-runtime",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "Cloudflare's Durable Object runtime (workerd), ported to TypeScript: actors with input/output gates, SQLite storage, facets and alarms, running in the browser and in Node.",
   "keywords": [
     "actors",