@plurnk/plurnk-grammar 0.74.5 → 0.74.6

package/package.json

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

package/plurnk.md

@@ -89,18 +89,12 @@ Body content is character-perfect, exactly matching whitespace.
 
 YOU MUST begin the turn with <<PLAN:plan goes here: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 with OPEN, FOLD, and KILL 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 terminate the turn by SENDing a message to the user with the proper status code.
-
-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
+YOU MUST terminate the turn by SENDing a message to the user with the proper status code (102, 200, 202, or 499).
 
 ## Examples