@plurnk/plurnk-contracts 1.19.1 → 1.19.3

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
@@ -475,7 +481,7 @@ beside owner metadata, not only a matcher carried inside its `pattern` option.
 |---|---|
 | Fence name | Reserved native OP, otherwise a registered executor or attached MCP service |
 | `(path)` | Target/program/tool slot; COPY and MOVE each have two resource operands |
-| `[metadata]` | One JSON array of option objects, owner-interpreted; options, never the op's input |
+| `[metadata]` | One owner-interpreted block; options, never the op's input |
 | `<scope>` | Operation-specific numeric or anchored coordinates |
 | `<!-- … -->` | Optional final, single-line aside |
 | Body | Literal content between framing newlines |
@@ -505,15 +511,23 @@ for the narrowly owned {§misplaced-aside-advisory}.
 
 §scheme-metadata-modifier A target may carry one single-line `[metadata]`
 block after its scope; executor and SEND fences also admit it without a target.
-Read with its brackets, the block is a JSON array of option objects, merged
-left to right with later keys winning; the keys belong to the selected scheme
-or executor, which owns interpretation, validation and authority. The language
-assigns no meaning to the content and stores each block's exact inner text:
-balanced brackets inside the block are retained, and double-quoted strings
-protect their brackets. Brackets inside `(path)` remain ordinary path and
-glob characters. A block that is not valid JSON, or a second block on one
+The block belongs to the selected scheme or executor, which owns its shape,
+interpretation, validation and authority. The language assigns no meaning to
+the content and stores each block's exact inner text: balanced brackets inside
+the block are retained, and double-quoted strings protect their brackets.
+Brackets inside `(path)` remain ordinary path and
+glob characters. A block the owner cannot read, or a second block on one
 operand, is the owner's `400`, never a parser diagnostic. An unfinished block
-or multiline metadata loses its boundary. Two keys never reach an owner:
+or multiline metadata loses its boundary.
+
+**House policy, not a language rule:** every first-party scheme and executor
+reads its block through the shared `MetadataOptions` reader, which takes the
+block with its brackets as a JSON array of option objects, merged left to
+right with later keys winning. A third-party owner may read its block any way
+it likes — the language guarantees only the exact inner text. Documentation
+for a first-party owner therefore shows the bracketed array form.
+
+Two keys never reach an owner:
 `pattern`, the language's own ({§matcher-option}), and `env`, reserved for the
 service's environment option on the operations that open a process or a
 Worker; the shared reader withholds both from the owner's options.
@@ -550,7 +564,7 @@ whose block left no metadata back bare when the bare form reads back identically
 | Executor name | Letters, digits, `_`, `.`, `+`, or `-`; reserved OPs win |
 | Fence | Three or more backticks, matched by exact count |
 | `(path)` | Local path, URI, program or tool name; §5 |
-| `[metadata]` | One JSON array of owner-defined option objects |
+| `[metadata]` | One owner-interpreted block of owner-defined options |
 | `<scope>` | Numeric or anchored coordinates; §7 |
 | Body | Literal text; never recursively interpreted as operations |
 

package/package.json

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

package/plurnk.md

@@ -9,9 +9,12 @@ 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 valid Operation Syntax OPs, responding with only fenced markdown if concluding.
 
-* `[metadata]`: optional one-line JSON array of special configuration.
+> [!WARNING]
+> YOU MUST offset any example OP you do not intend to execute with a hard or soft tab.
+
+* `[metadata]`: optional one-line special configuration.
 * `<!-- aside -->`: optional terse note.
 * All parameters and the aside must appear on the same line as OP.
 * OP may be either a Plurnk Operation or one of the tools.
@@ -29,10 +32,19 @@ Pattern Lookup Universal Resource NetworK: find anything by pattern, read it by
 * WORK: Deploy a child worker (fresh log).
 * FORK: Deploy a forked worker (forked log).
 * BARE: Deploy an isolated inference query (no log or tools).
-* WAIT: Yield until the next wake: a child's result, a message, a stream's end.
+* WAIT: Yield until the next wake: a child worker's result, a message, a stream's end.
+
+* markdown: Final response alone, concluding the entire loop. All other OPs, child workers, or streams are finished.
 
 ## Workflow Management
 
+> [!IMPORTANT]
+> The markdown response must be the only OP emitted in the final turn.
+
+    ````markdown
+    The answer is 42.
+    ````
+
 > [!INFO]
 > To cancel all unfinished work in your worker and its descendants, KILL your own worker address.
 
@@ -48,7 +60,6 @@ Pattern Lookup Universal Resource NetworK: find anything by pattern, read it by
 * Log item paths nest: `log:///1/2/3/READ` is loop/turn/item/operation.
 * FIND results hold one inner array per path: its channels, default first; append `#channel` to select another.
 * Percent-encode `(` as `%28` and `)` as `%29`.
-* Creating a file creates missing parent directories.
 
 ## File Editing
 
@@ -68,6 +79,9 @@ Pattern Lookup Universal Resource NetworK: find anything by pattern, read it by
 > [!TIP]
 > The EDIT body is literal text. YOU SHOULD address lines by `<@hash>` or `<@start,@end>`; stale targets are rejected.
 
+> [!TIP]
+> Creating a file creates missing parent directories.
+
 ## Delegation
 
     ````WORK (worker://reviewer) [{"env": {"NODE_ENV": "test"}}] <!-- the child's result lands in your log -->
@@ -115,9 +129,8 @@ All member files and entries are mapped, indexed, and universally pattern search
 | prefix | dialect                     | example                         |
 |--------|-----------------------------|---------------------------------|
 | `/`    | regex (ECMAScript)          | `/\btimeout\b/i`                |
-| `^`    | regex anchored to a line    | `^ERROR:.*`                     |
 | `//`   | xpath (1.0)                 | `//dependencies/*`              |
 | `$`    | jsonpath (RFC 9535)         | `$.items[?(@.price>500)]`       |
 | `~`    | full-text (SQLite FTS5)     | `~retry`                        |
-| `&`    | graph: (treesitter symbols) | `&sym`, `&<sym`, `&>sym`        |
+| `&`    | graph (treesitter symbols)  | `&sym`, `&<sym`, `&>sym`        |
 | none   | literal or extglob          | `?(export )?(async )function *` |