@markii/host 0.17.0-next.2 → 0.17.0-next.3

package/dist/browser.d.ts

@@ -1,7 +1,9 @@
 import type { NetProvider } from '@markii/lua';
 import type { HostIsolate } from './host/adapter.js';
 /** Builds the provider for one run from the job's host allowlist, byte cap and pin policy (the policy is meaningless in a browser and ignored). */
-export type BrowserNetProviderFactory = (netAllowlist: string[], maxFetchBytes: number, netPolicy: unknown) => NetProvider;
+export type BrowserNetProviderFactory = (netAllowlist: string[], maxFetchBytes: number, netPolicy: unknown, 
+/** Aborted when the isolate is killed or disposed. A provider cancels its in-flight requests on it. */
+signal?: AbortSignal) => NetProvider;
 export interface FetchNetProviderOptions {
     /**
      * The origins (`https://api.example.com`, `http://127.0.0.1:8080`) a
@@ -33,7 +35,9 @@ export interface FetchNetProviderOptions {
  * manual redirect's target, so it cannot be checked against the allowlist,
  * and a redirect is therefore a denial.
  *
- * Returns a factory because the byte cap arrives per job.
+ * Returns a factory because the byte cap arrives per job. Every request
+ * carries the run's `AbortSignal`, so killing the isolate cancels requests
+ * still in flight.
  */
 export declare function createFetchNetProvider(options?: FetchNetProviderOptions): BrowserNetProviderFactory;
 export interface BrowserHostIsolateOptions {

package/dist/browser.js

@@ -74,14 +74,16 @@ async function readCapped(response, maxBytes, denial) {
  * manual redirect's target, so it cannot be checked against the allowlist,
  * and a redirect is therefore a denial.
  *
- * Returns a factory because the byte cap arrives per job.
+ * Returns a factory because the byte cap arrives per job. Every request
+ * carries the run's `AbortSignal`, so killing the isolate cancels requests
+ * still in flight.
  */
 export function createFetchNetProvider(options = {}) {
     const allowed = new Set((options.allowedOrigins ?? [])
         .map(originOf)
         .filter((origin) => origin !== undefined));
     const denial = options.denial ?? ((message) => new Error(message));
-    return (netAllowlist, maxFetchBytes) => {
+    return (netAllowlist, maxFetchBytes, _policy, signal) => {
         // The run's granted hosts, re-checked here on the page side: the worker
         // checks them too, but the worker is the isolate a hostile script runs
         // in, so the page is the boundary (the same rule the Node provider
@@ -107,6 +109,8 @@ export function createFetchNetProvider(options = {}) {
             if (!allowed.has(url.origin)) {
                 throw denial(`origin "${url.origin}" is not on the host's allowlist`);
             }
+            if (signal?.aborted)
+                throw denial('the run has ended');
             const doFetch = options.fetch ?? fetch;
             let response;
             try {
@@ -118,6 +122,7 @@ export function createFetchNetProvider(options = {}) {
                     redirect: 'manual',
                     credentials: 'omit',
                     referrerPolicy: 'no-referrer',
+                    ...(signal !== undefined ? { signal } : {}),
                 });
             }
             catch (error) {

package/dist/host/adapter.d.ts

@@ -3,8 +3,7 @@
  * the CLI, or a future one) provides so `createMarkiiHost` can run every
  * shared behavior once. Nothing in this file names a `vscode`, `obsidian`,
  * Electron or TTY type — an adapter is built from injected dependencies,
- * so a test can construct the REAL adapter over fakes (batch 11's
- * `tmp/W11-adapter-design.md`, section 2).
+ * so a test can construct the REAL adapter over fakes.
  *
  * A capability group (`isolate`, `editor`, `packs`, `exports`) is absent
  * when a host does not offer it. `createMarkiiHost` never assumes one is
@@ -23,9 +22,7 @@ export interface HostDirEntry {
 }
 /**
  * One yes/no question. Every grant, consent, and replace prompt in the
- * whole app surface routes through this single method (survey finding A1:
- * nine near-identical prompt adapters across three apps collapse to one
- * call each). `message`, `allowLabel`, and `denyLabel` are already fully
+ * whole app surface routes through this single method. `message`, `allowLabel`, and `denyLabel` are already fully
  * built by `@markii/host`; the adapter only has to show them.
  */
 export interface HostPromptRequest {
@@ -43,7 +40,7 @@ export interface HostPromptRequest {
 }
 /**
  * A discriminated union: `workerPath` and `workerBytes` are mutually
- * exclusive per host (survey section C). A Node host (VS Code, the CLI)
+ * exclusive per host. A Node host (VS Code, the CLI)
  * gives a synchronous path lookup; a host whose runtime cannot create
  * worker threads (an Electron renderer, which is what the Obsidian plugin
  * runs in) gives an async, disposable Web Worker spawner instead.
@@ -51,15 +48,14 @@ export interface HostPromptRequest {
 export type HostIsolate = {
     readonly kind: 'node';
     /**
-     * The worker entry on disk. A host with a packaged worker resolves it
-     * here; a development or test run falls back to
-     * `defaultWorkerPath()` from `@markii/host/node`, in the host's own
-     * adapter (the shared run path has no Node dependency to do it).
+     * The worker entry on disk. A host with its own bundled worker
+     * resolves it here. `createNodeHostIsolate()` from
+     * `@markii/host/node` supplies the packaged one.
      */
     workerPath(): string;
     /**
-     * Creates the worker-thread isolate. Always `workerThreadIsolate`
-     * from `@markii/host/node`; injected so the shared run path imports
+     * Creates the worker-thread isolate: `workerThreadIsolate` from
+     * `@markii/host/node`. Injected so the shared run path imports
      * nothing from `node:*`.
      */
     readonly spawnIsolate: IsolateSpawner;
@@ -106,7 +102,7 @@ export interface HostEditor {
 }
 /**
  * Pack POLICY (which folders are even candidates) is irreducibly
- * host-specific (survey section D); everything after the list exists is
+ * host-specific; everything after the list exists is
  * already shared in `../packs/discover.ts` and friends. The adapter
  * supplies only the list and the install destination.
  */
@@ -124,12 +120,13 @@ export interface HostPackSource {
      * `'device-list'`: a folder in `installRoot` loads only when the trust
      * list in the adapter's `memento` names its namespace, and the host
      * gains `installedPacks`, `enablePack` and `disablePack`. An install
-     * trusts the pack it installs. Requires `installRoot`. `'none'` (or
-     * absent): every folder this host's own policy authorizes loads, which
-     * is right for a host that trusts its own install store (VS Code, the
-     * CLI). A host states its choice explicitly.
+     * trusts the pack it installs. Requires `installRoot`. `'none'`: every
+     * folder this host's own policy authorizes loads, which is right for a
+     * host that trusts its own install store (VS Code, the CLI). A web host
+     * that installs packs from users picks `'device-list'`. Required: a
+     * host states its choice explicitly.
      */
-    readonly trust?: 'device-list' | 'none';
+    readonly trust: 'device-list' | 'none';
     /**
      * Folders this host currently AUTHORIZES. Under `trust: 'device-list'`
      * these are the folders beyond the install root (the host adds the
@@ -167,10 +164,8 @@ export interface HostExportCapabilities {
 }
 /**
  * The wording nouns every shared behavior's message templates interpolate
- * (`./labels.ts`). This is the one answer to the survey's wording-drift
- * risk: near-identical copy across the three apps collapses into one
- * template plus these per-host nouns, instead of a per-host
- * reimplementation of the sentence itself.
+ * (`./labels.ts`). One template plus these per-host nouns
+ * replaces a per-host copy of each sentence.
  */
 export interface HostLabels {
     /** "extension" | "plugin" | "command line tool" */
@@ -196,7 +191,7 @@ export interface HostLabels {
  * Everything an adapter provides. An adapter is constructible from
  * injected dependencies (no module-scope global reads), which is what
  * lets a conformance test build the REAL adapter over a fake editor
- * (batch 11 Phase 3).
+ *.
  */
 export interface HostAdapter {
     readonly id: 'vscode' | 'obsidian' | 'cli' | (string & {});

package/dist/host/conformance-runner.d.ts

@@ -1,3 +1,4 @@
+import type { ArchiveExtractFs } from './pack-archive.js';
 import type { RunTrigger } from '@markii/runtime';
 import type { HostAdapter } from './adapter.js';
 /**
@@ -110,7 +111,7 @@ export declare function hostDeclaresCapability(adapter: HostAdapter, action: Hos
  * `next()` THROWS once exhausted rather than returning a default: an
  * unanswered prompt means the scenario and the implementation disagree
  * about how many questions get asked, which must never be silently read
- * as a deny (`tmp/W11-corpus-design.md`, "The prompt policy").
+ * as a deny.
  */
 export declare function createAnswerQueue(scenario: HostScenario): {
     next(): boolean;
@@ -134,6 +135,8 @@ export interface HostScenarioRunResult {
  */
 export declare function runHostScenario(adapter: HostAdapter, scenario: HostScenario, noteText: string, scenarioDir: string, options?: {
     readonly renderAnsi?: (text: string) => Promise<string>;
+    /** Where an installed pack archive is extracted. Defaults to the Node file system, which is right for an adapter that reads and writes real files. An adapter over another store (memory, a virtual file system) passes the matching writer. */
+    readonly archiveExtractFs?: ArchiveExtractFs;
 }): Promise<HostScenarioRunResult>;
 /** `expected[i]` compared against `actual[i]` for each index up to `expected`'s own length; a length mismatch is reported once rather than index-by-index noise. */
 export declare function containsInOrder(actual: readonly string[], expected: readonly string[]): string[];

package/dist/host/conformance-runner.js

@@ -1,6 +1,5 @@
 /**
- * Executes one `conformance/host/<scenario>` case (batch 11 Phase 3,
- * `tmp/W11-corpus-design.md`) against any real `HostAdapter`, so a single
+ * Executes one `conformance/host/<scenario>` case against any real `HostAdapter`, so a single
  * plain-data corpus proves the three apps' adapters behave the same.
  *
  * `conformance/host/` itself stays plain data (no TypeScript, matching the
@@ -26,8 +25,7 @@
  * pre-check here, over the same shared functions and the SAME
  * `adapter.labels` a real call site would use, so the scenario proves
  * wording parity across hosts without inventing a capability the contract
- * does not have. See `tmp/W11-phase3.md` for why this is a reported
- * finding, not a silent workaround.
+ * does not have. The scenario `10-scripts-disabled` holds the behavior.
  *
  * SIMULATED EXECUTION. A `run` action's `simulate` field (plain data) tells
  * this module what the isolate would have produced, instead of spawning a
@@ -162,7 +160,7 @@ export function hostDeclaresCapability(adapter, action) {
  * `next()` THROWS once exhausted rather than returning a default: an
  * unanswered prompt means the scenario and the implementation disagree
  * about how many questions get asked, which must never be silently read
- * as a deny (`tmp/W11-corpus-design.md`, "The prompt policy").
+ * as a deny.
  */
 export function createAnswerQueue(scenario) {
     const answers = [];
@@ -264,7 +262,7 @@ export async function runHostScenario(adapter, scenario, noteText, scenarioDir,
         // The runner is Node-only test tooling, so it supplies the real Node
         // implementations of the seams the host layer takes by injection.
         htmlEngine: createHtmlExportEngine(),
-        archiveExtractFs: createNodeArchiveExtractFs(),
+        archiveExtractFs: options.archiveExtractFs ?? createNodeArchiveExtractFs(),
         spawnRun: (spawnOptions) => Promise.resolve(simulatedRunResult(currentSimulation, spawnOptions)),
         ...(options.renderAnsi ? { renderAnsi: options.renderAnsi } : {}),
     });

package/dist/host/create-host.d.ts

@@ -3,13 +3,11 @@
  * its own run/export/pack/editor wiring. Everything it touches (files, prompts,
  * the isolate) arrives through the adapter, so the main entry stays
  * environment-neutral. VS Code's webview imports only the pure pieces and
- * never calls this function (`tmp/W11-adapter-design.md`, section 1).
+ * never calls this function.
  *
- * Phase 1a implemented `run`, `diagnostics`, and `open`. This phase
- * (1b) fills in `exportNote`, `installPack`, `loadPacks`, `completeAt`,
- * `hoverAt`, and `insertComponent`, over the behavior modules built in
- * this same pass (`./export-behavior.js`, `./pack-install.js`,
- * `./pack-load.js`, `./editor-behavior.js`). Every one of them still
+ * It provides `run`, `diagnostics`, `open`, `exportNote`, `installPack`, `loadPacks`, `completeAt`,
+ * `hoverAt`, and `insertComponent`, over the behavior modules (`./export-behavior.js`, `./pack-install.js`,
+ * `./pack-load.js`, `./editor-behavior.js`). Every one of them
  * returns the shared `Unsupported` outcome, with one diagnostics line,
  * when the adapter lacks the capability it needs — AGENTS.md's "clean is
  * not silent": a decline is never a silent no-op.

package/dist/host/editor-behavior.d.ts

@@ -4,12 +4,8 @@ import type { HostEditor, HostTextEdit } from './adapter.js';
 export declare const STANDARD_ORIGIN_TAG = "standard";
 export declare const LAYOUT_ORIGIN_TAG = "layout";
 /**
- * Survey finding A5: `apps/vscode/src/completion.ts:completionOriginTag`
- * and `apps/obsidian/src/complete-component.ts:completionOriginTag` had
- * IDENTICAL function bodies, differing only in which locally-defined
- * constant stood in for the standard/layout tag string. Both apps'
- * constants held the same lower-case values (`'standard'`/`'layout'`),
- * so there was never a wording difference to preserve.
+ * The origin tag a completion item carries: the lower-case
+ * `'standard'`/`'layout'` strings above, or the pack name.
  */
 export declare function completionOriginTag(item: CompletionItem): string;
 /** A small cache in front of `buildComponentCatalog` (`../insert/component-catalog.js`), so a completion/hover provider does not re-discover packs from disk on every keystroke. */

package/dist/host/editor-behavior.js

@@ -2,16 +2,16 @@
  * The `completeAt`/`hoverAt`/`insertComponent` behaviors' shared half,
  * merged from `apps/vscode/src/completion.ts` + `completion-catalog.ts`,
  * `apps/obsidian/src/complete-component.ts`, and both apps'
- * `insert-component.ts` (survey finding A5, plus table rows 31/33).
+ * `insert-component.ts`.
  *
- * NODE-FREE by design (`tmp/W11-adapter-design.md`, section 1): re-exported
+ * NODE-FREE by design: re-exported
  * from `../browser.ts` as well as `../index.ts`, so VS Code's webview
  * bundle can read the origin-tag vocabulary and the pure completion math
  * directly if a future slice needs to. `CatalogCache.get`'s injected
  * `load` is the one thing that reaches disk, and it is always supplied by
  * the caller (a main-entry-only pack-discovery call), never imported here.
  *
- * What stays app-side (deliberately, per the survey's section D): VS
+ * What stays app-side (deliberately): VS
  * Code's sectioned quick-pick presentation (`Standard`/`Layout`/`<pack>
  * pack` separators) and Obsidian's flat fuzzy list are a genuine product
  * difference, not duplication — this module returns the catalog and the
@@ -25,12 +25,8 @@ import { closesOpenContainerFence, completionAt, componentDocumentation, fenceEx
 export const STANDARD_ORIGIN_TAG = 'standard';
 export const LAYOUT_ORIGIN_TAG = 'layout';
 /**
- * Survey finding A5: `apps/vscode/src/completion.ts:completionOriginTag`
- * and `apps/obsidian/src/complete-component.ts:completionOriginTag` had
- * IDENTICAL function bodies, differing only in which locally-defined
- * constant stood in for the standard/layout tag string. Both apps'
- * constants held the same lower-case values (`'standard'`/`'layout'`),
- * so there was never a wording difference to preserve.
+ * The origin tag a completion item carries: the lower-case
+ * `'standard'`/`'layout'` strings above, or the pack name.
  */
 export function completionOriginTag(item) {
     if (item.kind !== 'component')

package/dist/host/export-behavior.d.ts

@@ -2,7 +2,7 @@
  * The `exportNote` behavior: outcome shape, wording, and format gating,
  * merged from `apps/vscode/src/export-html.ts`, the host-neutral half of
  * `apps/obsidian/src/export-note.ts`, and `apps/cli/src/export-note.ts`'s
- * `exportHtml` (survey finding A10, table rows 22/26).
+ * `exportHtml`.
  *
  * `html` and `md-plain` are fully implemented here, over `../export/note-export.js`'s
  * `buildNoteExport` (already host-neutral, already shared) and
@@ -12,20 +12,18 @@
  * AGENTS.md's package boundaries), so it is rendered through the injected
  * `renderAnsi` option; a host that omits it gets `Unsupported`.
  *
- * PDF stays a seam, never an implementation here, exactly as
- * `tmp/W11-adapter-design.md` specifies: this module builds the same HTML
+ * PDF stays a seam, never an implementation here, this module builds the same HTML
  * document `html` would have written and hands it to
  * `adapter.exports.htmlToPdf`, but the DEGRADE-TO-HTML-ON-FAILURE product
  * behavior Obsidian's own `exportNoteAsPdf` layers on top (falling back to
  * writing the HTML file when printing is unavailable or fails, and
  * reporting which of the two happened) is Obsidian-specific policy about
  * what to do with a seam's failure, not the seam itself — it stays
- * app-side. See `tmp/W11-phase1b.md` for this call.
+ * app-side.
  *
  * Cascade orchestration (multi-note export, `walkNoteCascade` +
  * `assignCascadeFileNames` + `rewriteCascadeLinks` + `zipExportArchive`)
- * is NOT moved in this pass — see `tmp/W11-phase1b.md`'s deviations
- * section for why, and what Phase 2 (or a follow-up) still needs to do.
+ * is not part of this module: it stays with each host.
  */
 import type { StoredValue } from '@markii/runtime';
 import type { OnDiagnostic, UnavailableComponent } from '@markii/stdlib';

package/dist/host/labels.d.ts

@@ -3,8 +3,7 @@
  * (`./script-execution.ts`, `./refresh-interval.ts`) interpolates, and the
  * one concrete record per app this repo ships. Each app's `HostAdapter`
  * imports its record rather than inventing its own strings, which is what
- * collapses the survey's near-identical wording pairs (`tmp/W11-survey.md`,
- * section A4) into one template.
+ * lets one template serve every host.
  *
  * Pure and dependency-free: re-exported from `../browser.ts` as well as
  * `../index.ts` so VS Code's Node-free webview bundle can read it too.

package/dist/host/pack-archive.js

@@ -1,13 +1,7 @@
 /**
  * `.mkp` pack archive handling, merged from `apps/vscode/src/packs/archive-packs.ts`
- * and `apps/obsidian/src/packs/archive-packs.ts` (survey finding A8). The
- * orchestrator diffed the two files directly (not through the survey's
- * earlier, unverified guess) and found them functionally byte-identical:
- * the same three exports (`describeArchiveError`, `writeArchiveContents`,
- * `ArchiveExtractFs`), the same implementation, the same path-jail
- * reasoning. They differed only in doc-comment wording (which host's
- * install command they described) and one em dash in a comment, which
- * carries no behavior. See `tmp/W11-phase1b.md` for the exact diff output.
+ * and `apps/obsidian/src/packs/archive-packs.ts`. It exports
+ * `describeArchiveError`, `writeArchiveContents` and `ArchiveExtractFs`.
  *
  * This module bridges `@markii/pack`'s in-memory archive reader
  * (`openPackArchive`, never modified here) into the write a pack install

package/dist/host/pack-install.d.ts

@@ -67,8 +67,7 @@ export declare function installConsentMessage(packName: string, labels: HostLabe
 /**
  * The collision confirmation's wording: a namespace already installed,
  * asked before replacing it. CANONICAL WORDING: "removes" (VS Code's prior
- * wording) over Obsidian's prior "deletes" — see `tmp/W11-phase1b.md`'s
- * before/after table for the exact strings this replaces.
+ * wording) over Obsidian's prior "deletes".
  */
 export declare function installReplaceConfirmMessage(packName: string): string;
 /**

package/dist/host/pack-install.js

@@ -1,11 +1,9 @@
 /**
  * The `.mkp` pack-install decision logic, merged from
  * `apps/vscode/src/packs/install-pack.ts` and
- * `apps/obsidian/src/packs/install-pack.ts` (survey finding A2: the single
- * biggest duplication finding in the survey — identical function names,
- * identical types, near-identical wording, differing only in that
- * Obsidian refuses a bundled-namespace archive before the consent prompt
- * and VS Code has no such concept).
+ * `apps/obsidian/src/packs/install-pack.ts`. Obsidian refuses a
+ * bundled-namespace archive before the consent prompt and VS Code has no
+ * such concept.
  *
  * `reservedNamespaces` generalizes Obsidian's `bundledNamespaces`: it
  * defaults to empty, so VS Code's behavior is byte-identical to before
@@ -131,8 +129,7 @@ export function installConsentMessage(packName, labels) {
 /**
  * The collision confirmation's wording: a namespace already installed,
  * asked before replacing it. CANONICAL WORDING: "removes" (VS Code's prior
- * wording) over Obsidian's prior "deletes" — see `tmp/W11-phase1b.md`'s
- * before/after table for the exact strings this replaces.
+ * wording) over Obsidian's prior "deletes".
  */
 export function installReplaceConfirmMessage(packName) {
     return `A pack named "${packName}" is already installed. Replacing it removes the installed copy and cannot be undone.`;

package/dist/host/pack-load.d.ts

@@ -1,8 +1,7 @@
 /**
  * The shared discovery path behind `loadPacks`, merged from
  * `apps/vscode/src/packs/discover-configured-packs.ts` and
- * `apps/obsidian/src/packs/discover-configured-packs.ts` (survey finding
- * A3) plus the discovery-and-namespace-collection half both apps'
+ * `apps/obsidian/src/packs/discover-configured-packs.ts` plus the discovery-and-namespace-collection half both apps'
  * `packs/pack-context.ts` also duplicate on top of it.
  *
  * Pack POLICY — which folders are even candidates before any content is

package/dist/host/pack-trust-behavior.js

@@ -12,7 +12,7 @@
  * already asked), enabling a present folder asks the same prompt, and
  * disabling or removing withdraws the entry.
  *
- * A host that declares `trust: 'none'` (or omits the field) trusts every
+ * A host that declares `trust: 'none'` trusts every
  * folder its own policy authorizes, and every function here is inert for
  * it. Neutral on purpose: only the adapter's file and state primitives
  * are used.

package/dist/host/refresh-interval.d.ts

@@ -3,9 +3,7 @@
  * merged from `apps/vscode/src/refresh-interval.ts` (the input-box
  * parse/validate half) and `apps/obsidian/src/local-settings.ts`'s
  * `refreshIntervalMsFromSeconds`/`MIN_REFRESH_INTERVAL_SECONDS` (the
- * read-side clamp half) — survey finding A7: the constant was duplicated
- * verbatim, with Obsidian's own comment noting it mirrors VS Code's, and
- * the clamp-not-reject policy was duplicated as both prose and behavior.
+ * read-side clamp half).
  *
  * The policy: a positive value under `MIN_REFRESH_INTERVAL_SECONDS` is
  * still ACCEPTED as typed (a host's own settings UI must not silently

package/dist/host/refresh-interval.js

@@ -3,9 +3,7 @@
  * merged from `apps/vscode/src/refresh-interval.ts` (the input-box
  * parse/validate half) and `apps/obsidian/src/local-settings.ts`'s
  * `refreshIntervalMsFromSeconds`/`MIN_REFRESH_INTERVAL_SECONDS` (the
- * read-side clamp half) — survey finding A7: the constant was duplicated
- * verbatim, with Obsidian's own comment noting it mirrors VS Code's, and
- * the clamp-not-reject policy was duplicated as both prose and behavior.
+ * read-side clamp half).
  *
  * The policy: a positive value under `MIN_REFRESH_INTERVAL_SECONDS` is
  * still ACCEPTED as typed (a host's own settings UI must not silently

package/dist/host/run-behavior.d.ts

@@ -1,7 +1,6 @@
 /**
  * The `run` behavior's host-shaped seams, built from a `HostAdapter`:
- * this is where survey findings A1 and A6 stop being duplicated three
- * times over.
+ * the grant prompts and the isolate spawn live here once for every host.
  *
  * A1: `apps/vscode/src/preview-panel.ts`'s `promptHostAdapter` /
  * `promptUnknownHostsAdapter` / `promptManyHostsAdapter`,
@@ -24,7 +23,7 @@
  * `runOnce` (the existing, already-shared grant-flow-plus-spawn
  * orchestration) and writes the `RunTrace` through `adapter.now()` rather
  * than `Date.now()`, so a fixed clock in a test fake makes the trace
- * byte-stable (batch 11 Phase 3's requirement).
+ * byte-stable.
  */
 import type { RunTrigger } from '@markii/runtime';
 import { type PromptHost, type PromptManyHosts, type PromptUnknownHosts } from '../run/grant-flow.js';
@@ -54,7 +53,7 @@ export declare function promptsFromAdapter(adapter: HostAdapter): {
 };
 /**
  * The one `spawnRun` adapter every Node host (`apps/vscode`, `apps/cli`)
- * used to duplicate (survey A6), plus the browser-isolate path Obsidian's
+ * needs, plus the browser-isolate path Obsidian's
  * own `spawnRun` wrapper needed. Dispatches on `HostIsolate`'s
  * discriminated union: a `'node'` host supplies only a worker path; a
  * `'browser'` host supplies an async, disposable `IsolateSpawner` factory,

package/dist/host/run-behavior.js

@@ -63,9 +63,23 @@ function noIsolateResult(cacheSnapshot) {
         cacheSnapshot,
     };
 }
+/** A synthetic `RunResult` for a node isolate whose worker file cannot be located. The run never throws. */
+function workerMissingResult(cacheSnapshot, error) {
+    return {
+        values: {},
+        failures: [
+            {
+                name: '<document>',
+                message: `the script worker could not be located: ${error instanceof Error ? error.message : String(error)}`,
+                kind: 'capability-denied',
+            },
+        ],
+        cacheSnapshot,
+    };
+}
 /**
  * The one `spawnRun` adapter every Node host (`apps/vscode`, `apps/cli`)
- * used to duplicate (survey A6), plus the browser-isolate path Obsidian's
+ * needs, plus the browser-isolate path Obsidian's
  * own `spawnRun` wrapper needed. Dispatches on `HostIsolate`'s
  * discriminated union: a `'node'` host supplies only a worker path; a
  * `'browser'` host supplies an async, disposable `IsolateSpawner` factory,
@@ -75,9 +89,16 @@ export async function spawnRunViaAdapter(isolate, options) {
     if (!isolate)
         return noIsolateResult(options.cacheSnapshot);
     if (isolate.kind === 'node') {
+        let workerPath;
+        try {
+            workerPath = isolate.workerPath();
+        }
+        catch (error) {
+            return workerMissingResult(options.cacheSnapshot, error);
+        }
         return spawnRunHost({
             ...options,
-            workerPath: isolate.workerPath(),
+            workerPath,
             spawnIsolate: isolate.spawnIsolate,
         });
     }

package/dist/host/script-execution.d.ts

@@ -1,7 +1,7 @@
 /**
  * The device-level script-execution switch and every sentence it can
  * produce, merged from `apps/vscode/src/script-execution.ts` and
- * `apps/obsidian/src/script-execution.ts` (survey finding A4: same file
+ * `apps/obsidian/src/script-execution.ts` (same file
  * name, same four exports, doc comments sharing the same "WHAT IT IS /
  * WHY DEVICE-LOCAL / WHY THE WORDING LIVES HERE" structure, differing
  * only in a handful of words).

package/dist/index.js

@@ -4,8 +4,7 @@
 // `esbuild-wasm`, `@markii/react` or `@markii/html` at runtime
 // (`apps/vscode/src/browser-entry.probe.test.ts` bundles it for a browser to
 // prove it). What needs Node lives in `./node.ts`, published as
-// `@markii/host/node`. Private workspace package: never published,
-// never added to `build:dist`. See AGENTS.md's repo-layout entry for
+// `@markii/host/node`. See AGENTS.md's repo-layout entry for
 // `packages/markii-host` for the module-by-module breakdown.
 //
 // This is the security-critical layer (tier gating, the grant model,