Fog of war reveals the ground around the bot through rock (t17)

Also: board rule to write tasks from chat in our own words, task
descriptions rewritten that way, and a note on lost web-board descriptions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.kandown/kandown_work.md

@@ -10,9 +10,12 @@ The board is the owner's to-do list. `docs/kandown.md` explains how kandown work
     chat, and write nothing in code until the owner decides. Then record the decision.
   - **Backlog, tagged `idea`**: ideas for later. Leave them alone unless asked.
   - Questions get answers.
-- **Keep the owner's words.** Never rewrite or tidy the owner's text in `## Context`, and don't
+- **Keep the owner's words.** Never rewrite or tidy text the owner wrote in a task file, and don't
   rename tasks the owner made. Add what you learn as `## Subtasks` with `report:` lines, or in
   the `report` field.
+- **Writing tasks from chat.** When you write a description, task or subtask from what the owner
+  said in chat, write it fully in your own words as a clear description of what they want. Don't
+  label it as the owner's, add dates, or quote them.
 - **When a task is finished**, move it to **Review** (that is "done, please check") and set the
   `report` field: what changed, and how to check it in the game. Never move a task to Done:
   the owner does that after checking it. If the owner moves it back with feedback, keep the
@@ -24,4 +27,4 @@ The board is the owner's to-do list. `docs/kandown.md` explains how kandown work
 - **Commit task files with the work** they describe. The owner may be editing tasks too: stage
   only the task files you changed.
 - **New tasks the owner asks for**: `kandown create "title" --to Todo` (add `-t discussion` or
-  `-t idea` for Backlog), then put the owner's words under `## Context`.
+  `-t idea` for Backlog), then describe the task under `## Context`.