docs: mention status updates

Amolith created

Change summary

README.md | 25 +++++++++++++++++++++----
1 file changed, 21 insertions(+), 4 deletions(-)

Detailed changes

README.md 🔗

@@ -53,6 +53,27 @@ provided references and thoroughly consider how to go about resolving the goal.
 After gathering that context, it adds tasks with `np t a -t title -d description
 -t title2 -d description2` and gets started on them.
 
+As it works through the tasks, it's expected to update statuses by ID with
+something like `np t u -i id -s status`. Commands that modify the model's plan
+output the revision so it can immediately see the result of its invocation
+without running another command (obviating patterns like running `git status`
+after every `git commit`). Format the list something like this, using individual
+unicode symbols to represent task statuses using one token per status instead of
+more verbose checkboxes `- [x]` or words `completed` that might use more tokens.
+The failed icon (`☒`) and cancelled icon (`⊗`) are only shown in the legend if
+there are actually failed or cancelled tasks in the list.
+
+```
+Create a comprehensive MCP server for task planning and management
+
+Legend: ☐ pending  ⟳ in progress  ☑ completed
+☑ Set up project structure [a1b2c3d4]
+  Create Go module, directories, and basic files
+⟳ Implement core planning logic [e5f6g7h8]
+  Create Goal and Task data structures with deterministic IDs
+☐ Build MCP server integration [i9j0k1l2]
+```
+
 I'm unsure how to handle session archival (mentioned in [random
 thoughts](#random-thoughts)). We could tell the model how to archive sessions in
 the rules, but I don't know that the model even needs to know about sessions;
@@ -85,10 +106,6 @@ could be translated as "the way of work", "the doctrine of design", etc.
   )"
   ```
 
-- I like the way
-  [planning-mcp-server](https://git.secluded.site/planning-mcp-server#tracking-progress)
-  renders the task list in unicode characters. `☑` is one token while `- [x]` is
-  probably like five.
 - Start a new session with `np s`. It adds details to the global sqlite database
   and produces output to guide the LLM through its next steps. Instead of
   telling the model up-front about everything it can do with _nasin pali_ though