Harness spec 3.6.0: phone_action, done on the person's phone and confirmed there

harness/phone.md, tools/phone_action.json, loop.json phone, conformance/phone.json.
The LLeMbas server's tool alone (scope llembas, sessions chat), offered once a
message came from the LLeMbas app with the capability phone_actions (new
requirement phone). Actions: alarm, timer, calendar_event, sms_draft,
email_draft, dial, navigate, add_stop, search_nearby, stop_navigation,
open_app, open_url, media, torch, settings_panel, automation_intent. Each
reads its own fields; required fields and value checks give the call's
refusal in the spec's words. The person confirms on the phone every time;
the result is done, declined or failed with what the phone said, or no
answer in time. add_stop carries the route's destination: no map app adds
to a running route, so the phone plans again via the stop.

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

CHANGELOG.md

@@ -4,6 +4,17 @@ All notable changes to LLeMbas CLI. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
 [Semantic Versioning](https://semver.org/).
 
+## [Unreleased]
+
+### Added
+
+- **Harness spec 3.6.0: phone actions.** The spec now describes `phone_action`, the LLeMbas
+  server's tool for doing something on the person's phone when they write from the LLeMbas app on
+  it — alarms and timers, calendar events, SMS and email drafts, the dialer, routes (start one,
+  add a stop, search nearby, stop), opening an app or an address, media, the torch, settings
+  panels and automations — confirmed on the phone every time (`harness/phone.md`). The server's
+  alone: the CLI does not offer it, and its conformance area is the server's.
+
 ## [2.0.0-beta.7] — 2026-11-10
 
 Harness spec 3.5.0: scheduled work on a linked computer.