@mulmoclaude/mulmoscript-plugin 4.5.0 → 4.5.2

package/dist/server.js

@@ -18,6 +18,29 @@ async function fileToDataUri(filePath, mimeType) {
 	return `data:${mimeType};base64,${(await readFile(filePath)).toString("base64")}`;
 }
 //#endregion
+//#region src/server/types.ts
+/**
+* Host capabilities the server ops run against. Only genuinely
+* host-specific transport lives here — the mulmocast orchestration, path
+* containment, and generation-state tracking are all in-package.
+*/
+/**
+* Which named-root capabilities a host has NOT wired.
+*
+* Pure and exported so the rule can be tested without building a server: the
+* condition used to key on the root COUNT alone, so a host that HAD passed
+* `artifactsFor` was told at every boot that its writes land in the default
+* root — the opposite of what the code then did (#3022).
+*
+* Reads and uploads need nothing from the host, so they never appear here.
+*/
+function missingRootCapabilities(backend) {
+	const missing = [];
+	if (backend.rootScopedGenerationState !== true) missing.push("GENERATION is refused until this host declares `rootScopedGenerationState` (its pending-generation state must carry the root, or it must keep none)");
+	if (backend.artifactsFor === void 0) missing.push("save/update land in the DEFAULT root until this host passes `artifactsFor`");
+	return missing;
+}
+//#endregion
 //#region src/server/mulmoErrorCapture.ts
 var capturedErrors = new AsyncLocalStorage();
 var loggerInstalled = false;
@@ -194,7 +217,29 @@ function createMulmoScriptServerOps(backend) {
 		if (rootDirs.has(trimmed)) throw new Error(`mulmoScript: extraRoots keys must be distinct after trimming — "${trimmed}" is registered twice`);
 		rootDirs.set(trimmed, path.resolve(dir));
 	}
-	if (rootDirs.size > 1) log.warn(backend.rootScopedGenerationState === true ? "extra stories roots registered — reads, uploads and generation work; save/update still land in the DEFAULT root until this host passes `artifactsFor` (#3019)" : "extra stories roots registered — reads and uploads work, but GENERATION is refused until this host declares `rootScopedGenerationState` (its pending-generation state must carry the root, or it must keep none), and save/update land in the DEFAULT root until it passes `artifactsFor` (#3019)", { roots: [...rootDirs.keys()].filter((id) => id !== "") });
+	warnAboutUnwiredRoots();
+	/**
+	* Tell a host which named-root capabilities it has not wired — and nothing
+	* when it has wired them all.
+	*
+	* The condition used to be the root COUNT alone, so a host that had passed
+	* `artifactsFor` was still told, at every boot, that its writes land in the
+	* default root. That is not a stale wording: it is the opposite of what the
+	* code then does, read by the hosts that got the wiring RIGHT (#3022, from
+	* the consuming host).
+	*
+	* Silence when nothing is missing, because a warning that always fires is
+	* one people learn to skip — and then the host that really did forget
+	* `artifactsFor` cannot tell either. Each clause is emitted only when that
+	* capability is actually absent, so the message says what is true for THIS
+	* host rather than what was true when it was written.
+	*/
+	function warnAboutUnwiredRoots() {
+		if (rootDirs.size <= 1) return;
+		const missing = missingRootCapabilities(backend);
+		if (missing.length === 0) return;
+		log.warn(`extra stories roots registered — reads and uploads work, but ${missing.join(", and ")} (#3019)`, { roots: [...rootDirs.keys()].filter((id) => id !== "") });
+	}
 	/** The registered directory for a wire `root`, or null when the host never
 	*  registered it. Null is a REJECTION, not a fallback to the default: an
 	*  unknown root must not quietly read the workspace's file of the same
@@ -335,12 +380,21 @@ function createMulmoScriptServerOps(backend) {
 	* It opens per root, not globally: the host answers `artifactsFor` for the
 	* roots it can serve, and a root it cannot is still refused. A host that
 	* wires nothing keeps the shipped refusal (#3019).
+	*
+	* The two refusals say different things because they are fixed in different
+	* places. No `artifactsFor` at all is a capability this host has not turned
+	* on. `artifactsFor` present but answering `null` for a REGISTERED root is a
+	* wiring mistake inside that host — and it is the quiet one, because the
+	* boot warning stays silent (the resolver WAS passed) while every write is
+	* refused. One message for both read as "the plugin cannot do this yet",
+	* which sends the host looking in the wrong place (#3024).
 	*/
 	function guardStoryWriteRoot(root) {
 		if (normalizeRoot(root) === "") return null;
 		const registered = guardStoryRootRegistered(root);
 		if (registered) return registered;
-		return artifactsForRoot(root) === null ? opBadRequest("writing to a non-default stories root is not supported yet") : null;
+		if (artifactsForRoot(root) !== null) return null;
+		return backend.artifactsFor === void 0 ? opBadRequest("writing to a non-default stories root is not supported yet") : opBadRequest(`this host's \`artifactsFor\` returned no FileOps for the registered stories root "${normalizeRoot(root)}"`);
 	}
 	/**
 	* The FileOps a write to this root must go through.