@plurnk/plurnk-execs 1.0.0 → 1.0.2

package/SPEC.md

@@ -117,6 +117,8 @@ MCP is the proof, not the exception: `plurnk-execs-mcp` is a plain producer —
 
 **Entry materialization is a sink, not a substrate breach (execs#18 / service#340).** `ExecArgs.entry?(path, content, { tags, mimetype }) → Promise<void>` lets an executor *request* that the consumer materialize a substrate entry — the same shape as `write`/`emit` (consumer-implemented callbacks; the executor never touches storage, tagging, or announcement machinery). The consumer creates the entry, applies the tags, and announces it through its ambience as a **folded** row (the meta line carries path + tokens; page-scale bodies never ride a wake packet). Consumer collision semantics: upsert content, union tags, bump freshness. A rejected `entry()` means *not materialized* — the requesting executor must treat that item as failed (search prunes its digest row). The sink is optional: absent, producers degrade gracefully (search emits its digest without materializing). This closed the gap that §2.6's earlier absolutism forced on the search flow (a double-fetch dance routed around the missing sink); the principle — executors own zero substrate machinery — is unchanged.
 
+**The search dead-row seam resolves here (execs#18 hub's "open specifics" are stale — this supersedes them).** The consumer implements `entry()` *as* the auto-prefetch: fetch, render, materialize the `https://` entry — so its resolve/reject **is** the liveness verdict, and the executor prunes the failed digest row (per the pruning rule above). The digest emitted is survivors-only in a **single pass**: no executor pre-validation (that would fetch — forbidden), no consumer post-filter of a candidate list, no double fetch. A URL prefetch carries no page body for the executor to supply, so `content` is **consumer-sourced** — the executor contributes the candidate `url` as `path` and the consumer derives the body from it; the executor learns liveness only through the verdict, never by reading.
+
 ## §3 Discovery
 
 `discover(options?) → { registry }`. Scans **every installed package** under `<cwd>/node_modules` — scope-agnostic (scoped and unscoped) — for those declaring `plurnk.kind === "exec"`, and registers each runtime tag from `plurnk.runtimes[]`. The scan is deliberately not limited to `@plurnk/*`: a **third party** can publish an executor under their own scope (`@acme/acme-execs-foo`) and have it discovered with no involvement from this project. (For the batteries-included set, an aggregator package — `@plurnk/plurnk-execs-all` — depends on the framework's daughters flat so one install surfaces them all; the framework itself stays contract-only.)

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-execs",
-    "version": "1.0.0",
+    "version": "1.0.2",
     "description": "Framework + contract for the @plurnk/plurnk-execs-* runtime executor family.",
     "keywords": [
         "plurnk",
@@ -27,8 +27,8 @@
     },
     "exports": {
         ".": {
-            "types": "./dist/index.d.ts",
             "plurnk-dev": "./src/index.ts",
+            "types": "./dist/index.d.ts",
             "default": "./dist/index.js"
         },
         "./package.json": "./package.json"
@@ -48,13 +48,14 @@
         "prepack": "npm run build"
     },
     "dependencies": {
-        "@plurnk/plurnk-schemes": "1.0.0",
-        "@plurnk/plurnk-execs-common": "1.0.0",
-        "@plurnk/plurnk-execs-search": "1.0.0",
-        "@plurnk/plurnk-execs-mcp": "1.0.0",
-        "@plurnk/plurnk-execs-git": "1.0.0",
-        "@plurnk/plurnk-execs-jq": "1.0.0",
-        "@plurnk/plurnk-execs-sqlite": "1.0.0",
-        "@plurnk/plurnk-meta": "1.0.0"
+        "@plurnk/plurnk-schemes": "1.0.2",
+        "@plurnk/plurnk-execs-common": "1.0.2",
+        "@plurnk/plurnk-execs-search": "1.0.2",
+        "@plurnk/plurnk-execs-mcp": "1.0.2",
+        "@plurnk/plurnk-execs-git": "1.0.2",
+        "@plurnk/plurnk-execs-jq": "1.0.2",
+        "@plurnk/plurnk-execs-sqlite": "1.0.2",
+        "@plurnk/plurnk-meta": "1.0.2",
+        "@plurnk/plurnk-execs-wasm": "1.0.2"
     }
 }