@plurnk/plurnk-grammar 0.76.9 → 0.76.10

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/plurnk.md +2 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plurnk/plurnk-grammar",
3
- "version": "0.76.9",
3
+ "version": "0.76.10",
4
4
  "description": "ANTLR4 grammar for the Plurnk LLM agent protocol",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/plurnk.md CHANGED
@@ -37,7 +37,7 @@ A `?` marks an optional field, as in the Syntax line; unmarked fields are requir
37
37
  | KILL | [signal]? | (path) | - | :: | KILL |
38
38
  | SEND | [submit code]? | (recipient)? | <timeout, poll>? | :message: | SEND |
39
39
 
40
- <<PLAN:concise plan goes here:PLAN is required at the beginning of a turn.
40
+ <<PLAN:plan goes here:PLAN is required at the beginning of a turn.
41
41
  <<FIND(path)::FIND returns a JSON array of matches: each object carries its path and per-channel mimetype, tokens, and lines. READ a hit's path to view it.
42
42
  <<READ(path)::READ returns lines of matching content. Every line is prefixed with the line number and a hard tab, `N: `.
43
43
  <<EDIT(path):literal text:EDIT is only for creating or modifying files and entries. Do not attempt to edit log items.
@@ -150,7 +150,7 @@ YOU MUST avoid and recover from Budget Overflow errors by FOLDing or KILLing big
150
150
  YOU MUST NOT share internal knowledgebase paths. Users can't access them.
151
151
  YOU MUST NOT emit free text between operations. Users can only see submission SEND messages with the proper submit code.
152
152
 
153
- YOU MUST start the turn with a concise PLAN.
153
+ YOU MUST start the turn with a PLAN.
154
154
  YOU MUST submit the OPs by SENDing either a brief response or a Github-flavored markdown response to the user with the proper submit code.
155
155
  * 102: submit a continuing turn with submit code 102: <<SEND[102]:Performing retrieval operations.:SEND
156
156
  * 202: submit a waiting turn with submit code 202: <<SEND[202]:Awaiting worker results.:SEND