@@ -0,0 +1,12 @@
+---
+'@objectstack/spec': patch
+---
+
+docs(spec): three comments describe the shared-chunk bundle layout, not the per-entry one
+
+Clause-②: no
+Metadata-protocol: none
+
+The module doc block in `@objectstack/spec`'s root entry, the `@__PURE__` note on the conversions table, and the Package API assembled-entry doc block (the generated reference page of the same name) still said each entry is a self-contained, single-file bundle. The build is one module graph: a module two entries reach ships once, in a shared chunk, and an entry links every chunk its graph touches. The sentences now say that. The doc text rides in the shipped declaration files, which is why this is a patch entry; no export, key, value or behaviour changes.
+
+What to do: nothing.
@@ -28,8 +28,8 @@ driver-config validators and the server-only pg URL grammar. Declared inside
 `@objectstack/spec/api` (#17517), that tree became part of every bundle of the
 entry — and a browser module that imported two string constants from
 `./sortability.zod` paid for all of it, roughly doubling its gzipped bundle,
-because the entry ships as one self-contained bundle and little of that tree
-can be dropped by a consumer's tree-shaking. The maintainer ruling on #18576
+because the entry links every chunk its module graph touches and little of
+that tree can be dropped by a consumer's tree-shaking. The maintainer ruling on #18576
 (letter B) removed the cost rather than watching it: the browser-facing
 `./api` no longer carries these declarations, and this entry does.
 
 
@@ -37,8 +37,8 @@ import {
  * `@objectstack/spec/api` (#17517), that tree became part of every bundle of the
  * entry — and a browser module that imported two string constants from
  * `./sortability.zod` paid for all of it, roughly doubling its gzipped bundle,
- * because the entry ships as one self-contained bundle and little of that tree
- * can be dropped by a consumer's tree-shaking. The maintainer ruling on #18576
+ * because the entry links every chunk its module graph touches and little of
+ * that tree can be dropped by a consumer's tree-shaking. The maintainer ruling on #18576
  * (letter B) removed the cost rather than watching it: the browser-facing
  * `./api` no longer carries these declarations, and this entry does.
  *
 
@@ -18238,10 +18238,11 @@ const MAJOR_18_CONVERSIONS: readonly OrderedConversion[] = [
  *
  * ⚠️ EVERY CALL THIS TABLE AND {@link ALL_CONVERSIONS} MAKE AT MODULE LOAD
  * CARRIES AN `@__PURE__` ANNOTATION — a major's `inApplicationOrder(…)` and
- * the flattening below, and the next major's when it opens. Each published
- * entry is one flat file (`tsup.config.ts`, `splitting: false`), so a
- * consumer's bundler keeps every top-level call it cannot prove pure, together
- * with everything that call references. Unmarked, these two initializers kept
+ * the flattening below, and the next major's when it opens. The entries share
+ * one module graph (`tsup.config.ts`, `oneModuleGraph`), and every entry whose
+ * graph reaches this module links the chunk it ships in, so a consumer's
+ * bundler keeps every top-level call it cannot prove pure, together with
+ * everything that call references. Unmarked, these two initializers kept
  * the whole table in every bundle of every entry whose graph reaches this
  * module — every conversion, and the view, field, page-component, dashboard,
  * chart and report schemas the conversions read. `./shared` is one of those
 
@@ -70,9 +70,11 @@
  * > machinery. The schema graph is the server/publish side's dependency, never
  * > the price of spelling a URL segment or reading a posture predicate.
  *
- * Every subpath entry is a self-contained bundle, so a vocabulary symbol that
- * shares an entry with schema modules costs its consumers the whole schema
- * closure (measured on #10096: one string fold through `/shared` cost
+ * The entries share one module graph (a module two entries reach ships once,
+ * in a shared chunk), but an entry links every chunk its own module graph
+ * touches, so a vocabulary symbol that shares an entry with schema modules
+ * still costs its consumers the whole schema closure (measured on #10096,
+ * under the former per-entry bundles: one string fold through `/shared` cost
  * +60.1 KB gzipped). When adding an export a browser consumer will reach,
  * either put it on a schema-free entry (`/meta-spelling` is the reference:
  * heavy derivation happens at BUILD time via a generator + check gate, the