@quillmark/quiver 0.5.1 → 0.6.0

package/LICENSE

@@ -1,201 +1,21 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+MIT License
+
+Copyright (c) 2026 Nibs
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/PROGRAM.md

@@ -37,24 +37,26 @@ Loaders are paired 1:1 with what they load:
 
 - `Quiver.fromPackage(specifier)` and `Quiver.fromDir(path)` load the
   **source** layout (Node only).
-- `Quiver.fromBuilt(url)` loads the **build output** over HTTP/HTTPS
+- `Quiver.fromBuiltUrl(url)` loads the **build output** over HTTP/HTTPS
   (browser-safe; works in Node too).
+- `Quiver.fromBuiltDir(path)` loads the **build output** from a local
+  directory (Node only).
 
 There is no auto-detection: each loader's name commits to what it expects.
 
 **Naming decisions:**
-- The verb is `build()`. Pairs with `fromBuilt()` (past participle = "the
-  built one"). Avoids collision with `npm pack`, JS bundler vocabulary,
-  and the internal "bundle zips" term.
+- The verb is `build()`. Pairs with the `fromBuilt*` family (past participle
+  = "the built one"). Avoids collision with `npm pack`, JS bundler
+  vocabulary, and the internal "bundle zips" term.
 - Loaders for source layouts are named by **where the source lives**
-  (`Package` / `Dir`). The loader for build output is named by **what it
-  loads** (`Built`), not by transport — `fromUrl` was rejected because it
-  hides the artifact type.
-- Build output is HTTP-served only. Loading a built artifact from local
-  disk is intentionally unsupported in V1; consumers either spin up a
-  local HTTP server or use `fromPackage`/`fromDir` against the source.
-  Adding `Quiver.fromBuiltDir(path)` later is purely additive if a real
-  use case appears.
+  (`Package` / `Dir`). Loaders for build output are named by **what** they
+  load (`Built`) plus **where** they load it from (`Url` / `Dir`). The
+  artifact type stays in the name; the transport disambiguates.
+- Server-side runtime (Node) reads packed artifacts from disk via
+  `fromBuiltDir`. This is the recommended shape when the runtime artifact
+  ships in the deployment image: source quivers stay as devDependencies,
+  there is no self-fetch over a load balancer / CDN, and serverless bundle
+  sizes are minimised.
 
 ### 2) `Quiver.yaml` Is Required in Source Quivers
 
@@ -72,16 +74,19 @@ Unknown fields in `Quiver.yaml` are a **validation error** (`quiver_invalid`). S
 ### 3) `QuillSource` Becomes Quiver-Centric
 
 - Re-express `QuillSource` concepts around Quivers
-- Three loaders, each with one input shape and one shape-of-thing-loaded:
+- Four loaders, each with one input shape and one shape-of-thing-loaded:
   - `Quiver.fromPackage(specifier)` — Node-only; resolves an npm specifier
     against `node_modules` and loads the source layout at the package root
   - `Quiver.fromDir(path)` — Node-only; loads source layout from a local
     directory. Also accepts `import.meta.url`-style `file://` URLs as a
     convenience for tests (the URL's parent directory is used)
-  - `Quiver.fromBuilt(url)` — browser-safe; loads build output from an
+  - `Quiver.fromBuiltUrl(url)` — browser-safe; loads build output from an
     `http(s)://` or origin-relative URL
+  - `Quiver.fromBuiltDir(path)` — Node-only; loads build output from a
+    local directory (the output of `Quiver.build`)
 - "Transport" is not a first-class concept; HTTP fetching is an internal
-  detail of `fromBuilt`
+  detail of `fromBuiltUrl`, filesystem access is an internal detail of
+  `fromBuiltDir`
 
 ### 4) Single-Quiver Scope (V1)
 
@@ -191,8 +196,17 @@ choose how to consume it:
   // build step (Node)
   await Quiver.build("./node_modules/@org/my-quiver", "./public/quivers/my-quiver");
   // browser runtime
-  const quiver = await Quiver.fromBuilt("/quivers/my-quiver/");
+  const quiver = await Quiver.fromBuiltUrl("/quivers/my-quiver/");
   ```
+- **Node server-side runtime consumers** also run the build step, ship the
+  packed artifact in their deployment image, and load it from disk:
+  ```ts
+  await Quiver.build("./node_modules/@org/my-quiver", "./static/quills/my-quiver");
+  // server runtime
+  const quiver = await Quiver.fromBuiltDir("./static/quills/my-quiver");
+  ```
+  This keeps source quivers as devDependencies and avoids self-fetching
+  through the deployment's load balancer / CDN.
 
 Rationale:
 
@@ -206,7 +220,7 @@ Rationale:
 the default.** Authors who need to ship runtime-ready output directly
 (e.g. their consumers cannot run a Node build step) may publish
 `Quiver.build(...)` output to a CDN and instruct consumers to use
-`Quiver.fromBuilt(<cdn-url>)`. Treated as the exception.
+`Quiver.fromBuiltUrl(<cdn-url>)`. Treated as the exception.
 
 Validation responsibility shifts left: authors should run
 `Quiver.fromDir` and `Quiver.build` in CI so `quiver_invalid` errors
@@ -222,17 +236,19 @@ V1 intentionally retains:
 1. Font dehydration as a build-output property
 2. Consumer validation tooling for source layouts (+ optional build-parity checks)
 3. Manifest pointer resolution for build output
-4. HTTP/HTTPS loading via `Quiver.fromBuilt`
-5. Source layout loading as first-class dev loop (`fromPackage` / `fromDir`)
-6. Typed errors (`QuiverError`) with quiver/source context
-7. Concurrency coalescing for in-flight loads
-8. Preload/fail-fast helpers where they still add value
+4. HTTP/HTTPS loading via `Quiver.fromBuiltUrl`
+5. Filesystem loading of build output via `Quiver.fromBuiltDir` for Node
+   server-side runtimes
+6. Source layout loading as first-class dev loop (`fromPackage` / `fromDir`)
+7. Typed errors (`QuiverError`) with quiver/source context
+8. Concurrency coalescing for in-flight loads
+9. Preload/fail-fast helpers where they still add value
 
 Removed from carryover assumptions:
 
 - Any engine-registration cache fast path (`register`/`has`) because upstream removed the capability
-- "Transport" as a user-facing concept (folded into `fromBuilt` internals)
-- Loading build output from local disk (no `fromBuiltDir` in V1; YAGNI)
+- "Transport" as a user-facing concept (folded into `fromBuiltUrl` /
+  `fromBuiltDir` internals)
 
 ---
 
@@ -277,8 +293,10 @@ V1 runtime loading paths:
 1. `Quiver.fromPackage(specifier)` — npm package resolution; loads source
    (authoring/dev/Node runtime)
 2. `Quiver.fromDir(path)` — local directory; loads source (Node)
-3. `Quiver.fromBuilt(url)` — HTTP(S); loads build output (browser; also
+3. `Quiver.fromBuiltUrl(url)` — HTTP(S); loads build output (browser; also
    works in Node)
+4. `Quiver.fromBuiltDir(path)` — local directory; loads build output
+   (Node server-side runtime)
 
 V1 build behavior:
 
@@ -361,7 +379,7 @@ Rehydration on load: the loader fetches the pointer → hashed manifest → requ
 
 ## API Surface (V1)
 
-Single class, three loaders + one builder. Each loader has one input
+Single class, four loaders + one builder. Each loader has one input
 shape and one shape-of-thing-loaded; no auto-detection.
 
 ```ts
@@ -380,7 +398,13 @@ class Quiver {
   // Browser-safe loader: load build output from an http(s):// or
   // origin-relative URL. Throws `transport_error` on file:// inputs.
   // (From `@quillmark/quiver` main.)
-  static fromBuilt(url: string): Promise<Quiver>;
+  static fromBuiltUrl(url: string): Promise<Quiver>;
+
+  // Node-only loader: load build output from a local directory (the
+  // output of Quiver.build). No network. Use for server-side runtime
+  // when the packed artifact ships in the deployment image.
+  // (From `@quillmark/quiver/node`.)
+  static fromBuiltDir(dirPath: string): Promise<Quiver>;
 
   // Node-only tooling: produce the runtime artifact from a source layout.
   // (From `@quillmark/quiver/node`.)
@@ -429,12 +453,12 @@ const result = quill.render(doc, { format: "pdf" });
 
 **Entrypoints:**
 - `@quillmark/quiver` (main, browser-safe): `Quiver` class with only
-  `fromBuilt` functional (Node-only loaders/builder throw
+  `fromBuiltUrl` functional (Node-only loaders/builder throw
   `transport_error` if reached in browser), `QuiverError`,
   `QuillmarkLike`, `QuillLike`, shared types.
 - `@quillmark/quiver/node`: adds `Quiver.fromPackage`, `Quiver.fromDir`,
-  `Quiver.build` behaviors. Single `Quiver` class — Node-only factories
-  fail fast outside Node.
+  `Quiver.fromBuiltDir`, `Quiver.build` behaviors. Single `Quiver` class —
+  Node-only factories fail fast outside Node.
 - `@quillmark/quiver/testing` (Node-only): single export
   `runQuiverTests(metaUrlOrDir, engine)` built on `node:test` (zero
   external test-runner dependency). Optional convenience; users on other
@@ -466,7 +490,7 @@ const result = quill.render(doc, { format: "pdf" });
 
 All V1 planner questions resolved; implementation plan can proceed against the spec above.
 
-1. ~~Final `Quiver` interface shape and transport factoring style~~ → Single `Quiver` class, three loaders (`fromPackage`, `fromDir`, `fromBuilt`) + one builder (`build`). Each loader names what it loads; no auto-detection.
+1. ~~Final `Quiver` interface shape and transport factoring style~~ → Single `Quiver` class, four loaders (`fromPackage`, `fromDir`, `fromBuiltUrl`, `fromBuiltDir`) + one builder (`build`). Each loader names what it loads (source/built) and where it loads from (package/dir/url); no auto-detection.
 2. ~~Final `Quiver.yaml` schema and unknown-field policy~~ → See §2: alphanumeric `name` and optional tooling-only `description`. Unknown fields are `quiver_invalid`.
 3. ~~Canonical ref grammar and parser API contract~~ → Internal `parseQuillRef`, not exported. Selector syntax per §5. Throws `invalid_ref`.
 4. ~~Exact warning policy for shadowed refs across quivers~~ → N/A in V1: no multi-quiver composition layer; each `Quiver` instance is independent (§4).

package/README.md

@@ -14,13 +14,16 @@ A Quiver has one authored shape: the **source layout** (`Quiver.yaml` at the
 package root, quills under `quills/<name>/<x.y.z>/`). Authors publish it as
 an npm package. Consumers decide how to consume it:
 
-- **Node consumers** load the source layout directly with `Quiver.fromPackage`.
+- **Node consumers** load the source layout directly with `Quiver.fromPackage`,
+  or load a packed (build-output) artifact from disk with
+  `Quiver.fromBuiltDir`.
 - **Browser consumers** run `Quiver.build(...)` as a build step and serve the
-  output as static assets, loading it with `Quiver.fromBuilt`.
+  output as static assets, loading it with `Quiver.fromBuiltUrl`.
 
-Each loader names exactly what it loads: `fromPackage` and `fromDir` always
-read source layouts; `fromBuilt` always reads build output over an HTTP(S)
-or origin-relative URL. No auto-detection, no branching on artifact shape.
+Each loader names exactly what it loads. Source: `fromPackage(specifier)`,
+`fromDir(path)`. Build output: `fromBuiltUrl(url)` (HTTP/HTTPS, browser-safe),
+`fromBuiltDir(path)` (filesystem, Node-only). No auto-detection, no branching
+on artifact shape.
 
 This keeps the author flow to a single command (`npm publish` or `git tag`)
 and puts the deployment-topology decision where it belongs: with the
@@ -91,22 +94,37 @@ await Quiver.build(
 // browser runtime
 import { Quiver } from "@quillmark/quiver";
 
-const quiver = await Quiver.fromBuilt("/quivers/my-quiver/");
+const quiver = await Quiver.fromBuiltUrl("/quivers/my-quiver/");
 const quill = await quiver.getQuill(doc.quillRef, { engine });
 ```
 
+## Server-side runtime (Node, packed artifact on disk)
+
+For server-side rendering where the packed artifact ships in the deployment
+image, use `Quiver.fromBuiltDir` to read it from disk. This avoids the
+self-fetch / load-balancer round-trip that `fromBuiltUrl` would force on a
+self-hosted deployment, and lets the source quiver stay in
+`devDependencies`:
+
+```ts
+import { Quiver } from "@quillmark/quiver/node";
+
+// Packed at build time, e.g. into ./static/quills/my-quiver
+const quiver = await Quiver.fromBuiltDir("./static/quills/my-quiver");
+```
+
 ## Advanced: pre-built distribution to a CDN
 
 If you need to ship the runtime artifact directly (e.g. consumers cannot run
 a Node build step), publish `Quiver.build` output to a CDN and have
-consumers point `fromBuilt` at the CDN URL:
+consumers point `fromBuiltUrl` at the CDN URL:
 
 ```ts
 import { Quiver } from "@quillmark/quiver/node";
 
 await Quiver.build("./my-quiver", "./dist/my-quiver");
 // upload ./dist/my-quiver to https://cdn.example.com/quivers/my-quiver/
-const quiver = await Quiver.fromBuilt("https://cdn.example.com/quivers/my-quiver/");
+const quiver = await Quiver.fromBuiltUrl("https://cdn.example.com/quivers/my-quiver/");
 ```
 
 ## Warm (prefetch all quill trees)
@@ -116,7 +134,8 @@ await quiver.warm();
 ```
 
 `warm()` is I/O-only: it loads every quill's tree (over the network for
-`fromBuilt`, off the filesystem for `fromPackage`/`fromDir`) and caches
+`fromBuiltUrl`, off the filesystem for `fromPackage` / `fromDir` /
+`fromBuiltDir`) and caches
 them. It does not require an engine and does not materialize Quill
 instances — that happens lazily on the first `getQuill` call, which is
 microseconds. A subsequent `getQuill` reuses the cached tree, skipping

package/dist/node.d.ts

@@ -4,7 +4,7 @@
  * Importing this module is the consumer's explicit declaration of intent:
  * "I am running in Node and want the Node-only Quiver factories." It exposes
  * the same `Quiver` class as the main entry, augmented with `fromDir`,
- * `fromPackage`, and `build` static methods.
+ * `fromPackage`, `fromBuiltDir`, and `build` static methods.
  *
  * Side effect: at module evaluation time, the Node-only static methods are
  * installed on the shared `Quiver` constructor. Any other module that already
@@ -12,10 +12,11 @@
  * runtime — but TypeScript will only expose them on the binding imported from
  * here, so the import path remains the contract.
  *
- * Bundler note: importing this entry pulls in `./source-loader.js` and
- * `./build.js`, both of which statically import `node:*` builtins. Browser
- * bundles must never reach this module. The main entry (`./index.js`) makes
- * no static or dynamic reference to it.
+ * Bundler note: importing this entry pulls in `./source-loader.js`,
+ * `./build.js`, and `./transports/fs-built-transport.js`, all of which
+ * statically import `node:*` builtins. Browser bundles must never reach this
+ * module. The main entry (`./index.js`) makes no static or dynamic reference
+ * to it.
  */
 import { Quiver as Base } from "./quiver.js";
 import { type BuildOptions } from "./build.js";
@@ -40,6 +41,20 @@ type NodeQuiverStatics = {
      * failure.
      */
     fromDir(pathOrFileUrl: string): Promise<Base>;
+    /**
+     * Loads a packed (build-output) quiver from a local directory containing
+     * `Quiver.json` and the manifest/bundle/store files written by
+     * `Quiver.build`. Symmetric to `fromBuiltUrl(url)` but reads from disk
+     * instead of HTTP — no network required.
+     *
+     * Use this for server-side runtime when a packed artifact ships in the
+     * deployment image; consumers can keep source quivers as devDependencies
+     * and avoid self-fetching over their own load balancer.
+     *
+     * Throws `quiver_invalid` on format errors, `transport_error` on I/O
+     * failure.
+     */
+    fromBuiltDir(dirPath: string): Promise<Base>;
     /**
      * Reads the Source Quiver at sourceDir, validates it, and writes the
      * runtime build artifact to outDir.

package/dist/node.js

@@ -4,7 +4,7 @@
  * Importing this module is the consumer's explicit declaration of intent:
  * "I am running in Node and want the Node-only Quiver factories." It exposes
  * the same `Quiver` class as the main entry, augmented with `fromDir`,
- * `fromPackage`, and `build` static methods.
+ * `fromPackage`, `fromBuiltDir`, and `build` static methods.
  *
  * Side effect: at module evaluation time, the Node-only static methods are
  * installed on the shared `Quiver` constructor. Any other module that already
@@ -12,15 +12,18 @@
  * runtime — but TypeScript will only expose them on the binding imported from
  * here, so the import path remains the contract.
  *
- * Bundler note: importing this entry pulls in `./source-loader.js` and
- * `./build.js`, both of which statically import `node:*` builtins. Browser
- * bundles must never reach this module. The main entry (`./index.js`) makes
- * no static or dynamic reference to it.
+ * Bundler note: importing this entry pulls in `./source-loader.js`,
+ * `./build.js`, and `./transports/fs-built-transport.js`, all of which
+ * statically import `node:*` builtins. Browser bundles must never reach this
+ * module. The main entry (`./index.js`) makes no static or dynamic reference
+ * to it.
  */
 import { Quiver as Base } from "./quiver.js";
 import { QuiverError } from "./errors.js";
 import { scanSourceQuiver, SourceLoader } from "./source-loader.js";
 import { buildQuiver } from "./build.js";
+import { loadBuiltQuiver } from "./built-loader.js";
+import { FsBuiltTransport } from "./transports/fs-built-transport.js";
 import { createRequire } from "node:module";
 import { dirname } from "node:path";
 import { fileURLToPath } from "node:url";
@@ -35,6 +38,9 @@ Quiver.fromDir = async function fromDir(pathOrFileUrl) {
     const { meta, catalog } = await scanSourceQuiver(dir);
     return Base._fromLoader(meta.name, catalog, new SourceLoader(dir));
 };
+Quiver.fromBuiltDir = async function fromBuiltDir(dirPath) {
+    return loadBuiltQuiver(new FsBuiltTransport(dirPath));
+};
 Quiver.fromPackage = async function fromPackage(specifier) {
     const req = createRequire(import.meta.url);
     let yamlPath;

package/dist/quiver.d.ts

@@ -4,10 +4,10 @@
  * Polymorphism via composition: internally stores a pluggable loader
  * (either source-backed or build-output-backed).
  *
- * This module is browser-safe: only `fromBuilt` and the instance API live
- * here. Node-only factories (`fromDir`, `fromPackage`, `build`) are installed
- * on this class by `./node.js`, which is the consumer's explicit opt-in to
- * the Node API surface.
+ * This module is browser-safe: only `fromBuiltUrl` and the instance API live
+ * here. Node-only factories (`fromDir`, `fromPackage`, `fromBuiltDir`,
+ * `build`) are installed on this class by `./node.js`, which is the
+ * consumer's explicit opt-in to the Node API surface.
  */
 import type { QuillmarkLike, QuillLike } from "./engine-types.js";
 /** @internal Internal loader strategy: source or build output. */
@@ -18,10 +18,10 @@ export declare class Quiver {
     #private;
     readonly name: string;
     /**
-     * Private constructor — use static factory methods (`Quiver.fromBuilt`, or
-     * the Node-only `Quiver.fromDir` / `Quiver.fromPackage` installed by
-     * `@quillmark/quiver/node`). TS prevents external `new Quiver(...)` at
-     * compile time.
+     * Private constructor — use static factory methods (`Quiver.fromBuiltUrl`,
+     * or the Node-only `Quiver.fromDir` / `Quiver.fromPackage` /
+     * `Quiver.fromBuiltDir` installed by `@quillmark/quiver/node`). TS prevents
+     * external `new Quiver(...)` at compile time.
      */
     private constructor();
     /**
@@ -34,14 +34,14 @@ export declare class Quiver {
      * Browser-safe factory. Loads build output from an HTTP/HTTPS URL.
      *
      * Origin-relative URLs (e.g. `/quivers/foo/`) are accepted in browser
-     * environments. `file://` URLs are rejected — local build output is
-     * not loadable in V1; serve over HTTP or use `fromPackage`/`fromDir`
-     * against the source.
+     * environments. `file://` URLs are rejected — to load build output from
+     * disk in Node, use `Quiver.fromBuiltDir(path)` from
+     * `@quillmark/quiver/node`.
      *
      * Throws `transport_error` on network/HTTP failure, `quiver_invalid`
      * on format errors.
      */
-    static fromBuilt(url: string): Promise<Quiver>;
+    static fromBuiltUrl(url: string): Promise<Quiver>;
     /** Returns all known quill names, sorted lexicographically. */
     quillNames(): string[];
     /**

package/dist/quiver.js

@@ -4,10 +4,10 @@
  * Polymorphism via composition: internally stores a pluggable loader
  * (either source-backed or build-output-backed).
  *
- * This module is browser-safe: only `fromBuilt` and the instance API live
- * here. Node-only factories (`fromDir`, `fromPackage`, `build`) are installed
- * on this class by `./node.js`, which is the consumer's explicit opt-in to
- * the Node API surface.
+ * This module is browser-safe: only `fromBuiltUrl` and the instance API live
+ * here. Node-only factories (`fromDir`, `fromPackage`, `fromBuiltDir`,
+ * `build`) are installed on this class by `./node.js`, which is the
+ * consumer's explicit opt-in to the Node API surface.
  */
 import { QuiverError } from "./errors.js";
 import { parseQuillRef } from "./ref.js";
@@ -29,10 +29,10 @@ export class Quiver {
      */
     #treeCache = new Map();
     /**
-     * Private constructor — use static factory methods (`Quiver.fromBuilt`, or
-     * the Node-only `Quiver.fromDir` / `Quiver.fromPackage` installed by
-     * `@quillmark/quiver/node`). TS prevents external `new Quiver(...)` at
-     * compile time.
+     * Private constructor — use static factory methods (`Quiver.fromBuiltUrl`,
+     * or the Node-only `Quiver.fromDir` / `Quiver.fromPackage` /
+     * `Quiver.fromBuiltDir` installed by `@quillmark/quiver/node`). TS prevents
+     * external `new Quiver(...)` at compile time.
      */
     constructor(name, catalog, loader) {
         this.name = name;
@@ -51,16 +51,16 @@ export class Quiver {
      * Browser-safe factory. Loads build output from an HTTP/HTTPS URL.
      *
      * Origin-relative URLs (e.g. `/quivers/foo/`) are accepted in browser
-     * environments. `file://` URLs are rejected — local build output is
-     * not loadable in V1; serve over HTTP or use `fromPackage`/`fromDir`
-     * against the source.
+     * environments. `file://` URLs are rejected — to load build output from
+     * disk in Node, use `Quiver.fromBuiltDir(path)` from
+     * `@quillmark/quiver/node`.
      *
      * Throws `transport_error` on network/HTTP failure, `quiver_invalid`
      * on format errors.
      */
-    static async fromBuilt(url) {
+    static async fromBuiltUrl(url) {
         if (url.startsWith("file://")) {
-            throw new QuiverError("transport_error", `Quiver.fromBuilt requires an http(s):// or origin-relative URL; got "${url}". Local build output is not loadable in V1 — serve it over HTTP or load source via fromPackage/fromDir.`);
+            throw new QuiverError("transport_error", `Quiver.fromBuiltUrl requires an http(s):// or origin-relative URL; got "${url}". For local build output, use Quiver.fromBuiltDir from @quillmark/quiver/node.`);
         }
         const { HttpTransport } = await import("./transports/http-transport.js");
         const { loadBuiltQuiver } = await import("./built-loader.js");

package/dist/transports/fs-built-transport.d.ts

@@ -0,0 +1,14 @@
+/**
+ * FsBuiltTransport — Node-only built-quiver transport that reads packed
+ * artifacts from the local filesystem.
+ * Internal; not exported from index.ts.
+ *
+ * Static `node:*` imports — this module must never be reached from browser
+ * bundles. It is loaded lazily by `Quiver.fromBuiltDir` in `./node.js`.
+ */
+import type { BuiltTransport } from "../built-loader.js";
+export declare class FsBuiltTransport implements BuiltTransport {
+    private readonly rootDir;
+    constructor(rootDir: string);
+    fetchBytes(relativePath: string): Promise<Uint8Array>;
+}

package/dist/transports/fs-built-transport.js

@@ -0,0 +1,34 @@
+/**
+ * FsBuiltTransport — Node-only built-quiver transport that reads packed
+ * artifacts from the local filesystem.
+ * Internal; not exported from index.ts.
+ *
+ * Static `node:*` imports — this module must never be reached from browser
+ * bundles. It is loaded lazily by `Quiver.fromBuiltDir` in `./node.js`.
+ */
+import { readFile } from "node:fs/promises";
+import { join, isAbsolute, normalize, sep } from "node:path";
+import { QuiverError } from "../errors.js";
+export class FsBuiltTransport {
+    rootDir;
+    constructor(rootDir) {
+        this.rootDir = rootDir;
+    }
+    async fetchBytes(relativePath) {
+        if (isAbsolute(relativePath)) {
+            throw new QuiverError("transport_error", `FsBuiltTransport: absolute paths are not allowed: "${relativePath}"`);
+        }
+        const normalized = normalize(relativePath);
+        if (normalized.startsWith("..") || normalized.split(sep).includes("..")) {
+            throw new QuiverError("transport_error", `FsBuiltTransport: path escapes root: "${relativePath}"`);
+        }
+        const filePath = join(this.rootDir, normalized);
+        try {
+            const buf = await readFile(filePath);
+            return new Uint8Array(buf.buffer, buf.byteOffset, buf.byteLength);
+        }
+        catch (err) {
+            throw new QuiverError("transport_error", `Failed to read "${filePath}": ${err.message}`, { cause: err });
+        }
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quillmark/quiver",
-  "version": "0.5.1",
+  "version": "0.6.0",
   "description": "Quiver registry and build tooling for Quillmark",
   "type": "module",
   "license": "MIT",