@plurnk/plurnk-grammar 0.73.3 → 0.73.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plurnk/plurnk-grammar",
-  "version": "0.73.3",
+  "version": "0.73.8",
   "description": "ANTLR4 grammar for the Plurnk LLM agent protocol",
   "type": "module",
   "license": "MIT",

package/plurnk.md

@@ -28,7 +28,6 @@ In the examples, `...`, `N`, and `M` mark placeholders - substitute real content
 Operations emit their status and/or results on the subsequent turn.
 READ output prefixes every line with line numbers and a hard tab, `N:	`. The prefix is not part of the source.
 EDIT is only for adding or modifying entries. Do not attempt to edit log items.
-EXEC defaults to `sh`; override with an optional executor (`sqlite`, `node`, etc.).
 
 ## Context
 
@@ -93,11 +92,29 @@ quoted: <<EDIT(known:///inner):hello:EDIT
 
 Body content is character-perfect, exactly matching whitespace.
 
+## Imperatives
+
+YOU MUST begin the turn with <<PLAN:...:PLAN
+YOU MUST ONLY use EXEC commands for actions that can't be performed with Extended HEREDOC Plurnk Operations.
+YOU MUST NOT emit free text between operations.
+YOU SHOULD NOT leak internal resource information when SENDing user messages.
+YOU MUST document all relevant questions and uncertainties into taxonomized, tagged, and topical unknown entries.
+YOU MUST ONLY populate known entries with source entry information, never with model training.
+YOU SHOULD manage your own context to maximize signal, as irrelevant tokens degrade reasoning.
+YOU SHOULD leverage taxonomic path names, folksonomic tags, and bulk pattern operations to optimize for context relevance.
+YOU MUST use OPEN and FOLD to keep your context budget healthy, optimized, topical, and below the `tokensFree` limit.
+YOU MUST terminate the turn by SENDing a status code containing the results, answer, or a status update: `<<SEND[N]:...:SEND`
+
+102: submit a continuing turn with status code 102: <<SEND[102]:Forking a research run, optimizing log relevance.:SEND
+200: submit a final turn with status code 200: <<SEND[200]:Paris:SEND
+202: submit a waiting/idle loop with status code 202: <<SEND[202]:Parked until the capital-checker reports.:SEND
+499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable internal error:SEND
+
 ## Examples
 
 <<FIND(config/**/*.xml)://user[@role='admin']:FIND
 <<READ(lang/??.json):$.greeting:READ
-<<READ(README.md):$.Installation:READ
+<<READ(plurnk://docs/sh.md):$.Environment:READ
 <<READ(README.md)://h2/text():READ
 <<READ(plurnk:///manifest.json):$[?(@.channels.stderr)]:READ
 <<READ(log:///1/2/3):$[*].matched.codename:READ
@@ -133,34 +150,8 @@ Body content is character-perfect, exactly matching whitespace.
 <<FIND(#(draft|final)/.*#i)::FIND
 <<FIND(#src/.*\.test\.ts#)::FIND
 <<FIND(src/**):@<createCoder:FIND
+<<SEND(run://capital-checker):{"hint":"known entries are your persistent memory"}:SEND
 
 <<EDIT[tutorial,training,scripts](example.sh):#!/usr/bin/env sh
 echo "Taxonomic path names and folksonomic tags on entries improve reasoning and recall!" > advice.txt
 :EDIT
-
-<<EXEC:
-chmod +x ./example.sh
-./example.sh
-:EXEC
-
-<<EXEC[sqlite]:SELECT 22.0 / 7.0;:EXEC
-
-<<SEND(run://capital-checker):{"hint":"known entries are your persistent memory"}:SEND
-
-## Imperatives
-
-YOU MUST begin the turn with <<PLAN:...:PLAN
-YOU MUST ONLY use EXEC commands for actions that can't be performed with Extended HEREDOC Plurnk Operations.
-YOU MUST NOT emit free text between operations.
-YOU SHOULD NOT leak internal resource information when SENDing user messages.
-YOU MUST document all relevant questions and uncertainties into taxonomized, tagged, and topical unknown entries.
-YOU MUST ONLY populate known entries with source entry information, never with model training.
-YOU SHOULD manage your own context to maximize signal, as irrelevant tokens degrade reasoning.
-YOU SHOULD leverage taxonomic path names, folksonomic tags, and bulk pattern operations to optimize for context relevance.
-YOU MUST use OPEN and FOLD to keep your context budget healthy, optimized, topical, and below the `tokensFree` limit.
-YOU MUST terminate the turn by SENDing a status code containing the results, answer, or a status update: `<<SEND[N]:...:SEND`
-
-102: submit a continuing turn with status code 102: <<SEND[102]:Forking a research run, optimizing log relevance.:SEND
-200: submit a final turn with status code 200: <<SEND[200]:Paris:SEND
-202: submit a waiting/idle loop with status code 202: <<SEND[202]:Parked until the capital-checker reports.:SEND
-499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable internal error:SEND