@coxmos/adapter-edge 0.0.1 → 0.0.2

package/README.md

@@ -2,21 +2,6 @@
 
 SvelteKit adapter targeting coxmos-edge's Deno-isolate runtime.
 
-## ⚠️ Verification status (read this first)
-
-Parts of this adapter are confirmed against real SvelteKit source and
-docs; one part is not yet confirmed and is clearly marked in the code.
-
-**Confirmed** (fetched and read directly from `sveltejs/kit`,
-`packages/adapter-node/index.js`, plus SvelteKit's own docs and a real
-GitHub issue showing `adapter-cloudflare`'s actual compiled output):
-- The `Adapter` interface shape (`{ name, async adapt(builder) }`)
-- The real list of `Builder` methods available (`writeClient`,
-  `writeServer`, `writePrerendered`, `generateManifest`,
-  `getBuildDirectory`, `rimraf`, `mkdirp`, etc.)
-- That a fetch-handler-style adapter output (`{ fetch(req) {...} }`) is
-  a real, existing pattern in SvelteKit's adapter ecosystem — this is
-  the right target shape for a Deno isolate.
 
 **Not yet confirmed** — flagged directly in `files/entry.js`:
 - The exact glue between `builder.generateManifest()`'s output and
@@ -25,13 +10,6 @@ GitHub issue showing `adapter-cloudflare`'s actual compiled output):
   reconstructed from public patterns, not fetched line-for-line from
   adapter-node's actual internal wiring.
 
-**Before deploying this anywhere real**: build a minimal SvelteKit app
-with this adapter, inspect the real output in `.coxmos/edge/server/`,
-and confirm the `entry.js` glue code actually matches what SvelteKit
-generated. See the comment block at the top of `files/entry.js` for
-exactly what to check — there's a real chance SvelteKit's own generated
-server output already does most of the `Server` wiring for you, which
-would let you simplify `entry.js` down to just the outer fetch wrapper.
 
 ## Usage
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@coxmos/adapter-edge",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "SvelteKit adapter for coxmos-edge (Deno isolate runtime). UNVERIFIED beyond Builder API surface - see index.js header before using in production.",
   "publishConfig": {
     "access": "public"