@plurnk/plurnk-execs 0.4.42 → 0.4.44

package/.env.defaults

@@ -0,0 +1,12 @@
+# --- @plurnk/plurnk-execs : runtime registration policy (SPEC §3.3) ---
+# Purely subtractive: these only ever REMOVE tags from the registered set — there
+# is no force-enable verb. Unset ⇒ every discovered runtime is registered. This
+# package sets no operative default; the comments below ARE the operator docs.
+
+# Allowlist: register ONLY these tags (comma-separated); every other tag is off.
+# PLURNK_EXECS_ONLY=sh,jq,search
+
+# Per-tag kill-switch (case-insensitive): set any registered tag to 0 to drop it.
+# Absent ⇒ the runtime stays enabled. e.g.:
+# PLURNK_EXECS_PYTHON=0
+# PLURNK_EXECS_BC=0

package/SPEC.md

@@ -222,7 +222,7 @@ When a loop leaves **zero** EXEC runtimes in the §3.2 *Active* bucket, the capa
 
 **One contributor, both cases.** `Advertise.contribute(registry, isPermitted)` returns the permitted runtimes **and** the notice from the *same* filter — a non-empty result never carries a notice, so the N-runtime sheet and the 0-runtime line cannot drift out of sync.
 
-**Cause-agnostic.** `isPermitted` resolves whether a registered tag survives *this* loop's gates: execs supplies the §3.3 policy cascade as the baseline predicate, and the consumer composes stricter gates into it — the effect-typed **host bar** by which a loop mode (ask-mode) bars host-effecting ops. But *why* the set is empty — policy zeroing every tag, or the host bar catching them all — is never execs' business. Execs owns the §2.3 `effect()` classification and the count; the consumer owns the loop-mode decision and reduces it to the effect-typed bar it composes into the predicate. Nothing about the mode reaches execs. The word is **"permitted,"** not "disabled": one word must not imply one cause.
+**Cause-agnostic.** `isPermitted` resolves whether a registered tag survives *this* loop's gates: execs supplies the §3.3 policy cascade as the baseline predicate, and the consumer composes stricter gates into it — the effect-typed **host bar** by which a loop mode (ask-mode) bars host-effecting ops. But *why* the set is empty — policy zeroing every tag, or the host bar catching them all — is never execs' business. Execs owns the §2.3 `effect()` classification and the count; the consumer owns the loop-mode decision and reduces it to the effect-typed bar it composes into the predicate. Nothing about the mode reaches execs. The line is short and **EXEC-scoped** — it names the op, so the model reads a bounded "no EXEC here", not a general rule — and cause-agnostic. Exact wording is the consumer's ask-mode probe to validate, not asserted here.
 
 Execs owns the notice content and the tally. It does **not** own the mode, the sheet's rendering, or the decision of when a loop bars host effects — only the single line spoken when its own count of surviving runtimes reaches zero.
 

