Fixed tool calling history

docs/10-android-app.md

@@ -257,8 +257,17 @@ payloads** so the schema does not drift with the Kotlin model fields
 
 - `message(lane PK, id PK, ts, payload)` — one row per persisted
   `MessageItem`; `lane` is the lane key (`chatId` or `chatId::threadId`),
-  `ts` for ordering. Tool cards and local system notices are **not**
-  persisted (ephemeral; they are not part of `history` either).
+  `ts` for ordering. Local system notices are **not** persisted (ephemeral).
+- `tool(lane PK, id PK, seq, payload)` — one row per persisted `ToolItem`
+  (tool-activity card). Tool cards are **not** part of the gateway's
+  `history` (which carries final messages only), so the app persists them
+  itself to restore them across a restart. The payload carries `anchor_id`
+  (the id of the message the card follows — the last non-streaming message
+  when the tool started); on load the card is inserted after its anchor, so
+  the order user message → tool card → answer survives a restart. A card
+  whose anchor is gone (deleted message) falls to the end of the lane; an
+  open card (process died before `tool.end`) is restored closed as
+  interrupted.
 - `channel(chat_id PK, payload)` — the whole channel directory (channels +
   threads), so the drawer works offline.
 - `meta(key PK, value)` — small UI state (currently: `last_lane`, the