task: Weekly review proposes task new/task close; tracker gains a closing write path

Files changed:
- CHANGES.md
- INSTALL.md
- README.md
- VERSION
- docs/knowledge-and-commitment.md
- instructions/gtd-weekly-review/SKILL.md
- instructions/ingest-large-tree.md
- instructions/wiki-ingest/SKILL.md
- tools/CONTRACT.md
- tools/chemenu/commands/review_cmd.py
- tools/chemenu/commands/task_cmd.py
- tools/chemenu/review.py
- tools/chemenu/tasks/protocol.py
- tools/chemenu/tasks/superproductivity.py
- tools/chemenu/tests/test_review.py
- tools/chemenu/tests/test_superproductivity.py
- tools/chemenu/tests/test_task_cmd.py

README.md

@@ -244,7 +244,11 @@ you and turns each one into a decision; `tools/wikitool new project` is what
 gives a new initiative its page and its tracker project under one name, and
 `tools/wikitool task new` files a single open item into the tracker - the
 commitment half of a source that carries both something to know and something
-to do, with no page of its own.
+to do, with no page of its own. `tools/wikitool task list` reads a project's
+open items back with their tracker id, and `tools/wikitool task close --id`
+marks one done - never deletes it - closing the loop the same source-driven
+way `task new` opened it, or the way the weekly review proposes it for a
+`waiting_overdue`/`someday_stale` finding once you confirm.
 
 Why the split runs this way, rather than syncing the two:
 [docs/knowledge-and-commitment.md](docs/knowledge-and-commitment.md).