pi-outpost 0.40.3 → 0.42.0

package/dist/contract/README.md

@@ -231,7 +231,10 @@ with a raster fallback. That path does not cover structured-exchange documents,
 this section is about.)
 
 The markup stands on its own. Boxes are `rect` and `text` with colours as attributes
-and an explicit white ground, so what lands in the document is what was on screen. An
+and an explicit white ground, so what lands in the document is what was on screen in the
+light theme. In the dark theme the viewer paints each colour's night counterpart over those
+attributes, as a Mermaid diagram follows the theme, and the file still leaves with the light
+figure. An
 earlier version drew them as HTML inside `foreignObject`, which looks identical in the
 browser and loses everything the moment it is serialized.
 

package/dist/contract/validate-structured-exchange.mjs

@@ -14188,7 +14188,7 @@ function rulePatterns(profile, rules, sources) {
 }
 
 // shared/bin/validate-structured-exchange.mjs
-var VERSION = `validate-structured-exchange ${false ? "development" : "0.40.3"}`;
+var VERSION = `validate-structured-exchange ${false ? "development" : "0.42.0"}`;
 var USAGE = `validate-structured-exchange [file]
 validate-structured-exchange --profile <profile.json> [file]
 validate-structured-exchange --check-profile <profile.json>

package/dist/pi-outpost-tools.mjs

@@ -106635,7 +106635,7 @@ function measureAccepted(envelope, serialized) {
 }
 
 // ../server/src/terminalSandbox.ts
-import { closeSync, constants as fsConstants, existsSync, lstatSync, openSync, readdirSync } from "node:fs";
+import { closeSync, constants as fsConstants, existsSync, lstatSync, openSync, readdirSync, readFileSync, realpathSync } from "node:fs";
 var EXCLUSIVE_OPEN = fsConstants.UV_FS_O_EXLOCK ?? 268435456;
 
 // ../server/src/config.ts