toilscript 0.1.46 → 0.1.48

package/dist/importmap.json

@@ -1,7 +1,7 @@
 {
   "imports": {
-    "toilscript": "https://cdn.jsdelivr.net/npm/toilscript@0.1.46/dist/toilscript.js",
-    "toilscript/cli": "https://cdn.jsdelivr.net/npm/toilscript@0.1.46/dist/cli.js",
+    "toilscript": "https://cdn.jsdelivr.net/npm/toilscript@0.1.48/dist/toilscript.js",
+    "toilscript/cli": "https://cdn.jsdelivr.net/npm/toilscript@0.1.48/dist/cli.js",
     "binaryen": "https://cdn.jsdelivr.net/npm/binaryen@130.0.0-nightly.20260609/index.js",
     "long": "https://cdn.jsdelivr.net/npm/long@5.3.2/index.js"
   }

package/dist/toilscript.generated.d.ts

@@ -3129,9 +3129,10 @@ declare module "types:toilscript/src/parser" {
         /**
          * Wire `@service` classes and free `@remote` functions onto the global `Rpc` registry. Runs ONCE
          * before element creation (via `weaveDataMigrations`). `@service` could be done at parse time, but
-         * folding both here gives a SINGLE place to honor the `@stream` gating: a project using `@stream`
-         * cannot declare `@service`/`@remote` (the 9003 diagnostic fires at element creation), so we must not
-         * half-inject first or the build crashes instead of reporting it.
+         * folding both here gives a SINGLE place to honor the same-source `@stream` rule: ONE source cannot
+         * declare both `@stream` and `@service`/`@remote`, so we SKIP the RPC weave for any source that also has
+         * a `@stream` - weaving it would half-inject an unresolvable import and crash instead of letting
+         * enforceStreamServiceExclusion report it. (`@stream` + `@service`/`@remote` DO coexist across tiers.)
          */
         private weaveRpc;
         /** Reject duplicate client-facing `Server` keys (two @services lowercasing to the same key, a free
@@ -3139,8 +3140,8 @@ declare module "types:toilscript/src/parser" {
          *  surface is emitted - else the generated `Server` object/type silently overwrites a key, or a collided
          *  id routes to the wrong method at dispatch. */
         private checkRpcSurfaceCollisions;
-        /** True if the program declares any `@stream` class (gates the RPC weave; see diagnostic 9003). */
-        private projectHasStream;
+        /** True if `source` declares any `@stream` class (the RPC weave skips such a source; diagnostic 9003). */
+        private sourceHasStream;
         /** Inject the RPC dispatch fn + its registration for one free `@remote` function (id = FNV of the
          *  bare function name, matching the generated client). */
         private injectRemote;
@@ -3677,12 +3678,11 @@ declare module "types:toilscript/src/program" {
         /** Initializes the program and its elements prior to compilation. */
         initialize(): void;
         /**
-         * Enforces the project-wide rule that a compilation unit using `@stream` cannot also
-         * declare `@service` or `@remote` anywhere (spec 03 section 4.4). The host loads one
-         * `hot.wasm` whose surface is either a stream node or an RPC service node, never both,
-         * so mixing them is a deploy-time ambiguity caught fail-closed at compile time. Reported
-         * at the offending `@service`/`@remote` site. Skipped in cold mode (neither flag is
-         * admitted there anyway).
+         * Enforces that a SINGLE source (one emitted surface) cannot declare BOTH `@stream` AND
+         * `@service`/`@remote`: the host loads one artifact whose surface is either a stream node or an RPC
+         * service node, never both. `@stream` and `@service`/`@remote` DO coexist across separate tier files
+         * (main.ts vs main.stream.ts); only the same-source clash is the deploy-time ambiguity caught here.
+         * Reported at the offending `@service`/`@remote` site. Skipped in cold mode.
          */
         private enforceStreamServiceExclusion;
         /** Processes overridden members by this class in a base class. */