@telorun/runner-core 0.13.0 → 0.14.0

package/dist/session/workspace-marker.d.ts

@@ -10,16 +10,18 @@ export declare const WORKSPACE_MARKER_FILENAME = "telo-workspace.yaml";
  * apps in one workspace resolve the same module twice into two caches — and an
  * app in a subdirectory gets a third.
  *
- * `modules:` is release scope and is read by `telo release` alone, which never
- * runs in a session. It is written anyway because an empty list is a hard error
- * in the parser, and a file this repo's own tooling would reject is not one to
- * seed into a user's workspace.
+ * **It declares no blocks.** Every field of the marker sits in a block scoped to
+ * the command that reads it, and a session runs none of them: `release:` is
+ * versioning and publishing, which never happens here. This used to write
+ * `modules: ["*"]` — release scope a session has no use for — purely because an
+ * empty list was a parse error, so the runner shipped a fabricated claim into
+ * every user's workspace to satisfy a reader that was never going to run.
  */
-export declare const WORKSPACE_MARKER_CONTENTS = "# Marks the root of this session's workspace.\n#\n# The Telo kernel anchors its module cache (.telo) at the directory holding this\n# file, so every application in this workspace resolves its imports once into one\n# cache instead of once per app.\nmodules: [\"*\"]\n";
+export declare const WORKSPACE_MARKER_CONTENTS = "# Marks the root of this session's workspace.\n#\n# The Telo kernel anchors its module cache (.telo) at the directory holding this\n# file, so every application in this workspace resolves its imports once into one\n# cache instead of once per app. It also bounds the walk that collects .env and\n# .env.local for a run.\n#\n# Nothing else is declared: 'release:' (where modules live, and where they\n# publish) is read by `telo release`, which does not run in a session.\n";
 /**
  * The marker, unless the workspace already brings its own. A user whose project
- * really is a Telo workspace has a marker with a real \`modules:\` list, and
- * overwriting it would silently change what \`telo release\` discovers.
+ * really is a Telo workspace has a marker with a real \`release.modules\` list,
+ * and overwriting it would silently change what \`telo release\` discovers.
  */
 export declare function workspaceMarkerWrite(bundle: RunBundle): NonNullable<WorkspaceChangeSet["write"]>;
 //# sourceMappingURL=workspace-marker.d.ts.map

