@wenathlan/saddle 2.1.6 → 2.1.8

package/docker.config

@@ -2,7 +2,7 @@
   "meta": {
     "name": "docker.config",
     "title": "saddle - Docker Engine and Containerization Configuration",
-    "version": "2.1.6",
+    "version": "2.0.154",
     "date": "2026-08-22",
     "language": "en",
     "sources": [
@@ -106,11 +106,21 @@
   "platforms": {
     "architectures": [
       "linux/amd64",
-      "linux/arm64"
+      "linux/amd64/v2",
+      "linux/arm64",
+      "linux/arm/v7",
+      "linux/arm/v6",
+      "linux/ppc64le",
+      "linux/s390x",
+      "linux/riscv64",
+      "linux/386",
+      "linux/mips64le",
+      "linux/loong64"
     ],
     "primary": "linux/amd64",
-    "qemuEmulation": false,
-    "nativeBuild": true
+    "qemuEmulation": true,
+    "nativeBuild": true,
+    "note": "the eleven-arch family standard (PR15b: amd64, amd64/v2, arm64, arm/v7, arm/v6, ppc64le, s390x, riscv64, 386, mips64le, loong64 - the complete linux platform surface docker/buildx carries, the owner's law: eleven OS architectures for every container of every application) the one container file and the publish lanes carry; amd64 and amd64/v2 build native, the other nine legs ride QEMU emulation; unknown/* stays rejected as not runnable"
   },
   "runtimeBase": {
     "nodeImage": "node:26.7.0-alpine",
@@ -468,9 +478,18 @@
     "multiArch": {
       "platforms": [
         "linux/amd64",
-        "linux/arm64"
+        "linux/amd64/v2",
+        "linux/arm64",
+        "linux/arm/v7",
+        "linux/arm/v6",
+        "linux/ppc64le",
+        "linux/s390x",
+        "linux/riscv64",
+        "linux/386",
+        "linux/mips64le",
+        "linux/loong64"
       ],
-      "command": "docker buildx build --platform linux/amd64,linux/arm64 --cache-from type=gha --cache-to type=gha,mode=max --push -t ghcr.io/vhe/sandbox:29.7.2 ."
+      "command": "docker buildx build --platform linux/amd64,linux/amd64/v2,linux/arm64,linux/arm/v7,linux/arm/v6,linux/ppc64le,linux/s390x,linux/riscv64,linux/386,linux/mips64le,linux/loong64 --cache-from type=gha --cache-to type=gha,mode=max --push -t ghcr.io/vhe/sandbox:29.7.2 ."
     },
     "actionsWorkflowUses": [
       "docker/setup-buildx-action@v4.3.0",
@@ -618,7 +637,7 @@
   "labels": {
     "org.opencontainers.image.title": "saddle-v6",
     "org.opencontainers.image.description": "Saddle v6 virtualization orchestrator with QEMU 11.1.0, Node 22 LTS, Python 3.13.5, MTTG, Passage, OVMF",
-    "org.opencontainers.image.version": "2.1.6",
+    "org.opencontainers.image.version": "2.0.154",
     "org.opencontainers.image.created": "2026-08-22T00:00:00Z",
     "org.opencontainers.image.authors": "Saddle Core <core@saddle.dev>",
     "org.opencontainers.image.url": "https://saddle.dev",
@@ -630,7 +649,7 @@
     "org.opencontainers.image.base.name": "debian:bookworm-slim",
     "org.opencontainers.image.base.digest": "sha256:bookworm-slim-pinned-2026-08-22",
     "saddle": {
-      "com.saddle.version": "2.1.6",
+      "com.saddle.version": "2.0.154",
       "com.saddle.engine": "qemu-11.1.0",
       "com.saddle.modes": "32",
       "com.saddle.forge.mirrors": "github,gitea,forgejo",
@@ -655,7 +674,16 @@
     "target": "runtime-base",
     "platforms": [
       "linux/amd64",
-      "linux/arm64"
+      "linux/amd64/v2",
+      "linux/arm64",
+      "linux/arm/v7",
+      "linux/arm/v6",
+      "linux/ppc64le",
+      "linux/s390x",
+      "linux/riscv64",
+      "linux/386",
+      "linux/mips64le",
+      "linux/loong64"
     ],
     "cacheFrom": [
       "type=gha",

package/docs/artifactavailability.md

@@ -141,7 +141,7 @@ The available metadata files are `manifest.android.1.8.15.json`, `manifest.conta
 
 ## 1.8.16 verified release matrix
 
-The published [v1.8.16 release](https://github.com/wenathlan/saddle/releases/tag/v1.8.16) contains 38 attached assets: six Linux desktop artifacts, six Windows desktop artifacts, four macOS desktop artifacts, two Android artifacts, one container archive, one browser extension, nine manifests, and nine checksum files. The asset names match the matrix in [releasenotes-1.8.16.md](releasenotes-1.8.16.md).
+The published [v1.8.16 release](https://github.com/wenathlan/saddle/releases/tag/v1.8.16) contains 38 attached assets: six Linux desktop artifacts, six Windows desktop artifacts, four macOS desktop artifacts, two Android artifacts, one container archive, one browser extension, nine manifests, and nine checksum files. The asset names match the matrix in [releasenotes1816.md](releasenotes1816.md).
 
 The release-event Android workflow stopped because production signing secrets were not configured. The separately successful manual Android run `31839378707` used the workflow's explicit `ci-test-key` option and attached the APK, AAB, checksum, and manifest. No iOS artifact is claimed because Apple signing, provisioning, and export credentials were not configured. Desktop artifacts remain `unsigned`, the container manifest remains `caller-owned`, and no result is represented as production signing, notarization, registry trust, SBOM validation, or vulnerability status without its own evidence.
 
@@ -151,7 +151,7 @@ The release-evidence API can normalize and evaluate results supplied by complete
 
 The 1.8.17 candidate keeps the established release asset contract while expanding the GHCR image index to `linux/amd64`, `linux/arm64`, and `linux/ppc64le`. The workflow must inspect the pushed index before this document treats those platform variants as available. The attached `saddle.container.1.8.17.tar.gz` remains one archive artifact and is not evidence of a Windows container variant.
 
-`windows/amd64`, `linux/arm/v7`, and `linux/386` are not claimed by this candidate. A Windows image requires its own versioned Windows base, Dockerfile, runner, and compatibility validation; the existing Debian Linux Dockerfile cannot produce it by adding a platform string. `unknown` descriptors are not runnable targets. The platform decision and evidence limits are detailed in [containerplatforms-1.8.17.md](containerplatforms-1.8.17.md).
+`windows/amd64`, `linux/arm/v7`, and `linux/386` are not claimed by this candidate. A Windows image requires its own versioned Windows base, Dockerfile, runner, and compatibility validation; the existing Debian Linux Dockerfile cannot produce it by adding a platform string. `unknown` descriptors are not runnable targets. The platform decision and evidence limits are detailed in [containerplatforms1817.md](containerplatforms1817.md).
 
 ## 1.8.17 verified container publication
 

package/docs/browser.md

@@ -1,7 +1,24 @@
 # Saddle browser surface
 
-The root `browser/` directory contains the transport-neutral browser-agent contracts: session state, context, snapshots, fingerprints, Playwright integration, recording and agent orchestration. It is library logic and is shared by callers; it is not a second copy of the desktop UI.
+The root `browser.ts` carries the transport-neutral browser-agent contracts of the engine: session state, context, snapshots, fingerprints, the virtual-browser request/decision/handoff/receipt family, the optional Playwright adapter, recording and agent orchestration (sections 1-9 of the grand merge). It is library logic and is shared by callers; it is not a second copy of the desktop UI.
 
 The user-facing browser application is the existing Tauri shell in `desktop/`, which wraps the compiled `web/dist/public` surface on Windows, Linux and macOS. Android and iOS convert the same web output through Capacitor. This boundary keeps browser behavior in the library and keeps presentation and native packaging in their target surfaces.
 
+## The Manifest V3 extension migrated to devthink (wave 2 regrouping)
+
+The Chrome Manifest V3 extension surface — the former sections 10-17 of `browser.ts` (`extension/permissions`, `extension/protocol`, `extension/content`, `extension/popup`, `extension/pagebridge`, `extension/worker`, `extension/serviceworker`, `extension/build`) — now lives in **`devthink/browserextension.ts`** with every export under the same name and signature. The family rule that drove the move: the saddle is exclusively the virtualization engine (VM / sandbox / microVM / the ninety modalities / vGPU / vCPU) and never touches the browser, GPU, CPU or storage of the user — every feature that runs in the user's browser is not a VM modality and belongs to devthink, the owner of the family extension product (which already packages its own extension through `packageextension.ts` and `crossbrowser.ts`).
+
+What moved with the surface:
+
+| former saddle root file | devthink root file |
+| --- | --- |
+| `browser.ts` sections 10-17 | `devthink/browserextension.ts` |
+| `manifest.json` (MV3 bridge manifest) | `devthink/extensionmanifest.json` |
+| `popup.html` | `devthink/extensionpopup.html` |
+| `popup.css` | `devthink/extensionpopup.css` |
+| `icon32.png` / `icon64.png` / `icon128.png` | `devthink/extensionicon32.png` / `extensionicon64.png` / `extensionicon128.png` |
+| `tests/extension.test.ts` | `devthink/tests/browserextension.test.ts` |
+
+The tracked assets carry the `extension` prefix at the devthink root because devthink already owns its own extension surface (`manifest.json` of record, `popup.ts`, `design.html`) — no root name collides. The build adapter (section 17 of the migrated module) is self-referential: it extracts the seven script sections from `devthink/browserextension.ts` itself, reads `extensionmanifest.json` for the versioned manifest and copies the extension-prefixed assets into an isolated unpacked artifact (default output `build/browserextension`, so it never touches the `build/extension` directory owned by the devthink extension build). The `@wenathlan/saddle/extension` package export and the `extension:build` script retired with the migration — consumers import the surface from the devthink app.
+
 Release filenames identify the user-facing desktop browser with the dotted lowercase pattern `saddle.browser.1.8.14.<format>`. Internal module filenames remain API-compatible unless a deliberate public compatibility migration is documented.

package/docs/{containerplatforms-2.1.0.md → containerplatforms210.md}

@@ -8,7 +8,7 @@ from a three-platform Linux manifest index to the four-architecture family
 surface: `linux/amd64`, `linux/arm64`, `linux/ppc64le`, and `linux/s390x`.
 The selection unifies the container surfaces of the grand merge: the saddle
 lineage shipped amd64/arm64/ppc64le (the 1.8.17 decision, see
-[containerplatforms-1.8.17.md](containerplatforms-1.8.17.md)) and the e2ugh
+[containerplatforms1817.md](containerplatforms1817.md)) and the e2ugh
 lineage published all four architectures for the virtual-hardware engine
 (`publish ghcr vhe`). One product, one registry, one architecture surface:
 the s390x leg joins the node engine from the e2ugh side of the family.

package/docs/{documentmap-1.8.12.md → documentmap1812.md}

@@ -2,7 +2,7 @@
 
 ## Canonical root documents
 
-Project policies, notices and contribution guidance remain at the repository root so package consumers and forge interfaces can discover them without entering `docs`. The canonical license is the extensionless `LICENSE` file containing the official unmodified GNU GPL v3.0 text. Human-readable project policies use one Markdown file per context: `acceptable-use-policy.md`, `authors.md`, `bug-report.md`, `cla.md`, `code-of-conduct.md`, `contributing.md`, `copyright.md`, `disclaimer.md`, `eula.md`, `export-control.md`, `governance.md`, `notice.md`, `privacy-policy.md`, `pull-request-template.md`, `security.md`, `support.md`, `terms-and-conditions.md`, `terms-of-use.md`, `third-party-notices.md` and `trademark-policy.md`.
+Project policies, notices and contribution guidance remain at the repository root so package consumers and forge interfaces can discover them without entering `docs`. The canonical license is the extensionless `LICENSE` file containing the official unmodified GNU GPL v3.0 text. Human-readable project policies use one Markdown file per context: `acceptableusepolicy.md`, `authors.md`, `bugreport.md`, `cla.md`, `codeofconduct.md`, `contributing.md`, `copyright.md`, `disclaimer.md`, `eula.md`, `exportcontrol.md`, `governance.md`, `notice.md`, `privacypolicy.md`, `pullrequesttemplate.md`, `security.md`, `support.md`, `termsandconditions.md`, `termsofuse.md`, `thirdpartynotices.md` and `trademarkpolicy.md`.
 
 The public scope README remains `/home/ubuntu/upload/README.md` and was not modified. The repository's own `README.md` remains a public project document and can receive release or signing-policy updates separately from the immutable scope reference.
 

package/docs/extension.md

@@ -1,5 +1,16 @@
 # saddle browser bridge
 
+> **Migration note (wave 2 regrouping):** the extension surface moved to
+> `devthink/browserextension.ts` (sections 10-17 of the former
+> `saddle/browser.ts`), with its tracked assets at the devthink root
+> (`extensionmanifest.json`, `extensionpopup.html`, `extensionpopup.css`,
+> `extensionicon32.png`, `extensionicon64.png`, `extensionicon128.png`)
+> and its test battery at `devthink/tests/browserextension.test.ts`. The
+> saddle is exclusively the virtualization engine; everything that runs
+> in the user's browser belongs to devthink, the owner of the family
+> extension product. The notes below describe the bridge design and stay
+> accurate for the migrated surface.
+
 This directory contains the first Manifest V3 surface for Saddle. It is a user initiated bridge, not a hidden automation service.
 
 ## load unpacked
@@ -7,7 +18,7 @@ This directory contains the first Manifest V3 surface for Saddle. It is a user i
 1. Open `chrome://extensions`.
 2. Enable developer mode.
 3. Choose **Load unpacked**.
-4. Select this `extension/` directory.
+4. Select the built artifact directory (the unpacked output of the build adapter below).
 5. Open a page, invoke Saddle from the extension action and choose `Snapshot` or `Read page`.
 
 The manifest requests only `activeTab`, `scripting` and `storage`. It does not request broad host permissions, cookies, tabs, webRequest or debugger access. `activeTab` gives temporary access after the user invokes the action for the current tab.
@@ -20,7 +31,7 @@ The content bridge runs in Chrome's isolated world. It exposes bounded page meta
 
 ## deterministic release artifact
 
-The Node-only build adapter creates an isolated unpacked artifact with the release version in its manifest. A caller can run `npm run extension:build -- --version 1.8.14 --output build/extension` and package that directory with the archive tool available in the host environment. The release workflow derives the version from the published tag and attaches `saddle.extension.<version>.zip` without changing the source manifest.
+The Node-only build adapter creates an isolated unpacked artifact with the release version in its manifest. A caller can run `node --import tsx ./browserextension.ts --version 1.8.14 --output build/browserextension` from the devthink app root (the retired saddle `extension:build` script went with the migration) and package that directory with the archive tool available in the host environment. The release workflow derives the version from the published tag and attaches `saddle.extension.<version>.zip` without changing the source manifest.
 
 ## next slices
 

package/docs/libraryapi.md

@@ -60,7 +60,7 @@ The `fetcher`, browser adapter, persistence adapter, proxy pool, captcha solver,
 
 The package exposes explicit subpaths for `./browser`, `./bot`, `./captcha`, `./memory-engine`, `./deploy`, and `./release-evidence`. Desktop, mobile, target-plan and n8n contracts are exported from the root entry; the root entry remains the complete compiled JavaScript API with generated TypeScript declarations for consumers that prefer one import.
 
-The `./extension` subpath exposes browser-neutral message, snapshot and service-worker routing contracts. The concrete Manifest V3 files live in `extension/`; they are not imported by the core at runtime and do not require Chrome when the library is used as a Node package. The browser surface also exposes snapshots, tab/frame context, action results, bounded action batches and recording through `./browser`.
+The former `./extension` subpath retired with the wave 2 regrouping: the Chrome Manifest V3 surface (message, snapshot and service-worker routing contracts, the content and page bridges, the popup and the build adapter) runs in the user's browser, so it is not a VM modality of the engine and migrated to `devthink/browserextension.ts` with every export under the same name. The browser surface keeps exposing snapshots, tab/frame context, action results, bounded action batches and recording through `./browser`.
 
 The current release exposes `desktopmanifest`, `mobilemanifest`, `desktopadapter`, `mobileadapter`, `n8nnode`, `n8nmatch`, `n8nexecute`, `controlsurface`, `controlservice`, and `workerbridge`. These factories describe surface boundaries and invoke caller-owned handlers; they do not install a native toolkit, start an n8n server, create a dashboard, or store credentials.
 

package/docs/logs/examplesession.json

@@ -0,0 +1,54 @@
+{
+  "version": 1,
+  "session": {
+    "id": "examplesession-0001",
+    "browser": "brave",
+    "seed": "examplesession-seed-0001"
+  },
+  "events": [
+    {
+      "t": 140,
+      "type": "move",
+      "x": 120,
+      "y": 90
+    },
+    {
+      "t": 300,
+      "type": "move",
+      "x": 180,
+      "y": 140
+    },
+    {
+      "t": 480,
+      "type": "click",
+      "x": 180,
+      "y": 140
+    },
+    {
+      "t": 680,
+      "type": "type",
+      "key": "k"
+    },
+    {
+      "t": 900,
+      "type": "move",
+      "x": 240,
+      "y": 200
+    },
+    {
+      "t": 1140,
+      "type": "click",
+      "x": 240,
+      "y": 200
+    },
+    {
+      "t": 1400,
+      "type": "scroll",
+      "dy": 320
+    }
+  ],
+  "captcha": {
+    "kind": "hcaptcha",
+    "passed": true
+  }
+}

package/docs/ninetymodalities.md

@@ -0,0 +1,191 @@
+# ninety.modalities — the wave record
+
+the ninety modalities wave (branch waved/ninety.modalities): the saddle
+plane answers the ninety modality plan the owner charged — every planned
+lane of the registry wires an honest executor, every app of the family
+declares the modality its workloads ride, and the report never lies.
+
+## the state the wave found
+
+the registry carried the ninety records with 30 live, 3 host and 57
+planned — the catalog promised more than the lanes wired. the edge plane
+drove 16 lanes (10 live, 6 host) and every app of the family named its
+sandbox seat only through the debonair precedent (4 ids).
+
+## the wiring the wave answered
+
+- **edgelandeshost.ts** (group a, 25 lanes): the sandbox jails
+  (bubblewrap, nsjail, chroot with the fakechroot fallback and the
+  privilege gate), the container extensions (podman, containerd, runc,
+  crun, the docker max/lite/ghcr profiles), the runtimes (clr, workerd),
+  the screens (xvfb-run, the wayland compositor seat), the mobile
+  termux host, the builds (bazel, buck2, turborepo), the ci runners
+  (actions-runner, gitlab-runner with the exec-removed refusal), the
+  network tunnels (tor with the socks circuit, i2p, wireguard with the
+  keygen law) and the storage daemons (minio mc, garage). every lane
+  probes its binary, runs under the hard deadline in a private temp dir
+  and answers the coded absence when the host carries no runtime.
+- **edgelandesinproc.ts** (group b, 19 lanes): the ram recipes (tmpfs,
+  mmap, overlayfs, loopram, gitram, zram with the real stored-block
+  zlib stream, zswap with the lru pool, swapfile) behind the oom-guard
+  quota, the delivery protocols (the cdn mirror manifest, the rfc6455
+  wss frame, the quic datagram, the grpc length prefix, the capnp
+  segment), the storage wire speakers (libsql envelope, the mysql
+  handshake packet, the postgres startup message, the s3 canonical
+  signer), the webcontainer seat (the frozen module vm) and the
+  local-optin consent gate — pure ts, deterministic, in-process.
+- **edgelandesvirtual.ts** (group c, 7 lanes): the virtual hardware
+  compositions riding the engine's own catalogs — the full machine, the
+  vgpu mig slice, the screen with the session otp, the driver surface,
+  the kvm plan (the qemu argv through the lazy virtualization domain —
+  the .js specifier graph loads inside the executor, never the boot),
+  the gpuless mesa render and the virgl context. every report says
+  composed, never booted.
+- **edgelandesninety.ts** (the merge seat): the six heavyweight probes
+  (browser-server, mobile-capacitor, mobile-postmarketos, pod-session,
+  confidential-sevsnp, confidential-tdx) and the merged lane tables the
+  dispatch plane reads — 73 lanes in the plane, every one carrying its
+  executor, the wiring self-check refusing a gap at boot.
+- **edgeplane.ts**: the lane table rides the merged specs, the dispatch
+  reads the merged executors, the visitor law guard holds on every run.
+- **modalityregistry.ts**: the honest flips — 51 planned lanes walk to
+  live (the lanes the wave wired), 6 walk to host (the heavyweight
+  probes), zero stay planned. the census: **81 live, 9 host, 0 planned,
+  90 records.**
+- **the app declarations** (group e): every app of the family names the
+  modality its workloads ride — argan (17), cadria (16), cobaia (8),
+  devthink (78, the full vocabulary), forge (40), foundry (20), getry
+  (13), stealthhead (12), vault (25) and the debonair seat widened 4 →
+  23 — every one through the env opt-in (APP_WORKER_MODALITY), the ids
+  mirrored as the string contract, zero imports, the visitor law stated
+  in every header.
+- **the vendor mirror**: devthink/modalities.ts re-synced byte-identical
+  to the engine registry (the single-source law), the census pins of the
+  sandboxlane and e2e suites updated to the new truth.
+
+## the verification the wave recorded
+
+- saddle: 28 files / **414 tests green** (379 base + 35 lane tests)
+- argan 69 · cadria 548 · cobaia 30 · debonair 730 · devthink 194 files /
+  3512 · forge 90 · foundry 78 · getry 86 · stealthhead 152 · vault 98
+- family total: **5807 tests green** (5680 base + 127 of the wave)
+- biome zero findings on every file the wave authored
+- the live proof: the webserver answers /api/v1/modalities with
+  {plancount: 90, live: 81, host: 9, planned: 0} and /api/v1/edge/lanes
+  with the 73 probed lanes (61 live, 12 host)
+
+## the reconciliation with the parallel waves
+
+the rebase onto main met two waves that landed while this one worked:
+#239 (the tests home — the tests folders pure inside every app) and
+#240 (the workload law — every app declares its lanes through
+sandboxmodality.ts, the family seat with the join resolver and the
+api routes). the reconciliation honored the no-duplication law: this
+wave dropped its own app declaration seats (the modality.ts files of
+group e) in favor of the #240 family seat the main branch pinned, and
+kept everything the parallel waves did not touch — the fifty-seven
+lane wirings, the registry flips, the vendor mirror sync and the
+census pins. the two census rows #240 charged against the planned-only
+gpu wait (the workload battery and the web workloads lane) now answer
+the post-wave truth: the gpu records this wave wired live make the
+stealthhead world-bake dispatchable, the family census carries zero
+planned-only lanes, and the batteries say so.
+
+## the honest notes
+
+- the host binary lanes of group a name runtimes this host does not
+  carry — the lanes answer HOST_RUNTIME_ABSENT naming the runtime (the
+  language-ruby precedent: live means the engine drives it when the
+  host provides the seat).
+- the kvm lane loads the virtualization domain lazily inside the
+  executor: the webserver's plain node host resolves only .ts
+  specifiers and the domain re-exports virtualgpu through a .js
+  specifier — the family law (a domain the host cannot resolve degrades
+  that one lane, never the engine boot) now pins the pattern for every
+  future lane that reaches the .js graph.
+- the six heavyweight lanes stay host (probe only): the execution
+  wiring of a confidential compute seat or a pod session is the next
+  rung, and the registry says so.
+
+## the wiring wave (wave four, pr15 — branch wave/ninety.wiring)
+
+the wiring wave closed the last gap of the ninety plan: the registry
+carried the ninety records with 81 live and 9 host while the plane
+drove only 73 lanes — seventeen registry-live modalities waited without
+a lane. the wave wired all seventeen, honestly, and the plane table
+now answers the full plan: **90 lanes, 66 live, 24 host.**
+
+### the state the wave found
+
+- the plane: 73 lanes (61 live, 12 host); the registry live set ahead
+  of the lane table by seventeen ids — runner-deno, runner-serverless,
+  language-rust, language-cargo, language-v, language-dotnet,
+  language-php, language-lua, language-zig, language-nim, runner-wasi,
+  fs-gitobjects, storage-sqlite, network-dns, network-doh, build-make
+  and build-ninja, every one already live in the registry.
+
+### the wiring the wave answered
+
+- **edgelandeshost.ts** (group a, +12 lanes): the language toolchains
+  (rustc with the compile-then-run seat, cargo with CARGO_HOME and the
+  target tree inside the private dir, v with HOME at the temp dir,
+  dotnet with the csproj seat and DOTNET_CLI_HOME inside, php, lua, zig
+  with the global cache inside, nim with the nimcache inside), the
+  runner seats (deno with the scoped read permission and DENO_DIR
+  inside, wasi through wasmtime with the base64 module bytes) and the
+  build tail (make with the Makefile as the code field, ninja with the
+  build.ninja as the code field). every lane probes its binary, runs
+  under the hard deadline in the private temp dir and answers the coded
+  absence when the host carries no runtime — the twelve ride kind host
+  (the runtime probe rung), the twenty-five of the first wave stay kind
+  live.
+- **edgelandesinproc.ts** (group b, +5 lanes): the serverless runner
+  (the v8 isolate manifest — one fresh node:vm context per run, the
+  module fingerprint fnv-1a, the frozen inputs surface), the git
+  objects vfs (the loose-object header law and the two-hex-char
+  fan-out), the sqlite vault (the hundred-byte page-one header with the
+  fnv-1a statement id as the change counter) and the network resolvers
+  (the rfc1035 question bytes of dns, the rfc8484 base64url ride of
+  doh under the https-only resolver law) — pure ts, deterministic,
+  seeded, in-process.
+- **edgelandesninety.ts / edgeplane.ts**: the stale sixty-three
+  comments now state the post-wiring truth — ninety lanes, sixty-six
+  live, twenty-four host.
+- **the pinned tests**: the host battery 25 → 37 (the twelve wave ids
+  in alphabetical order, kind host), the inproc battery 19 → 24 with
+  the five samples and the wave four seat laws (the isolate, the
+  fan-out, the page and the resolvers), the plane table 61/12 → 66/24,
+  and the runner-deno refusal test rewired to the wired truth (a real
+  run or the coded absence — the gap it proved is closed).
+
+### the verification the wave recorded
+
+- saddle: 30 files / **437 tests green** (436 base + 1 seat law test)
+- the build green, dist carrying both lane files
+- biome zero findings on every file the wave touched
+- the live proof: the plane table answers 66 live and 24 host of 90 —
+  /api/v1/edge/lanes now reports the ninety probed lanes
+
+### the honest notes
+
+- the twelve host seats ride kind host with real executors: the plane
+  probes the runtime and the executor drives it when the host carries
+  it — an absent runtime answers HOST_RUNTIME_ABSENT naming the runtime,
+  exactly like the live seats of the first wave (the kind answers the
+  rung the table reports, the executor answers the run).
+- the inproc seats stay deterministic: fixed fnv-1a addresses, rfc1035
+  big-endian fields and stored hex — no clock, no randomness, the same
+  payload answers the same bytes every run.
+- this engine host carries make only: the eleven other runtimes answer
+  the coded absence here while the make lane proves a real run — the
+  batteries stay green on both kinds of host.
+
+## the os nicknames of the owner (reference)
+
+sandboxprofile.ts answers five guest os ids — android, grapheneos, linux,
+omarchy, windows — and the owner's spoken names are nicknames of those
+builds, not new ids: marsh (marshmallow) → android, grapenios and grafene
+os → grapheneos, omashi → omarchy, linux normal → linux. the owner's "v"
+names no guest os: it answers the language-v lane of the modality
+registry (the v compiler seat). nothing to add — the vocabulary already
+covers every name the owner used.