docs: document batch task operations

Amolith and Crush created 3 days ago

Updated README.md and AGENTS.md to document the new batch task
capabilities:
- Task addition: np t a -t 'one' -d 'desc' -t 'two' -d 'desc'
- Status updates: np t u -i id1 -s status1 -i id2 -s status2

Clarified both single and batch patterns in workflow descriptions.

Co-authored-by: Crush <crush@charm.land>

Change summary

AGENTS.md | 16 +++++++++-------
README.md |  9 +++++----
2 files changed, 14 insertions(+), 11 deletions(-)

Detailed changes

AGENTS.md 🔗

@@ -43,7 +43,7 @@ go test -v -run TestName ./path/to/package
 - `cmd/`: Cobra commands
   - Root and top-level: `a` (archive), `m` (monitor/TUI stub), `p` (plan printout stub), `r` (resume), `s` (start)
   - `cmd/g/`: goal command group; `g` (show stub), `g s` (set goal stub with -t/-d)
-  - `cmd/t/`: task command group; `t` (list stub with status filter flag), `t a` (add stub), `t u` (update stub)
+  - `cmd/t/`: task command group; `t` (list stub with status filter flag), `t a` (add, supports batch via repeatable -t/-d), `t u` (update, supports batch status updates via repeatable -i/-s)
 - `internal/`:
   - `db/`: Badger wrapper: options, tx helpers, key builders, path hashing
   - `goal/`: goal document + store
@@ -59,13 +59,15 @@ go test -v -run TestName ./path/to/package
 Commands exist and are registered, but most are stubs that print placeholder output:
 
 ```bash
-np s   # start session (stub)
-np a   # archive session (stub)
-np p   # print plan (stub)
-np r   # resume session (stub)
+np s   # start session
+np a   # archive session
+np p   # print plan
+np r   # resume session
 np m   # monitor TUI (stub)
-np g   # goal (stub); np g s -t -d flags defined
-np t   # tasks (stub); -s status flag defined; t a/u files exist as stubs
+np g   # goal; np g s -t -d (set), np g u -t -d -r (update)
+np t   # tasks; -s status flag for filtering
+np t a # add tasks; supports batch: -t "one" -d "desc" -t "two" -d "desc"
+np t u # update tasks; supports batch status: -i id1 -s status1 -i id2 -s status2
 ```
 
 Fang is used for execution/versioning; Cobra provides the command tree.

README.md 🔗

@@ -121,10 +121,11 @@ from the ticket and any extra operator-provided context. If there's a ticket ID,
 that goes in the goal description. The output of `np g s` says to look at the
 provided references, thoroughly consider how to go about resolving the goal, and
 gather additional context from other files if necessary. Once it has a good idea
-how to resolve the goal, it should add some tasks with `np t a -t title -d
-description -t title2 -d description2`. The descriptions are good places to
-reference files and symbols. The output of `np t a` tells it to update tasks as
-it works on them with something like `np t u -i task-id -s status`.
+how to resolve the goal, it should add tasks with `np t a -t title -d description`
+(single) or `np t a -t title1 -d description1 -t title2 -d description2` (batch).
+The descriptions are good places to reference files and symbols. The output of
+`np t a` tells it to update tasks as it works on them with `np t u -i task-id -s
+status` (single) or `np t u -i id1 -s status1 -i id2 -s status2` (batch).
 
 Commands that modify the model's goal or list output the full changed plan
 (formatted [like so](#the-format-the-model-sees)) so it doesn't have to run