feat(tasks): a task can say a session is working it — the claim (milestone 381 step 2)

status is durable and nothing clears it, so in_progress cannot also mean
"someone is on this now". The claim is that second meaning, stored as who
and when so it dies on read rather than needing to be cleared.

- notes.claimed_by / claimed_at / claim_touched_at / claim_session (0110).
- The server stamps it on the write that is the work: reaching in_progress
  (update or create, via apply_status_transition) and a work log on an open
  task. done/cancelled/todo release it. Live while touched within
  CLAIM_LEASE (2h); dead on read past it, with no sweep.
- The plugin's PostToolUse hook on update_task/add_task_log binds the
  harness's session_id (GET /api/plugin/claim-session). It binds only to a
  live claim the caller holds; it cannot create one.
- to_dict carries `claim`. Plugin version minted.

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

scripts/check_plugin.py

@@ -386,6 +386,15 @@ SMOKE_EVENTS: dict[str, str] = {
          "tool_input": {"rule_id": 1, "outcome": "applied"},
          "tool_response": {}}
     ),
+    # The claim-session binder (milestone 381). Silent like the ledgers above —
+    # a PostToolUse hook that spoke would add a line after every task write —
+    # and with no instance configured it must exit before reaching for one.
+    "scribe_claim_session.sh": json.dumps(
+        {"session_id": "smoke", "cwd": ".",
+         "tool_name": "mcp__scribe__add_task_log",
+         "tool_input": {"task_id": 1, "content": "smoke"},
+         "tool_response": {}}
+    ),
     # The shared library is sourced, never run; executed bare it defines
     # functions and exits — silent by construction.
     "scribe_defs.sh": "",