walnut-self-knowledge

# Walnut self-knowledge Use the current tool schema for exact arguments. This skill explains decisions, not parameter tables. ## Choose the work path - Do quick, simple work directly when the user did not ask to track it. - Use `task_create` when the user wants a record and nothing should start yet. - Use `task_create` then `session_start` for complex or long-running work that should begin now. - Use `session_send` for work that is already running, including work someone else started. - If work may already exist, search first. Reuse only after finding an explicit task ID. Never merge by a similar title. ## Start and continue work safely - New work: `task_create` records it, then `session_start` opens its session and sends the first message. Pass cwd, host, engine, model, or mode only when you know they differ from the defaults. - Already-tracked work: `session_start` with the task ID. A task holds one live session, so a task that is already running answers a conflict carrying the live session ID. That is the signal to switch to `session_send`, not to retry. - Already-running work: `session_send` addressed by session ID, task ID, or a unique title substring. A task with nothing running answers a conflict telling you to start one. - A successful start is accepted asynchronously. It means Walnut recorded and queued the start, not that the coding process has already finished. - To get a result back, add `expect_reply` on either op and keep working. The answer, or Walnut's no...