5 Commits

Include renames

Author	SHA1	Message	Date
showtan001	60ee157e97	feat: preserve planner context across task steps	2026-08-30 22:59:19 +08:00
q792602257	d69be48f96	feat(planner): persist reusable action semantics	2026-07-15 18:14:28 +08:00
q792602257	778af2da53	fix(cloud): align planner configuration and records	2026-07-15 09:43:14 +08:00
q792602257	40efa53411	feat(cloud): attribute planner token usage	2026-07-13 23:10:21 +08:00
q792602257	a68f609453	Implement cloud-planner-proxy: AI planner routes through Cloud API ... Implements all 19 tasks of the cloud-planner-proxy OpenSpec change: - Cloud API: cloud.planner_config (CloudPlannerConfig, load/build helpers) reusing runtime.tool_calling_client provider clients (no new dependency needed -- device-cloud-platform already depends on device-agent-runtime). - Cloud API: new host-scoped POST /internal/v1/hosts/{host_id}/planner/decide internal endpoint, reusing existing bearer auth; logs only metadata (host id, tool name, latency, error class), never prompt/screenshot content. - Host Agent: new AI_PLANNER_TRANSPORT config (direct default | cloud) and host_agent/cloud_planner_client.py::CloudProxyToolCallingClient, a synchronous ToolCallingClient implementation (structural, not importing runtime) that calls the new endpoint via its own httpx.Client -- avoids bridging the async HostAgentClient across the worker-thread boundary that AIPlanner.plan() runs in (asyncio.to_thread in lease.py). - Host Agent wiring: create_execution_factories()/_host_agent_planner() select the cloud-proxy client only when AI_PLANNER_TRANSPORT=cloud; direct/unset transport is unchanged (still the default). - Tests: 22 new tests across Cloud API config, the new endpoint, the new client, and transport-selection wiring; full non-integration suite (492 tests) passes with no regressions. - Docs: docs/CLOUD_DEPLOYMENT.md documents the cloud transport, its trade-offs, and the credential split between Host Agent and Cloud API. proposal.md/design.md were corrected during implementation to reflect two findings: no new anthropic/openai dependency is actually needed, and CloudProxyToolCallingClient uses its own sync httpx.Client rather than a new HostAgentClient method, per the thread-boundary reasoning above.	2026-07-13 21:27:48 +08:00