package/dist/session/workspace-marker.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"workspace-marker.d.ts","sourceRoot":"","sources":["../../src/session/workspace-marker.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,SAAS,EAAE,kBAAkB,EAAE,MAAM,gBAAgB,CAAC;AAEpE,+EAA+E;AAC/E,eAAO,MAAM,yBAAyB,wBAAwB,CAAC;AAE/D;;;;;;;;;;;;;GAaG;AACH,eAAO,MAAM,yBAAyB,gRAMrC,CAAC;AAEF;;;;GAIG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,SAAS,GAChB,WAAW,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC,CAI1C"}
+{"version":3,"file":"workspace-marker.d.ts","sourceRoot":"","sources":["../../src/session/workspace-marker.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,SAAS,EAAE,kBAAkB,EAAE,MAAM,gBAAgB,CAAC;AAEpE,+EAA+E;AAC/E,eAAO,MAAM,yBAAyB,wBAAwB,CAAC;AAE/D;;;;;;;;;;;;;;;GAeG;AACH,eAAO,MAAM,yBAAyB,6dASrC,CAAC;AAEF;;;;GAIG;AACH,wBAAgB,oBAAoB,CAClC,MAAM,EAAE,SAAS,GAChB,WAAW,CAAC,kBAAkB,CAAC,OAAO,CAAC,CAAC,CAI1C"}

package/dist/session/workspace-marker.js

@@ -9,22 +9,27 @@ export const WORKSPACE_MARKER_FILENAME = "telo-workspace.yaml";
  * apps in one workspace resolve the same module twice into two caches — and an
  * app in a subdirectory gets a third.
  *
- * `modules:` is release scope and is read by `telo release` alone, which never
- * runs in a session. It is written anyway because an empty list is a hard error
- * in the parser, and a file this repo's own tooling would reject is not one to
- * seed into a user's workspace.
+ * **It declares no blocks.** Every field of the marker sits in a block scoped to
+ * the command that reads it, and a session runs none of them: `release:` is
+ * versioning and publishing, which never happens here. This used to write
+ * `modules: ["*"]` — release scope a session has no use for — purely because an
+ * empty list was a parse error, so the runner shipped a fabricated claim into
+ * every user's workspace to satisfy a reader that was never going to run.
  */
 export const WORKSPACE_MARKER_CONTENTS = `# Marks the root of this session's workspace.
 #
 # The Telo kernel anchors its module cache (.telo) at the directory holding this
 # file, so every application in this workspace resolves its imports once into one
-# cache instead of once per app.
-modules: ["*"]
+# cache instead of once per app. It also bounds the walk that collects .env and
+# .env.local for a run.
+#
+# Nothing else is declared: 'release:' (where modules live, and where they
+# publish) is read by \`telo release\`, which does not run in a session.
 `;
 /**
  * The marker, unless the workspace already brings its own. A user whose project
- * really is a Telo workspace has a marker with a real \`modules:\` list, and
- * overwriting it would silently change what \`telo release\` discovers.
+ * really is a Telo workspace has a marker with a real \`release.modules\` list,
+ * and overwriting it would silently change what \`telo release\` discovers.
  */
 export function workspaceMarkerWrite(bundle) {
     const provided = bundle.files.some((f) => f.relativePath === WORKSPACE_MARKER_FILENAME);

package/dist/session/workspace-marker.js.map

@@ -1 +1 @@
-{"version":3,"file":"workspace-marker.js","sourceRoot":"","sources":["../../src/session/workspace-marker.ts"],"names":[],"mappings":"AAEA,+EAA+E;AAC/E,MAAM,CAAC,MAAM,yBAAyB,GAAG,qBAAqB,CAAC;AAE/D;;;;;;;;;;;;;GAaG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;CAMxC,CAAC;AAEF;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAClC,MAAiB;IAEjB,MAAM,QAAQ,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,YAAY,KAAK,yBAAyB,CAAC,CAAC;IACxF,IAAI,QAAQ;QAAE,OAAO,EAAE,CAAC;IACxB,OAAO,CAAC,EAAE,IAAI,EAAE,yBAAyB,EAAE,OAAO,EAAE,yBAAyB,EAAE,CAAC,CAAC;AACnF,CAAC"}
+{"version":3,"file":"workspace-marker.js","sourceRoot":"","sources":["../../src/session/workspace-marker.ts"],"names":[],"mappings":"AAEA,+EAA+E;AAC/E,MAAM,CAAC,MAAM,yBAAyB,GAAG,qBAAqB,CAAC;AAE/D;;;;;;;;;;;;;;;GAeG;AACH,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;;;;CASxC,CAAC;AAEF;;;;GAIG;AACH,MAAM,UAAU,oBAAoB,CAClC,MAAiB;IAEjB,MAAM,QAAQ,GAAG,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,YAAY,KAAK,yBAAyB,CAAC,CAAC;IACxF,IAAI,QAAQ;QAAE,OAAO,EAAE,CAAC;IACxB,OAAO,CAAC,EAAE,IAAI,EAAE,yBAAyB,EAAE,OAAO,EAAE,yBAAyB,EAAE,CAAC,CAAC;AACnF,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@telorun/runner-core",
-  "version": "0.13.0",
+  "version": "0.14.0",
   "description": "Backend-neutral core for Telo runners: the /v1 session contract, the RunnerBackend interface, the session registry, SSE/byte ring buffers, and bundle handling. Shared by docker-runner and k8s-runner.",
   "keywords": [
     "telo",

package/src/session/workspace-marker.test.ts

@@ -27,9 +27,14 @@ describe("workspaceMarkerWrite", () => {
     expect(workspaceMarkerWrite(bundle(["telo.yaml", WORKSPACE_MARKER_FILENAME]))).toEqual([]);
   });
 
-  it("writes a marker the workspace parser accepts", () => {
-    // An empty `modules:` is a hard error in that parser, so a marker seeded
-    // with one would be a file this repo's own tooling rejects.
-    expect(WORKSPACE_MARKER_CONTENTS).toMatch(/^modules: \[.+\]$/m);
+  it("declares no blocks — a session reads none of them", () => {
+    // It used to write `modules: ["*"]`, release scope a session has no use
+    // for, purely because an empty list was a parse error. A marker whose whole
+    // content is comments is valid, so the runner stops shipping a fabricated
+    // claim into every user's workspace.
+    expect(WORKSPACE_MARKER_CONTENTS.split("\n").filter((line) => line.trim() !== "")).toEqual(
+      expect.arrayContaining([expect.stringMatching(/^#/)]),
+    );
+    expect(WORKSPACE_MARKER_CONTENTS).not.toMatch(/^[A-Za-z]/m);
   });
 });

package/src/session/workspace-marker.ts

@@ -12,23 +12,28 @@ export const WORKSPACE_MARKER_FILENAME = "telo-workspace.yaml";
  * apps in one workspace resolve the same module twice into two caches — and an
  * app in a subdirectory gets a third.
  *
- * `modules:` is release scope and is read by `telo release` alone, which never
- * runs in a session. It is written anyway because an empty list is a hard error
- * in the parser, and a file this repo's own tooling would reject is not one to
- * seed into a user's workspace.
+ * **It declares no blocks.** Every field of the marker sits in a block scoped to
+ * the command that reads it, and a session runs none of them: `release:` is
+ * versioning and publishing, which never happens here. This used to write
+ * `modules: ["*"]` — release scope a session has no use for — purely because an
+ * empty list was a parse error, so the runner shipped a fabricated claim into
+ * every user's workspace to satisfy a reader that was never going to run.
  */
 export const WORKSPACE_MARKER_CONTENTS = `# Marks the root of this session's workspace.
 #
 # The Telo kernel anchors its module cache (.telo) at the directory holding this
 # file, so every application in this workspace resolves its imports once into one
-# cache instead of once per app.
-modules: ["*"]
+# cache instead of once per app. It also bounds the walk that collects .env and
+# .env.local for a run.
+#
+# Nothing else is declared: 'release:' (where modules live, and where they
+# publish) is read by \`telo release\`, which does not run in a session.
 `;
 
 /**
  * The marker, unless the workspace already brings its own. A user whose project
- * really is a Telo workspace has a marker with a real \`modules:\` list, and
- * overwriting it would silently change what \`telo release\` discovers.
+ * really is a Telo workspace has a marker with a real \`release.modules\` list,
+ * and overwriting it would silently change what \`telo release\` discovers.
  */
 export function workspaceMarkerWrite(
   bundle: RunBundle,