package/dist/advertise.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"advertise.d.ts","sourceRoot":"","sources":["../src/advertise.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAqBzD,MAAM,CAAC,OAAO,OAAO,SAAS;IAI1B,MAAM,CAAC,QAAQ,CAAC,eAAe,kCAAkC;IAEjE,MAAM,CAAC,UAAU,CACb,QAAQ,EAAE,YAAY,EACtB,WAAW,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,GACtC;QAAE,SAAS,EAAE,QAAQ,EAAE,CAAC;QAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAGlD;CACJ"}
+{"version":3,"file":"advertise.d.ts","sourceRoot":"","sources":["../src/advertise.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,QAAQ,EAAE,YAAY,EAAE,MAAM,YAAY,CAAC;AAGzD,MAAM,CAAC,OAAO,OAAO,SAAS;IAE1B,MAAM,CAAC,QAAQ,CAAC,eAAe,kCAAkC;IAEjE,MAAM,CAAC,UAAU,CACb,QAAQ,EAAE,YAAY,EACtB,WAAW,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,GACtC;QAAE,SAAS,EAAE,QAAQ,EAAE,CAAC;QAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAA;KAAE,CAGlD;CACJ"}

package/dist/advertise.js

@@ -1,26 +1,6 @@
-// The EXEC family's capability contribution to the consumer's `# Plurnk System
-// Tools` sheet for ONE loop (SPEC §3.4). Its whole job is the legible no: when
-// a loop leaves ZERO EXEC runtimes Active (§3.2), the sheet must carry a
-// positive statement rather than silent absence — the grammar still teaches
-// `EXEC` as a valid op, so a bare op mention with no availability signal reads
-// as *unknown*, and the model confabulates runtimes that the gate then refuses
-// (execs#24). The negative line closes that window.
-//
-// One contributor, both cases. `permitted` and the `notice` fall out of the
-// SAME filter, so the N-runtime sheet and the 0-runtime line cannot drift: a
-// non-empty result never carries a notice.
-//
-// Cause-agnostic by contract. `isPermitted` resolves whether a registered tag
-// survives THIS loop's gates — execs supplies the §3.3 policy cascade as the
-// baseline, and the consumer composes stricter gates into it (the effect-typed
-// host bar of ask-mode, execs#24). WHY the set is empty is never execs'
-// business: execs owns the §2.3 `effect()` classification and this tally; the
-// consumer owns the loop-mode decision. Execs counts survivors and speaks the
-// count — nothing about the mode reaches this module.
+// The EXEC family's per-loop capability contribution (SPEC §3.4, execs#24).
 export default class Advertise {
-    // The single family-level line spoken when zero EXEC runtimes survive.
-    // "permitted", not "disabled": true whether §3.3 policy zeroed every tag or
-    // an effect-typed host bar caught them all — one word must not imply one cause.
+    // Deliberate wording — validated by the consumer probe, not free to edit (SPEC §3.4).
     static NO_EXECS_NOTICE = "No EXEC operations permitted";
     static contribute(registry, isPermitted) {
         const permitted = [...registry.values()].filter(({ runtime }) => isPermitted(runtime));

package/dist/advertise.js.map

@@ -1 +1 @@
-{"version":3,"file":"advertise.js","sourceRoot":"","sources":["../src/advertise.ts"],"names":[],"mappings":"AAEA,+EAA+E;AAC/E,+EAA+E;AAC/E,yEAAyE;AACzE,4EAA4E;AAC5E,+EAA+E;AAC/E,+EAA+E;AAC/E,oDAAoD;AACpD,EAAE;AACF,4EAA4E;AAC5E,6EAA6E;AAC7E,2CAA2C;AAC3C,EAAE;AACF,8EAA8E;AAC9E,6EAA6E;AAC7E,+EAA+E;AAC/E,wEAAwE;AACxE,8EAA8E;AAC9E,8EAA8E;AAC9E,sDAAsD;AACtD,MAAM,CAAC,OAAO,OAAO,SAAS;IAC1B,uEAAuE;IACvE,4EAA4E;IAC5E,gFAAgF;IAChF,MAAM,CAAU,eAAe,GAAG,8BAA8B,CAAC;IAEjE,MAAM,CAAC,UAAU,CACb,QAAsB,EACtB,WAAqC;QAErC,MAAM,SAAS,GAAG,CAAC,GAAG,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC,WAAW,CAAC,OAAO,CAAC,CAAC,CAAC;QACvF,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,eAAe,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IAC5F,CAAC;CACJ"}
+{"version":3,"file":"advertise.js","sourceRoot":"","sources":["../src/advertise.ts"],"names":[],"mappings":"AAEA,4EAA4E;AAC5E,MAAM,CAAC,OAAO,OAAO,SAAS;IAC1B,sFAAsF;IACtF,MAAM,CAAU,eAAe,GAAG,8BAA8B,CAAC;IAEjE,MAAM,CAAC,UAAU,CACb,QAAsB,EACtB,WAAqC;QAErC,MAAM,SAAS,GAAG,CAAC,GAAG,QAAQ,CAAC,MAAM,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,EAAE,OAAO,EAAE,EAAE,EAAE,CAAC,WAAW,CAAC,OAAO,CAAC,CAAC,CAAC;QACvF,OAAO,EAAE,SAAS,EAAE,MAAM,EAAE,SAAS,CAAC,MAAM,KAAK,CAAC,CAAC,CAAC,CAAC,SAAS,CAAC,eAAe,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;IAC5F,CAAC;CACJ"}

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-execs",
-    "version": "0.4.42",
+    "version": "0.4.44",
     "description": "Framework + contract for the @plurnk/plurnk-execs-* runtime executor family.",
     "keywords": [
         "plurnk",
@@ -35,7 +35,8 @@
     "files": [
         "dist/**/*",
         "README.md",
-        "SPEC.md"
+        "SPEC.md",
+        ".env.defaults"
     ],
     "scripts": {
         "test:lint": "tsc --noEmit",
@@ -46,7 +47,7 @@
         "prepare": "npm run build"
     },
     "dependencies": {
-        "@plurnk/plurnk-schemes": "0.33.19"
+        "@plurnk/plurnk-schemes": "0.33.21"
     },
     "devDependencies": {
         "@types/node": "^26.0.1",