@plurnk/plurnk-contracts 1.28.0 → 1.29.0

package/SPEC.md

@@ -680,7 +680,11 @@ by one ASCII space. Target and scope form one resource selection; COPY/MOVE
 repeat the complete selection/metadata group per operand. ANTLR accepts
 adjacent slots and scope/metadata permutations within a selection without
 changing ownership or making them distinct canonical forms. Each selection
-has at most one scope; its metadata blocks retain their authored order.
+has at most one scope; its metadata blocks retain their authored order. A second scope
+is refused, and the recovery reads the pair: a line number followed by its anchor
+(`<91> <@abcde>`, a copied row prefix) recovers to the anchor alone, two other single
+positions to one scope with both ends (`<@abcde> <-1>` to `<@abcde,-1>`), and anything
+else to one operation per selection.
 
 §lifecycle-slots NOTE accepts no target, scope, or metadata. WAIT retains its
 optional target and duration under {§send-wait-scope}. Their literal bodies begin
@@ -958,7 +962,8 @@ the path and the rest is the channel (a spelling that opens with `#` names no pa
 whole), exactly as `worker:///a.html#readable` decomposes, so
 the `#channel` a READ receipt advertises (`channels: {"#readable": N}`) is addressable in the
 same bare spelling the receipt used: a model that appends the channel to the path it was just
-shown addresses the same entry. `raw` is therefore always the path alone; a
+shown addresses the same entry, and so does one that writes it after the parenthesis,
+`(page.html) #readable`, which {§naked-pattern} reads as the channel. `raw` is therefore always the path alone; a
 bare path never contains a literal `#`, and `PlurnkParser.stringify` renders the channel back.
 Without a `#` the field is absent, so an older `LocalPath` literal stays valid.
 
@@ -1825,7 +1830,11 @@ diagnostics are:
   scope or option block, the rest of a FIND, READ or KILL heading line is the
   matcher, in whichever dialect its first characters claim
   ({§matcher-prefix-claims}): `/re/i`, `^anchored`, `//xpath`, `$.json`, `~words`,
-  `&symbol`, or a sigil-less glob or literal such as `TODO` or `*.ts`. Those
+  `&symbol`, or a sigil-less glob or literal such as `TODO` or `*.ts`. One
+  spelling is not a matcher: `#name` alone, a `#` followed by one channel token
+  and nothing else, after a target that names no channel, is that target's
+  channel exactly as if written on the path ({§local-path-fragment}); a target
+  that already names a channel keeps such a token as its pattern. Those
   matchers remain independent of owner options: a block without `pattern` never
   erases the heading matcher, and invalid blocks still reach the owning validator.
   These operations take no body, so heading-line text can mean nothing else. On EDIT only
@@ -1875,6 +1884,7 @@ diagnostics are:
   | `READ → sh:///x#stdout <1,50>` | the target, `READ (sh:///x#stdout) <1,50>`; COPY/MOVE take one arrow per operand | `` `→ sh:///x#stdout` is how the log shows an address; it was read as the target. Write the target in parentheses: `READ (sh:///x#stdout) <1,50>`. `` |
   | `READ (a.py) <1,50> · 900`, `· 320 tokens`, a bare `·` | nothing: the token charge is dropped, on the heading or after a matcher | `` `· 900` is the token charge the log shows on a heading; it is not part of an operation and was ignored. `` |
   | `FIND (x) /re/ · locate the sign handling` | the aside | `` `· locate the sign handling` was read as the aside; a note on an operation is written `<!-- locate the sign handling -->`. `` |
+  | `FIND (x) <84,180> · no <!-- read the helpers -->` | the comment is the aside; the dot note before it is stray text, dropped | `` `· no` was ignored; the aside is `<!-- read the helpers -->`. `` |
 
   The arrow's path runs to the next space, `<` or `[`; a `·` never begins a heading matcher. In
   distinct recorded benchmark emissions the arrow form opened 40 headings and the charge ended 52,
@@ -1911,8 +1921,11 @@ diagnostics are:
   scope opener, report the offending scope (at most 64 code points, ending at
   `>` or the heading's line end) and its operation's constraint: FIND result
   positions, text coordinates, or no scope. Do not append advice for
-  other operations or infer why the producer supplied the value. Spacing and
-  boundary-loss diagnostics retain their own contracts.
+  other operations or infer why the producer supplied the value. A text-coordinate
+  scope that pairs an anchor with the same five characters unmarked (`<@abcde,fghij>`)
+  states the anchor rule instead, with the scope marked: `` every line anchor carries
+  its `@`: `<@abcde,@fghij>` ``. Spacing and boundary-loss diagnostics retain their own
+  contracts.
 - §misplaced-aside-advisory **Aside in the body.** A READ or FIND whose
   body is solely an HTML comment (`<!-- … -->`) can never carry a matcher: it is
   the aside the model put on the line below the heading. The builder takes

package/package.json

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

package/plurnk.md

@@ -28,12 +28,16 @@ body?
 
 ## Workflow Management
 
+```SEND <!-- parameterless send messages user -->
+This is an example of a brief progress update for the user.
+```
+
 ```WAIT <60> <!-- wait up to 60 seconds -->
-Example explanation of delay.
+This is an example of a brief progress update for the user.
 ```
 
 > [!IMPORTANT]
-> YOU SHOULD NOT respond before the KILL turn.
+> YOU SHOULD ONLY answer the user with SEND, WAIT, or the KILL turn.
 > YOU SHOULD NOT perform a KILL turn before you have fully resolved all child workers and streams.
 > YOU MAY perform the standalone KILL turn by emitting a single parameterless KILL containing the final deliverable response.
 
@@ -62,7 +66,7 @@ This is an example of the complete, final deliverable response.
 
 * `(path)` may be a glob/extglob, permitting bulk operations.
 * Log item paths nest: `log:///1/2/3/READ` is loop/turn/item/OP.
-* FIND results hold one inner array per path: its channels, default first; append `#channel` to select another.
+* FIND results hold one inner array per path: its channels, default first; append `#channel` to the path to select another: `(sh:///ab3d5678#stderr)`.
 * Percent-encode in paths `(` as `%28` and `)` as `%29`.
 
 ## `<scope|range>`