@markii/bundle 0.3.0 → 0.4.0

package/README.md

@@ -1,5 +1,7 @@
 # @markii/bundle
 
-Bundle (`.mkbundle`) storage and policy handling for [Mark](https://github.com/sadigaxund/markii): manifest parsing/validation, a bundle-relative path-jail, the zip storage form (via `fflate`), a Node-only directory storage form (`./fs` subpath), and a capability-restricted script view. No React, no markdown parsing.
+Bundle (`.mkz`) storage and policy handling for [Markii](https://github.com/sadigaxund/markii): manifest parsing/validation, a bundle-relative path-jail, the zip storage form (via `fflate`), a Node-only directory storage form (`./fs` subpath), and a capability-restricted script view. No React, no markdown parsing.
+
+The legacy `.mkbundle` extension is still recognized for one more release; new bundles are always written as `.mkz`.
 
 See the [repository](https://github.com/sadigaxund/markii) for the format spec and the reference library as a whole.

package/dist/fs.js

@@ -116,7 +116,7 @@ async function resolveInsideRoot(rootAbs, relPath) {
  * Writes `data` to an already symlink-checked `target` that is known to
  * exist, refusing to write through a hard link (ESCAPE 3: `st_nlink > 1`
  * means some other path — possibly outside the bundle entirely, e.g.
- * `ln b.mkbundle/../victim.txt b.mkbundle/cache/hard` — refers to the exact same
+ * `ln b.mkz/../victim.txt b.mkz/cache/hard` — refers to the exact same
  * inode, so writing here would also silently modify that other path).
  *
  * Opens the file first *without* truncating (`'r+'`), `fstat`s the open

package/dist/script-view.d.ts

@@ -22,8 +22,9 @@ export interface ScriptView {
  * trust (their own note, a dev/test harness) — but it must always be an
  * explicit, named opt-in at the call site, never `createScriptView`'s
  * default. See the DEFECT-10 note on `createScriptView` for why: an
- * untrusted `.mkbundle` opened from elsewhere must never be able to grant
- * itself capabilities merely by declaring them in its own manifest.
+ * untrusted `.mkz` bundle (or its legacy `.mkbundle` counterpart) opened
+ * from elsewhere must never be able to grant itself capabilities merely by
+ * declaring them in its own manifest.
  */
 export declare function grantAllDeclaredPermissions(manifest: BundleManifest): BundlePermissions;
 /**
@@ -31,7 +32,7 @@ export declare function grantAllDeclaredPermissions(manifest: BundleManifest): B
  *
  * DEFECT 10 / spec §10: "Capabilities are declared in the manifest, granted
  * by the user" — declaring is not granting. `manifest.permissions` is
- * whatever the (possibly untrusted) `.mkbundle` *asks for*; `grantedPermissions`
+ * whatever the (possibly untrusted) `.mkz` bundle *asks for*; `grantedPermissions`
  * is whatever the user has actually *approved* for this note (e.g. via a
  * permission-prompt UI, remembered per note and re-prompted if scripts
  * change — see §10). The capability this view actually exposes is the

package/dist/script-view.js

@@ -7,8 +7,9 @@ import { isWriteAllowed } from './paths.js';
  * trust (their own note, a dev/test harness) — but it must always be an
  * explicit, named opt-in at the call site, never `createScriptView`'s
  * default. See the DEFECT-10 note on `createScriptView` for why: an
- * untrusted `.mkbundle` opened from elsewhere must never be able to grant
- * itself capabilities merely by declaring them in its own manifest.
+ * untrusted `.mkz` bundle (or its legacy `.mkbundle` counterpart) opened
+ * from elsewhere must never be able to grant itself capabilities merely by
+ * declaring them in its own manifest.
  */
 export function grantAllDeclaredPermissions(manifest) {
     return manifest.permissions ?? {};
@@ -18,7 +19,7 @@ export function grantAllDeclaredPermissions(manifest) {
  *
  * DEFECT 10 / spec §10: "Capabilities are declared in the manifest, granted
  * by the user" — declaring is not granting. `manifest.permissions` is
- * whatever the (possibly untrusted) `.mkbundle` *asks for*; `grantedPermissions`
+ * whatever the (possibly untrusted) `.mkz` bundle *asks for*; `grantedPermissions`
  * is whatever the user has actually *approved* for this note (e.g. via a
  * permission-prompt UI, remembered per note and re-prompted if scripts
  * change — see §10). The capability this view actually exposes is the

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@markii/bundle",
-  "version": "0.3.0",
-  "description": "Bundle (.mkbundle) storage and policy layer for Mark: manifest handling, the bundle-relative path-jail, zip (fflate) and Node directory storage forms, and a capability-restricted script view. No React, no parsing.",
+  "version": "0.4.0",
+  "description": "Bundle (.mkz, formerly .mkbundle) storage and policy layer for Markii: manifest handling, the bundle-relative path-jail, zip (fflate) and Node directory storage forms, and a capability-restricted script view. No React, no parsing.",
   "keywords": [
     "markdown",
     "mark",