@plurnk/plurnk-execs 1.23.0 → 1.25.0

package/SPEC.md

@@ -263,8 +263,12 @@ under a per-probe timeout, then caches each verdict. This is intentionally
 per-tag: a multi-tag package can expose only the interpreters actually present.
 A probe that spawns or opens a connection passes the supplied signal through so
 completion or timeout reaps its work. Probe rejection or timeout makes only
-that tag unavailable; a configured default runtime that is absent or
-unavailable is a fail-hard boot error.
+that tag unavailable. No particular executor is required to start the host.
+Typed `ConfigurationError` failures during module loading, construction, or
+probing retain the tag's declaration and diagnostic without publishing an
+executable or output scheme; unrelated tags remain available. Constructors
+must not report internal implementation defects as configuration errors.
+Core owns startup diagnostics and demand refusal in {§configuration-repair-path}.
 
 ## §executor-output-address Tag-addressed output
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plurnk/plurnk-execs",
-  "version": "1.23.0",
+  "version": "1.25.0",
   "description": "Framework + contract for the @plurnk/plurnk-execs-* runtime executor packages.",
   "keywords": [
     "plurnk",
@@ -50,9 +50,9 @@
     "prepublishOnly": "npm audit --audit-level=moderate && npm test"
   },
   "dependencies": {
-    "@plurnk/plurnk-contracts": "1.23.0",
-    "@plurnk/plurnk-parser": "1.23.0",
-    "@plurnk/plurnk-meta": "1.23.0",
-    "@plurnk/plurnk-schemes": "1.23.0"
+    "@plurnk/plurnk-contracts": "1.25.0",
+    "@plurnk/plurnk-parser": "1.25.0",
+    "@plurnk/plurnk-meta": "1.25.0",
+    "@plurnk/plurnk-schemes": "1.25.0"
   }
 }