@paged-media/plugin-sdk 0.2.30-canary.0 → 0.2.32-canary.0

package/dist/index.d.ts

@@ -698,19 +698,38 @@ declare function loadBundle(getEditor: () => PagedEditor, bundle: PagedBundle, o
  *  KEEP IN SYNC with plugin-cli's WASM_MAX_* and the schema's `maxBytes`
  *  maximum — the CLI hand-mirrors the contract. */
 declare const WASM_BUDGETS: {
-    /** Hard per-artifact byte ceiling for layout/codec/compute. A
-     *  release-optimised wasm layout engine (Blitz-class) lands in the
-     *  low-single-digit MiB; 8 MiB rejects an accidentally-bundled debug
-     *  build while leaving headroom for one real engine. A manifest
-     *  `maxBytes` may only TIGHTEN this. */
+    /**
+     * THE budget, as of 2026-08-19 (maintainer decision): **100 MB for the
+     * whole app including every plugin.**
+     *
+     * The per-thing ceilings below used to be the governance. They were
+     * the wrong shape: each capped one artifact or one bundle, so eight
+     * bundles could each pass their own gate while the app shipped a
+     * quarter of a gigabyte, and nothing in any repo measured the sum.
+     * What a user downloads is the sum, so the sum is what is governed.
+     *
+     * This constant is the CONTRACT; the enforcement lives where the app
+     * is assembled, in the editor's `scripts/wasm-budget.mjs` (run in its
+     * `checks` CI job), because only the app knows which bundles ship. It
+     * deduplicates by real path — pnpm links one store entry from many
+     * packages, and a naive walk over-counts nearly 6x. Measured 2026-08-19:
+     * 49.4 MB across 9 distinct artifacts, ~50 MB of headroom.
+     */
+    readonly maxAppTotalBytes: number;
+    /** Per-artifact ceiling for layout/codec/compute. Folded into the
+     *  app-wide envelope on 2026-08-19 (was 8 MiB, briefly 25): a single
+     *  artifact is no longer independently interesting, since the sum is
+     *  bounded. Kept — not deleted — so a manifest `maxBytes` still has
+     *  something to TIGHTEN and the loader keeps a hard upper stop. */
     readonly maxArtifactBytes: number;
-    /** D-07b — the governed HIGHER ceiling for `purpose: "engine"` (a
-     *  vendored DB/query engine like DuckDB-WASM ≈ 36 MiB). 64 MiB fits the
-     *  real artifacts with headroom; still a hard cap a manifest may only
-     *  tighten. Only the `engine` purpose earns it. */
+    /** D-07b — was the HIGHER ceiling for `purpose: "engine"` (a vendored
+     *  DB/query engine like DuckDB-WASM ≈ 36 MiB) back when ordinary
+     *  artifacts were capped far lower. Now equal to the ordinary cap; the
+     *  `purpose` distinction survives for governance/telemetry, not size. */
     readonly maxEngineArtifactBytes: number;
-    /** Total declared wasm across one bundle. Sized so one `engine`
-     *  artifact + a codec fit. */
+    /** Total declared wasm across ONE bundle. Also the app-wide number —
+     *  one bundle may in principle spend the entire envelope, and the
+     *  app-wide check is what stops the app as a whole. */
     readonly maxTotalBytes: number;
     /** Wall-clock budget for fetch + compile + instantiate. Protects the
      *  editor's main flow from a pathological module; advisory, the loader

package/dist/index.js

@@ -566,7 +566,12 @@ function createBundleHost(getEditor, manifest, options) {
         "contribute.panel",
         `contributes.panels[] must include "${c.id}"`
       );
-      return store.add(getEditor().registries.panels.register(c));
+      return store.add(
+        getEditor().registries.panels.register({
+          ...c,
+          source: manifest.name
+        })
+      );
     },
     schemaPanel(c) {
       assertNamespaced(c.id, "schemaPanel");
@@ -583,6 +588,8 @@ function createBundleHost(getEditor, manifest, options) {
         defaultGroup: c.defaultGroup,
         closable: c.closable,
         movable: c.movable,
+        // Host-stamped provenance, same as `panel()` above.
+        source: manifest.name,
         component: makeSchemaPanelComponent(
           c,
           bindings,
@@ -2618,20 +2625,39 @@ function loadBundle(getEditor, bundle, options) {
 
 // src/wasm-bundle-loader.ts
 var WASM_BUDGETS = {
-  /** Hard per-artifact byte ceiling for layout/codec/compute. A
-   *  release-optimised wasm layout engine (Blitz-class) lands in the
-   *  low-single-digit MiB; 8 MiB rejects an accidentally-bundled debug
-   *  build while leaving headroom for one real engine. A manifest
-   *  `maxBytes` may only TIGHTEN this. */
-  maxArtifactBytes: 8 * 1024 * 1024,
-  /** D-07b — the governed HIGHER ceiling for `purpose: "engine"` (a
-   *  vendored DB/query engine like DuckDB-WASM ≈ 36 MiB). 64 MiB fits the
-   *  real artifacts with headroom; still a hard cap a manifest may only
-   *  tighten. Only the `engine` purpose earns it. */
-  maxEngineArtifactBytes: 64 * 1024 * 1024,
-  /** Total declared wasm across one bundle. Sized so one `engine`
-   *  artifact + a codec fit. */
-  maxTotalBytes: 80 * 1024 * 1024,
+  /**
+   * THE budget, as of 2026-08-19 (maintainer decision): **100 MB for the
+   * whole app including every plugin.**
+   *
+   * The per-thing ceilings below used to be the governance. They were
+   * the wrong shape: each capped one artifact or one bundle, so eight
+   * bundles could each pass their own gate while the app shipped a
+   * quarter of a gigabyte, and nothing in any repo measured the sum.
+   * What a user downloads is the sum, so the sum is what is governed.
+   *
+   * This constant is the CONTRACT; the enforcement lives where the app
+   * is assembled, in the editor's `scripts/wasm-budget.mjs` (run in its
+   * `checks` CI job), because only the app knows which bundles ship. It
+   * deduplicates by real path — pnpm links one store entry from many
+   * packages, and a naive walk over-counts nearly 6x. Measured 2026-08-19:
+   * 49.4 MB across 9 distinct artifacts, ~50 MB of headroom.
+   */
+  maxAppTotalBytes: 100 * 1e3 * 1e3,
+  /** Per-artifact ceiling for layout/codec/compute. Folded into the
+   *  app-wide envelope on 2026-08-19 (was 8 MiB, briefly 25): a single
+   *  artifact is no longer independently interesting, since the sum is
+   *  bounded. Kept — not deleted — so a manifest `maxBytes` still has
+   *  something to TIGHTEN and the loader keeps a hard upper stop. */
+  maxArtifactBytes: 100 * 1e3 * 1e3,
+  /** D-07b — was the HIGHER ceiling for `purpose: "engine"` (a vendored
+   *  DB/query engine like DuckDB-WASM ≈ 36 MiB) back when ordinary
+   *  artifacts were capped far lower. Now equal to the ordinary cap; the
+   *  `purpose` distinction survives for governance/telemetry, not size. */
+  maxEngineArtifactBytes: 100 * 1e3 * 1e3,
+  /** Total declared wasm across ONE bundle. Also the app-wide number —
+   *  one bundle may in principle spend the entire envelope, and the
+   *  app-wide check is what stops the app as a whole. */
+  maxTotalBytes: 100 * 1e3 * 1e3,
   /** Wall-clock budget for fetch + compile + instantiate. Protects the
    *  editor's main flow from a pathological module; advisory, the loader
    *  aborts with a clear error when exceeded. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@paged-media/plugin-sdk",
-  "version": "0.2.30-canary.0",
+  "version": "0.2.32-canary.0",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -11,7 +11,7 @@
     }
   },
   "dependencies": {
-    "@paged-media/plugin-api": "0.2.30-canary.0"
+    "@paged-media/plugin-api": "0.2.32-canary.0"
   },
   "peerDependencies": {
     "react": "^18.3.0"
@@ -22,7 +22,7 @@
     }
   },
   "devDependencies": {
-    "@paged-media/canvas-wasm": "0.61.0",
+    "@paged-media/canvas-wasm": "0.62.0",
     "@types/node": "20.19.39",
     "@types/react": "^18.3.12",
     "react": "^18.3.0",