@plurnk/plurnk-contracts 1.19.1 → 1.19.2

package/SPEC.md

@@ -343,9 +343,11 @@ own lines' indentation. An OPENER is different: an operation's backticks follow
 directly (operator, 2026-09-18), so an indented fence opens a quotation, never an operation —
 CommonMark reads an indented block as code, and `plurnk.md` shows its own examples that way. This
 reverses the 2026-09-12 tolerance (then measured at five to ten percent of emissions on
-GLM-5.3-flash; 2.8% of that lane's emissions today). The cost is paid loudly: an indented fence
-naming a known operation draws `must start its line to run` and is an operation attempt, never an
-answer ({§prose-conclusion}), so the loop continues instead of delivering a program as prose.
+GLM-5.3-flash; 2.8% of that lane's emissions today). An offset fence is prose and draws nothing:
+`plurnk.md` instructs the model to offset any example it does not intend to execute, so the form
+is correct by construction and there is no mistake to report (operator, 2026-09-21). The parser
+presumes nothing about why a fence is offset, and {§prose-conclusion} judges the reply on its own
+terms.
 
 §inline-chain A closer on a heading line, or on a body's closing line, may be
 followed on that same line by the next opener; the closer still closes, and the
@@ -447,9 +449,13 @@ diagnostic, notice or teaching mentions the reading (#760).
 as the model's answer, or an operation attempt. `PlurnkParser.operationAttempt(input,
 executors)` names the attempt: a line opening a four-backtick fence, a heading outside
 any fence ({§bare-heading-advisory}; a known executor's name is a heading only when a
-slot follows it), native tool-call markup that {§native-tool-calls} did not read, or
-echoed packet rows (`### log://…`). Anything else, three-backtick code blocks included,
-is prose (#761).
+slot follows it), a three-backtick fence naming an operation — a miscounted heading is a
+typo, not an answer, so the loop continues and the next packet carries `needs four
+backticks to run` (#801) — native tool-call markup that {§native-tool-calls} did not
+read, or echoed packet rows (`### log://…`). The three-backtick rule reads the raw text,
+since such a fence quotes itself, and it takes the executor rule with it: ```` ```sh ````
+is an ordinary code block, ```` ```sh (x) ```` is a miscounted heading. Anything else,
+code blocks under a bare language tag included, is prose (#761).
 
 §bare-heading-advisory An operation name that opens a line outside any block in the
 shape of a heading (`READ (…)`, `NOTE`, …) is prose and runs nothing. The parser

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@plurnk/plurnk-contracts",
-    "version": "1.19.1",
+    "version": "1.19.2",
     "description": "Canonical PLURNK language contract, schemas, generated types, and runtime-neutral wire contracts",
     "keywords": [
         "plurnk",

package/plurnk.md

@@ -9,7 +9,10 @@ Pattern Lookup Universal Resource NetworK: find anything by pattern, read it by
     ````
 
 > [!IMPORTANT]
-> YOU MUST ONLY respond with either valid Operation Syntax OPs or prose (concludes loop, may contain GFM). Not both.
+> YOU MUST ONLY respond with either valid Operation Syntax OPs or prose. Any prose in the body concludes the loop. Not both.
+
+> [!WARNING]
+> YOU MUST offset any example OP you do not intend to execute with a hard or soft tab.
 
 * `[metadata]`: optional one-line JSON array of special configuration.
 * `<!-- aside -->`: optional terse note.