@di-framework/pglite-component 0.0.0-stage → 6.0.11

package/LICENSE-APACHE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/LICENSE-MIT

@@ -0,0 +1,23 @@
+MIT License
+
+Copyright (c) 2025-2026 @di-framework Contributors
+
+Contact: support@di-framework.dev
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,305 @@
-# Temporary Holding Version
+# di-framework:pglite — embedded PostgreSQL over WIT
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The provider bundles the PGlite PostgreSQL 17.5 engine into a WebAssembly
+component. SQL calls cross WIT and WebAssembly memory. There is no TCP listener,
+network client, native sidecar, or separate database service.
+
+```text
+app.wasm → di-framework:pglite/database → bundled PostgreSQL engine
+                                                ↓
+                                          WASI filesystem
+                                                ↓
+                                       persistent /data mount
+```
+
+`open("/data/orders", none)` opens a persistent database root. An empty path
+selects `/data/pglite`. Missing or read-only storage fails; the provider never
+silently substitutes an in-memory database. This replaces the old TCP client:
+`PGHOST`, `PGPORT`, and connection-target strings are no longer used.
+
+## npm package
+
+`@di-framework/pglite-component` is versioned with this repository (6.0.x) and
+published by the platform release workflow. It contains:
+
+| Import | What |
+| --- | --- |
+| `@di-framework/pglite-component` | The `SqlDatabase` adapter (`createWasmPgliteDatabase`, see below), ESM with types |
+| `@di-framework/pglite-component/wasm` | `dist/di-framework-pglite.wasm`, the composed provider component |
+| `@di-framework/pglite-component/wit` | `dist/di-framework-pglite.wit`, the WIT recovered from that component |
+| `@di-framework/pglite-component/wit/*` | The source WIT (`wit/world.wit` and its `deps/`) for bindings generators |
+
+`BUILD-INFO.txt`, `SHA256SUMS` and `THIRD-PARTY-NOTICES.txt` ship next to the
+wasm. The adapter needs `@di-framework/repo` `^6.1.0` as a peer dependency.
+
+The release job builds the wasm from source with the same `make` targets as
+CI, runs `make unit smoke` against it, and refuses to publish a pack without
+the wasm or the adapter. The npm copy is for application developers composing
+locally. GHCR stays the digest-pinned source that the CLI composes at deploy
+time (see [Publishing to GHCR](#publishing-to-ghcr)); the two are separate
+builds of the same sources and are not guaranteed to be byte-identical, so pin
+deployments by GHCR digest.
+
+## Build and verify
+
+```sh
+make tools
+make build
+make smoke
+bun test
+```
+
+`bun run build` builds the adapter (`bun run build:adapter`, TypeScript only,
+no engine) and then runs `make build`.
+
+Use the pinned Rust toolchain through rustup, Python 3, and the installed
+`wasm-tools`/`wac`. Preparing the engine from source also needs a Linux Docker
+or Podman daemon, Git, curl, and several GB of build storage. The engine build
+is cached under `target/engine`. Containers are build tools only; deployment
+runs the resulting `.wasm` directly. For a remote Podman daemon, set the task's
+`DOCKER_CONTEXT=podman`.
+
+The build embeds the support filesystem, adapts the engine's WASI Preview 1
+imports to Preview 2, and composes the engine with the Rust database provider.
+It fails if the final artifact imports sockets or leaves the engine unresolved.
+Ship `dist/di-framework-pglite.wasm` together with `THIRD-PARTY-NOTICES.txt`.
+Build provenance and checksums are in `dist/BUILD-INFO.txt` and `SHA256SUMS`.
+
+`make smoke` composes a real WIT consumer, runs it without network access, and
+checks typed parameters/results, SQL errors and recovery, transactions,
+rollback on close/drop, exclusive connection ownership, durability settings,
+and persistence across separate runtime processes. It also exits a runtime
+with an open transaction and verifies that committed rows survive and the
+uncommitted row is absent after restart. No scripted database server is used.
+
+## Publishing to GHCR
+
+The pglite component is published to GitHub Container Registry (GHCR) as an OCI wasm component. [The workflow](https://github.com/di-framework/platform/actions/workflows/pglite-component-publish.yml) runs by itself on each push to `main` that changes one of its input paths (`on.push.paths`). `workflow_dispatch` stays available for reruns and always builds.
+
+The workflow has four jobs:
+- `check-source` (`packages: read`) hashes the committed input files (`scripts/source-check.ts`). On a push it skips the build when `ghcr.io/di-framework/pglite-component:src-<hash>` already exists, so commits that do not change the component publish nothing.
+- `build` (no write token) runs the same targets as `ci.yml`: `make tools-rust`, `make unit smoke` (which runs `make build`, composing the provider with the engine via `wac plug`), then the publisher crates' clippy and tests.
+- `publish` (`packages: write`) downloads the tested `dist/` and runs `pglite-component-publisher`. It never rebuilds or modifies `dist/`. It checks `SHA256SUMS`, requires the export `di-framework:pglite/database@0.2.0` and rejects any import that is not `wasi:*`, then pushes `ghcr.io/di-framework/pglite-component:<commit sha>` once, pulls it back by the manifest digest to compare bytes, then points the version tag (`0.2.0`, the WIT package version) at that same manifest with `oras tag` and asserts both tags resolve to one digest. The `build` job passes the tested wasm sha256 to `publish`, which verifies it before pushing. It also tags the manifest `src-<hash>`.
+- `pin` (`contents: write`, `pull-requests: write`) opens or updates the PR `bot/pin-pglite-component`, "chore: pin pglite-component to <digest>", which rewrites the digests in this README with `scripts/pin-artifact.ts`. GitHub does not run workflows on a PR that `GITHUB_TOKEN` opened, so a maintainer has to start its checks (close and reopen it) before merging. It also runs when a push's source is already published (a revert to an older source, or a pin PR closed unmerged), so `main`'s pin follows the current source; it opens no PR when `main` already has the digest. On that path the `realign` job (`packages: write`) points the moving version tag back at that source's digest with `scripts/retag.sh`, which leaves a tag that is already there alone. Every tag move is behind the same source guard, so a stale run never retags.
+
+Tags are movable. `0.2.0` always points to the latest `main` publish for WIT package 0.2.0, and re-running a commit also moves its SHA tag. Only the `@sha256:...` digest is immutable, so consumers pin by digest.
+
+### Artifact location
+
+The digest is in **Details** > **Record component digest** > **Step summary**, and in the `pglite-publish-report` artifact (`publish-report.json`).
+Published digest: `ghcr.io/di-framework/pglite-component@sha256:8bc30505cf28b1a65f72588da692d2ba3d79a6a2025c9256341a8625967a3286`
+
+**Note:** The GHCR package must be made public by an org admin after the first publish. Until then, only members with access to di-framework/platform can pull it.
+
+## Use from an application
+
+The application imports `di-framework:pglite/database@0.2.0`. For a JavaScript
+component built with the framework's component toolchain:
+
+```ts
+import { open } from 'di-framework:pglite/database@0.2.0';
+
+const db = open('/data/orders', undefined);
+try {
+  db.exec('CREATE TABLE IF NOT EXISTS orders (id bigint PRIMARY KEY, title text)');
+  db.run('INSERT INTO orders VALUES ($1, $2)', [
+    { tag: 'integer', val: 1n },
+    { tag: 'text', val: 'First order' },
+  ]);
+  const row = db.first('SELECT title FROM orders WHERE id = $1', [
+    { tag: 'integer', val: 1n },
+  ]);
+} finally {
+  db.close();
+}
+```
+
+Compose the application with the provider. For a local build:
+
+```sh
+make compose APP=path/to/app.wasm OUT=path/to/app.composed.wasm
+mkdir -p ./data
+wasmtime run --dir ./data::/data path/to/app.composed.wasm
+```
+
+To use the published OCI component from GHCR instead (pin by digest for reproducibility):
+
+```sh
+export PGLITE_REF='ghcr.io/di-framework/pglite-component@sha256:8bc30505cf28b1a65f72588da692d2ba3d79a6a2025c9256341a8625967a3286'
+wash oci pull "${PGLITE_REF}" pglite.wasm
+wac plug --plug pglite.wasm path/to/app.wasm -o path/to/app.composed.wasm
+mkdir -p ./data
+wasmtime run --dir ./data::/data path/to/app.composed.wasm
+```
+
+Consumers (like cli-extensions) pin the component by digest.
+
+That invocation is for a command component; serve HTTP components using your
+normal host while granting the same filesystem preopen. The final component
+requires WASI filesystem, clocks, streams, CLI and randomness interfaces, plus
+standardized WebAssembly exception handling for PostgreSQL error recovery.
+
+The public interface retains `exec`, `run`, `query`, `first`, transactions,
+savepoints, `rows-affected`, `close`, and `server-version`. PostgreSQL parameters
+use `$1`, `$2`, etc. Text parameters are sent with OID 0 (unknown type), allowing
+PostgreSQL to infer the type from context; comparisons against `uuid`, `timestamptz`,
+and `jsonb` columns work correctly (see Typed values). `server-version()` reports the bundled engine without
+opening a database. Only the `template1` database is currently supported;
+other `open-options.database` values are rejected. Requests must fit the engine's
+input buffer; each serialized result is limited to 64 MiB and stays in memory.
+Larger results return a PostgreSQL program-limit error. Signal-based statement
+timeouts are unavailable in this WASI engine: nonzero `statement-timeout-ms`
+options fail explicitly. Use host execution limits for runaway queries.
+
+## `SqlDatabase` adapter
+
+`createWasmPgliteDatabase` adapts the `di-framework:pglite/database@0.2.0`
+import to the `SqlDatabase` contract of `@di-framework/repo`, so repositories
+and migrations run on embedded PostgreSQL. Compose your component with this
+provider (see above). The adapter is portable: it uses only
+`node:async_hooks`, which the framework's component toolchain shims.
+
+```ts
+import type { SqlDatabase } from '@di-framework/repo';
+import { createWasmPgliteDatabase } from '@di-framework/pglite-component';
+
+// The database root is yours to choose. An empty path selects /data/pglite.
+const db: SqlDatabase = await createWasmPgliteDatabase('/data/identity');
+
+await db.exec('CREATE TABLE IF NOT EXISTS users (id uuid PRIMARY KEY, email text UNIQUE, meta jsonb)');
+await db.transaction(async (tx) => {
+  await tx.run('INSERT INTO users (id, email, meta) VALUES (?, ?, ?)', [id, email, { plan: 'free' }]);
+});
+const user = await db.first<{ email: string; meta: { plan: string } }>(
+  'SELECT email, meta FROM users WHERE id = ?',
+  [id],
+);
+```
+
+The provider allows one open connection per component instance. Keep one
+handle and share it: every call goes through one async mutex.
+
+- **Transactions.** `transaction(fn)` runs the provider's `begin` and `commit`, and `rollback` when `fn` throws. Statements issued from inside `fn`, through the callback view or the outer handle, join the transaction; other tasks wait for it. Inside `fn`, prefer the callback view: while the transaction is open it joins from any async context, including a worker loop or `AsyncResource` created earlier, and Wasm-guest code that the `node:async_hooks` shim does not instrument (native async generators). The outer handle joins only from `fn`'s own async context. From any other context it waits for the mutex, so awaiting it from `fn` deadlocks. A nested `transaction()` opens a savepoint. When it throws, only its own work rolls back, and the outer transaction can continue. Its work commits only with the outer transaction. Sibling savepoints started concurrently run one at a time. A plain statement issued through a view while a sibling savepoint is open joins that savepoint and rolls back with it: in `Promise.all([tx.transaction(failing), (async () => { await work(); await tx.run(...); })()])`, a `run` issued while the savepoint is open lands inside it, so await the savepoint first when the statement must survive it. Statements issued concurrently inside one transaction reach the connection one at a time, also with bindings that return promises. `transaction()` on a view, called from another async context while a sibling savepoint is open, waits for that sibling to finish; if the sibling awaits that call, it waits forever. Joining lasts only while a transaction is open. A savepoint's callback view kept after the savepoint returns joins the nearest open ancestor while the root transaction is still open, and its work commits or rolls back with that ancestor. Once the root transaction has ended, a retained callback view, like a timer scheduled inside `fn`, waits for the mutex like any other caller and never runs inside another task's transaction.
+- **Placeholders.** `?` placeholders become `$1`, `$2`, ... in order (`toPgPlaceholders`). The rewrite skips `'...'` and `E'...'` strings, `"..."` identifiers, `$tag$...$tag$` bodies, `--` and `/* */` comments, and the jsonb operators `?|` and `?&`. Because of that, `?||` reads as `?|` followed by `|`: put a space in the concatenation (`? || 'x'`). The bare jsonb `?` operator looks like a placeholder: use `jsonb_exists(col, ?)` in a statement with parameters. A statement run without parameters is not rewritten. You can write `$n` yourself, but do not mix `$n` with `?` in one statement.
+- **Parameters.** `string` is sent as text, and PostgreSQL infers its type from context, so a UUID or timestamp string works against `uuid` and `timestamptz` columns. A safe integer is `int8`, another number is `float8`, a `boolean` is `bool`, and `Uint8Array`, `ArrayBuffer` and typed arrays are `bytea`. A `Date` is sent as an RFC 3339 timestamp. Plain objects and arrays are sent as JSON, so a JavaScript array is not a PostgreSQL array: pass a literal such as `'{a,b}'`. A `bigint` outside the safe integer range is sent as decimal text, so it is not rounded. A `number` that is an integer outside the safe range throws a `TypeError`, because it has already lost precision: pass a `bigint` or a decimal string for `int8`. NaN and Infinity are valid `float8` values and are sent as `real`.
+- **Results.** Values match the `wasmcloud:postgres` codec in `@di-framework/repo`, so repositories behave the same on both backends. `json` and `jsonb` are parsed. `timestamptz` is an ISO string with milliseconds (`2024-01-15T10:30:00.123Z`, microseconds truncated); `infinity` and BC dates are returned as PostgreSQL prints them. An `int8` outside the safe integer range is a decimal string, but only when the binding lifts WIT `s64` as a `bigint`; a binding that lifts it as a JavaScript number (componentize-qjs lowers `s64` from numbers) has already lost the precision, so cast large `int8` columns to `text` in the query (`id::text`) when exact values matter (#153). `bool` is a boolean, `bytea` is a `Uint8Array`, and `timestamp` without zone, `date`, `uuid`, `numeric` and arrays are strings.
+- **Errors.** Failures throw `WasmPgliteError` with the WIT `tag`. A PostgreSQL error keeps its SQLSTATE in `error.code` (`'23505'` for a unique violation), and the message starts with `PostgreSQL <code>`, so `isUniqueViolation` from `@di-framework/repo` works too.
+
+Pass `module` or `loadModule` to supply the interface yourself (for tests), and
+`database` or `statementTimeoutMs` to forward `open-options`.
+`createSqlDatabaseFromWasmPgliteConnection` wraps a connection you have already
+opened.
+
+The adapter's view of the import is typed by `js/wit.d.ts`, generated from
+`wit/world.wit` by `bun scripts/wit-types.ts`. After changing the WIT, rerun it;
+the tests and `build:adapter` fail while the file is stale, and the typecheck
+fails when the WIT no longer fits the adapter. That check covers method names,
+arity and result types, not parameter variants: removing or narrowing a `value`
+case is not caught (TODO #153).
+
+## Typed values (0.2.0+)
+
+Every `open` pins `DateStyle=ISO` and `TimeZone=UTC` (set in the startup packet and re-applied
+on each open, since `close` runs `DISCARD ALL`), so text output is deterministic. Result mapping by
+PostgreSQL type:
+
+| PostgreSQL type | `value` variant | Format |
+| --- | --- | --- |
+| `bool` | `boolean` | |
+| `int2`, `int4`, `int8` | `integer` | `int8` is `integer` (`s64`); node-pg returns a string |
+| `float4`, `float8` | `real` | |
+| `bytea` | `blob` | |
+| `json`, `jsonb` | `json` | JSON text; `jsonb` is re-rendered by PostgreSQL (`{"a": 1}`) |
+| `timestamptz` | `timestamp` | RFC 3339 in UTC, e.g. `2024-01-15T10:30:00Z`, fractional seconds kept (`...:00.123Z`). `infinity` and `-infinity` are returned as those literals; BC dates are returned unmodified (`0044-03-15 00:00:00+00 BC`) |
+| `timestamp` (no zone) | `text` | `2024-01-15 10:30:00` (ISO, space separator, no offset). Deliberately not `timestamp`, which always denotes an instant |
+| `date` | `text` | `2024-01-15` |
+| `uuid`, `numeric` | `text` | canonical PostgreSQL text (`12.50` keeps its scale) |
+| arrays | `text` | PostgreSQL array literal, e.g. `{a,b}` |
+| everything else | `text` | |
+
+Parameters are typed as follows. `integer`, `real`, `boolean` and `blob` are
+sent as `int8`, `float8`, `bool` and `bytea`. `text`, `json` and `timestamp`
+are all sent with OID 0 (unknown), so PostgreSQL infers the type from context:
+a `json` parameter works against `json` and `jsonb` columns and with `jsonb`
+operators (`@>`, `=`), and a `timestamp` parameter against `timestamptz` and
+`timestamp` columns. Send RFC 3339 for `timestamp`; any string PostgreSQL
+accepts for the inferred type works.
+
+Column type OIDs are not exposed: adding them to `row` would change its shape
+and break every existing consumer, and the variants above plus Text for the
+rest cover the adapters' needs. A separate additive API can be added later.
+
+### Migrating from 0.1.0
+
+Bump consumers and composition pins to `di-framework:pglite/database@0.2.0`
+(the `value` variant gained cases, so 0.1.0 bindings do not link). Text
+parameters were previously sent as `text` (OID 25); they are now OID 0. That
+fixes `uuid = $1`, `timestamptz < $1` and `jsonb @> $1`, but PostgreSQL can no
+longer type a parameter that has no context: `SELECT $1 IS NULL` now fails with
+`could not determine data type of parameter $1`. Add a cast, for example
+`SELECT $1::text IS NULL`.
+
+Error mapping changed: undefined table (42P01), undefined column (42703) and
+every other class-42 code except 42601 (syntax error) and 42P18 (un-inferable
+parameter type) moved from `invalid-sql` to `execution-failed`. Branch on
+`pg-error.code` instead of the variant for those cases.
+
+Error handling surfaces SQLSTATE codes through `error.code`, enabling
+machine-readable handling of constraint violations and other conditions:
+- `"23505"` = unique violation
+- `"22012"` = division by zero
+- `"54000"` = result too large
+
+## Persistence and ownership
+
+For an `open("/data/orders", ...)` call:
+
+- `/data/orders/data/` is PGDATA (catalogs, tables, WAL and configuration).
+- `/data/orders/runtime/` contains bundled initialization/support files.
+- Bootstrap and shared-memory scratch files also stay beneath `/data/orders`.
+
+Mount the entire root on persistent storage and reuse it after restarts.
+Initialization creates the cluster once; later starts reuse it. Incomplete
+clusters or an incompatible PostgreSQL major version are rejected.
+`fsync`, `synchronous_commit`, and `full_page_writes` are enabled before the
+backend starts. The host filesystem must honor WASI sync operations; a local
+restart test is not a power-loss durability certification.
+
+**Give each database directory one component owner at a time.** The provider
+rejects a second simultaneous connection within its component instance. Close
+or drop rolls back uncommitted work, resets session settings, and allows the
+same root to be reopened. A component instance stays bound to its first root;
+use another instance for a different database.
+
+There is no cross-instance filesystem lock in this WASI implementation. The
+host must serialize access to each directory, including request instances and
+rolling replacements. A single replica alone does not prevent concurrent
+request instances from sharing files. Do not mount one root into overlapping
+instances or replicas. Fatal engine traps require a new component instance.
+
+For the framework's platform-managed storage, annotate the WorkloadDeployment:
+
+```yaml
+metadata:
+  annotations:
+    di-framework.dev/persistent-storage: "true"
+    di-framework.dev/storage-mount: /data
+```
+
+The platform controller mounts the workload's persistent directory and grants
+its components the matching WASI preopen. Use a stable workload identity on
+redeploy and configure exclusive execution for this database. These
+annotations provide storage; they do not enforce database ownership.
+
+## Implementation
+
+- `js/adapter.ts`: the `SqlDatabase` adapter published on npm (`bun run build:adapter`).
+- `js/wit.d.ts`: generated TypeScript view of the `database` interface.
+- `src/lib.rs`: public WIT resources and connection lifecycle.
+- `src/pgwire.rs`: PostgreSQL message encoding and typed rows, over memory.
+- `src/engine.rs`: persistent filesystem setup and exclusive engine access.
+- `engine/bridge.wat`: private canonical ABI bridge to the core engine.
+- `scripts/prepare-engine.ts`: pinned engine preparation and componentization (all build scripts are Bun TypeScript; see `scripts/`).
+- `wit/deps/pglite-engine/engine.wit`: internal interface, composed away at build.
+
+Engine provenance and modifications are described in `engine/NOTICE`.

package/dist/BUILD-INFO.txt

@@ -0,0 +1,13 @@
+component:       di-framework:pglite@0.2.0
+profile:         release
+built:           2026-10-12T04:34:54Z
+rustc:           rustc 1.97.1 (8bab26f4f 2026-07-14)
+target:          wasm32-wasip2
+wasm-tools:      wasm-tools 1.258.0 (5c6d31c78 2026-08-24)
+wit-bindgen:     0.61.1
+md5:             0.7.0
+engine:          PostgreSQL 17.5, persistent WASI filesystem
+engine-source:   https://github.com/moznion/wasipg/tree/fa290be67946c0d3c4540bd1400b11e193d874e1
+adapter-sha256:  e51dd61669a20daca34befe7fdadf1ac84e4795a2c84a8400818ee1de5373ccc
+engine-sha256:   b4d513111988a9494ff506c57164762cae91d08c9e80ffdf10f349e5c7f24d7a
+size:            17990191 bytes

package/dist/SHA256SUMS

@@ -0,0 +1,4 @@
+e8681fc6d6099b33b57e9a63ed72622fa2796fc76c86a4087b6c72c2d8453892  di-framework-pglite.wasm
+6053154ec1bc94de63ce4f4f4cce5922ef57dce794c2dde326f5845b8982d35f  di-framework-pglite.wit
+eac0414a2dd37c0a5ff904037d65a07aa0328fa8ccc2dcd77b7efd870b9425da  BUILD-INFO.txt
+0b8bbbe8aa2898431d20371148a445c9b1ecdecb2ca81d3c98d43256f650590e  THIRD-PARTY-NOTICES.txt