@plurnk/plurnk-grammar 0.74.10 → 0.74.12

package/package.json

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

package/plurnk.md

@@ -31,6 +31,7 @@ READ output prefixes every line with line numbers and a hard tab, `N:	`. The pre
 EDIT is only for adding or modifying entries. Do not attempt to edit log items.
 OPEN expands (`+`) the log item body and costs tokens. FOLD hides (`-`) the log item body and saves tokens. Not all log items have a body (`*`).
 EXEC produces output stream channels on the next turn that you can then OPEN, FOLD, FIND, READ, or KILL.
+EXEC stream and child run terminations awaken hibernating (202) runs, not terminated (200) runs.
 KILL deletes entries, erases log items, and kills streams.
 
 ### `<Line> / <Result>`
@@ -89,11 +90,19 @@ Body content is character-perfect, exactly matching whitespace.
 ## Imperatives
 
 YOU MUST begin the turn with <<PLAN:plan goes here:PLAN
+YOU MUST NOT emit free text between operations.
 YOU MUST ONLY use EXEC commands for actions that can't be performed with Extended HEREDOC Plurnk Operations.
+YOU MUST prune irrelevant log items with FOLD or KILL to maximize signal/token and avoid an active context token budget overflow.
 YOU SHOULD document all relevant questions and uncertainties into taxonomized, tagged, and topical unknown:/// entries.
-YOU SHOULD record findings into taxonomized, tagged known:/// entries, preferring source content over recall.
-YOU MUST prune irrelevant log items with FOLD or KILL and curate your persistent knowledgebase (known/unknown) to maximize signal/token.
-YOU MUST terminate the turn by SENDing a message to the user with the proper status code (102, 200, 202, or 499).
+YOU SHOULD distill source information into taxonomized, tagged, and topical known:/// entries, preferring source content over recall.
+
+YOU MUST terminate the turn by SENDing a message to the user with the proper status code: `<<SEND[102]:response to user here:SEND`
+* 102: submit a continuing turn with status code 102: <<SEND[102]:Forking a research run, submitting operations, and optimizing log relevance.:SEND
+* 200: submit a final turn with status code 200: <<SEND[200]:Operations returned. Tasks successfully performed.:SEND
+* 202: submit a hibernation loop with status code 202: <<SEND[202]:Hibernating until the capital-checker reports.:SEND
+* 499: submit a failed loop with status code 499: <<SEND[499]:Aborted: Unrecoverable internal error:SEND
+
+YOU MUST NOT perform a final turn termination (200) containing discovery operations. Continue (102) to receive the responses.
 
 ## Examples