@wenathlan/saddle 2.0.155 → 2.0.159

package/README.md

@@ -30,8 +30,8 @@ domain modules land beside the saddle domains:
 | `scheduler.ts`, `compute.ts`, `performance.ts` | job queues, batch compute and benchmark planning |
 | `media.ts`, `render.ts`, `quantum.ts`, `tiers.ts` | media pipeline, GPU registry, quantum simulation, tier policy |
 | `security.ts`, `alternatives.ts` | hardening gates and the alternative-stack catalog |
-| `index.html`, `App.tsx`, `Sol/` | the single SPA shell and the Sol theme (one tsx app with one stylesheet per theme) |
-| `server.ts`, `sandbox.ts` | the zero-dependency self-hosted API of the 2.0.155 grand-merge envelope (`node server.ts`; the api answers its version at `/api/v1/health`) and the browser-pure engine port |
+| `index.html`, `App.tsx`, `sol/` | the single SPA shell and the Sol theme (one tsx app with one stylesheet per theme) |
+| `server.ts`, `sandbox.ts` | the zero-dependency self-hosted API of the 2.0.156 grand-merge envelope (`node server.ts`; the api answers its version at `/api/v1/health`) and the browser-pure engine port |
 | `vercel.json`, `netlify.toml` | the platform deploy adapters beside the surface they publish (the caddy ghost stays out of the tree) |
 | `specs/*` package exports | processors, gpus, cores, boards and the qemu/mttg/passage/docker envelopes |
 
@@ -282,7 +282,7 @@ intelligence.ts, modes.ts
                the saddle domain routing barrel files (bot, browser, delivery, integrations, profiles)
 server.ts, webserver.ts, api.ts, cli.ts
                the self-hosted api surfaces, the web console and the stable cli
-Sol/           the Sol theme — the platform's web surface (one tsx app, one stylesheet per theme)
+sol/           the Sol theme — the platform's web surface (one tsx app, one stylesheet per theme)
 specs          processors.json, gpus.json, cores.json, boards.json and the qemu/mttg/passage/docker/vm envelopes
 tests/         deterministic engine and extension coverage
 docs/          architecture, API, security, release and registry notes

package/biome.jsonc

@@ -23,9 +23,9 @@
       "!**/docs",
       "!**/tests/tmp",
       "!**/tests/code",
-      "!**/Sol/dist",
-      "!**/Sol/.vite",
-      "!**/Sol/node_modules",
+      "!**/sol/dist",
+      "!**/sol/.vite",
+      "!**/sol/node_modules",
       "!**/coverage",
       "!**/android",
       "!**/releasecheck",

package/docs/architecture1819.md

@@ -1,76 +1,39 @@
-# Saddle 1.8.19 architecture organization
+# architecture 1819
 
-## Objective
-
-This reorganization preserves every existing capability while making ownership and dependency direction easier to inspect. The root entry point remains a thin universal router. Public contracts remain additive and stable. Existing package subpaths remain compatible. Generated `dist/` output remains untracked.
-
-> A domain groups correlated behavior, contracts and tests. It is not a claim that unrelated code is removed or that an infrastructure adapter is activated.
-
-## Twenty correlated domains
-
-| ID | Domain | Current ownership | Allowed direction |
-| --- | --- | --- | --- |
-| 01 | Public surface | `index.ts`, `library/` | Re-exports domain façades only. |
-| 02 | Foundation | `core/` | Defines errors, identifiers, hashing, events and serializable nouns. |
-| 03 | Isolation policy | `isolation/`, API policy helpers | Evaluates approval, denial, handoff and receipt boundaries. |
-| 04 | Execution planning | `runtime/`, `runners/` | Plans and observes work through caller-owned adapters. |
-| 05 | Memory planning | `memory/` | Defines internal working-set, targets, transforms and bounded plans. |
-| 06 | Storage planning | `storage/` | Defines adapter-owned content, cache, chunk and synchronization contracts. |
-| 07 | Persistence | `persistence/` | Defines optional schema, migration and provider-neutral persistence adapters. |
-| 08 | Browser | `browser/`, `extension/` | Defines browser, virtual-browser, extension and session contracts without user-profile access. |
-| 09 | Acquisition | `scrape/`, `captcha/` | Defines request, crawl, extract, proxy and challenge contracts. |
-| 10 | Communication | `api/` | Defines authenticated envelopes, transports, rate policy and event serialization. |
-| 11 | External adapters | `adapters/` | Defines replaceable forge, socket, app and MCP adapters. |
-| 12 | Automation | `automation/`, `surfaces/` | Defines automation manifests, permissions, triggers and surface requirements. |
-| 13 | Intelligence | `ai/` | Defines token, chunk, retrieval, provenance and metric contracts. |
-| 14 | Binary handling | `binary/` | Defines archive, build and transformation plans without execution. |
-| 15 | Distribution | `packager/`, `release/` | Defines package, artifact, delivery, readiness and evidence contracts; filesystem-backed asset verification remains an explicit subpath. |
-| 16 | Modes | `modes/`, `server/` | Defines target modes, surface profiles and host-neutral service/deployment adapters; the Node server remains an explicit subpath only. |
-| 17 | Commands | `cli/` | Defines command parsing, presentation and command-level integration. |
-| 18 | Web application | `web/` | Defines static routes, UI components, visual assets and build boundaries. |
-| 19 | Native modes | `desktop/`, `android/`, `ios/`, `extension/` | Defines platform packaging metadata and calls library contracts. |
-| 20 | Quality and operations | `tests/`, `.github/`, `docs/` | Defines deterministic evidence, build checks, release operations and architecture records. |
-
-## Dependency flow
-
-![Rendered organization diagram](architecture-1.8.19.png)
+The architecture flowchart of the saddle engine layers (mermaid source, formerly architecture1819.mmd):
 
 ```mermaid
 flowchart TD
-  public[Public surface] --> foundation[Foundation]
-  public --> policy[Isolation policy]
-  public --> execution[Execution planning]
-  public --> memory[Memory planning]
-  public --> storage[Storage planning]
-  public --> browser[Browser]
-  public --> acquisition[Acquisition]
-  public --> communication[Communication]
-  public --> automation[Automation]
-  public --> intelligence[Intelligence]
-  public --> binary[Binary handling]
-  public --> distribution[Distribution]
-  public --> modes[Modes]
+  public[01 Public surface] --> foundation[02 Foundation]
+  public --> policy[03 Isolation policy]
+  public --> execution[04 Execution]
+  public --> memory[05 Memory]
+  public --> storage[06 Storage]
+  public --> persistence[07 Persistence]
+  public --> browser[08 Browser]
+  public --> acquisition[09 Acquisition]
+  public --> communication[10 Communication]
+  public --> integration[11 External adapters]
+  public --> automation[12 Automation]
+  public --> intelligence[13 Intelligence]
+  public --> binary[14 Binary]
+  public --> distribution[15 Distribution]
+  public --> modes[16 Modes]
+  public --> commands[17 Commands]
+  public --> web[18 Web application]
+  public --> native[19 Native modes]
+  public --> quality[20 Quality operations]
   foundation --> policy
   policy --> execution
-  memory --> storage
-  storage --> persistence[Persistence]
+  memory --> storage --> persistence
   acquisition --> browser
-  automation --> communication
-  execution --> adapters[External adapters]
-  browser --> adapters
-  communication --> adapters
-  binary --> distribution
-  modes --> surfaces[Commands, web and native modes]
-  distribution --> operations[Quality and operations]
-  surfaces --> operations
+  automation --> communication --> integration
+  execution --> integration
+  browser --> integration
+  binary --> distribution --> quality
+  modes --> commands
+  modes --> web
+  modes --> native
+  web --> quality
+  native --> quality
 ```
-
-The root may import only domain façades. Each façade may import its owned modules and lower-level contracts. Runtime, browser, storage, binary and remote-provider behavior remain adapter-owned: no domain may add implicit host, filesystem, browser-profile, network or provider effects.
-
-## Compatibility rules
-
-Existing module paths referenced by package exports remain valid. A module may be moved only after a compatibility shim or an equivalent export is in place, all relative imports are updated, and the package dry-run includes the expected output. Native mode metadata, workflow paths, CLI command paths and static web routing are release boundaries and therefore move only with corresponding validation.
-
-## Implementation order
-
-The first reorganization block groups the public root exports behind domain façades. The second groups adjacent library modules where no package subpath or native workflow depends on their exact location. The final block aligns tests and documentation with the same 20 domains. Each block must pass the engine build, active tests, legacy tests, formatting, package inspection, web checks and native-flat validation before the next block begins.

package/docs/features.md

@@ -0,0 +1,5 @@
+# saddle features
+
+## Dependencies
+
+- synchronized dependency union — the eleven family apps share one dependency tree: identical `dependencies`, `devDependencies` and `peerDependencies` (same keys, same versions, nothing removed, highest semver wins on conflicts) and one `engines` catalog with node as maestro and the V 0.5.2 seat as catalog annotation (@family wave/depssync).

package/index.ts

@@ -21,7 +21,7 @@ import { randomInt, randomUUID } from 'node:crypto';
 import { EventEmitter } from 'node:events';
 import { mkdirSync, readFileSync, writeFileSync } from 'node:fs';
 import { join } from 'node:path';
-import type { migprofileid } from './virtualmemory.ts';
+import type { migprofileid } from './virtual.ts';
 
 /* ------------------------------------------------------------------ */
 /* Section 1: reference versions                                       */
@@ -1446,18 +1446,12 @@ export {
   tmpfsrecipe,
   zramrecipe,
 } from './tiers.ts';
-/** Re-exports the virtual processor bank and cpuinfo generators. */
-export * from './virtualcpu.ts';
-/** Re-exports the gpu passthrough surface (vfio, rom dump, vgpu data). */
-export * from './virtualgpu.ts';
-/** Re-exports the virtualization surface (qemu turbo argv, passage,
- * mttg cgroups, mttg grid, checkpoint and restore, virtualizationcore
- * bridge). */
-export * from './virtualization.ts';
-/** Re-exports the MIG profile union declared by the memory module. */
-export type { migprofileid } from './virtualmemory.ts';
-/** Re-exports the memory tier catalog and virtual memory manager. */
-export * from './virtualmemory.ts';
+/* the virtual family fold (the edgelandes law, wave/virtualfold): the
+ * four arm modules — virtualcpu.ts, virtualgpu.ts, virtualization.ts and
+ * virtualmemory.ts — retired into the one keyword file virtual.ts, so
+ * their star re-exports retire with them: the `export * from
+ * './virtual.ts'` of the routing barrel below carries every one of their
+ * names (plus the MIG profile type union) through the single seat. */
 
 /* ── Section 2: the saddle domain routing barrel ── */