Skip to content

v0.13.3 — Trusted Planner Semantics

Choose a tag to compare

View all tags
@ITSpecialist111 ITSpecialist111 released this 11 Jul 14:59
· 4 commits to main since this release
0.13.3
d2d3cbd

Trusted planner semantics

Live testing of 0.13.2 successfully restored Home Assistant and Ollama tool use, then exposed one conservative classification edge case: ha_summarise_area was recorded as a low-impact mutation instead of being executed as a read.

Fixed

  • Plan mode now uses the authoritative ToolRegistry semantics already used by the deterministic scheduler.
  • Registered read-only tools always execute to ground a plan in live Home Assistant state.
  • Registered mutations are always intercepted, even when their names look read-only.
  • Added summarise_ and summarize_ compatibility prefixes for unregistered/custom tools.
  • Rejected the single spurious pending plan created by the read-only live test. No Home Assistant state was changed.

Verification

  • Live 0.13.2 state probe: 2,696 entities, 44 domains, 111 ms.
  • Live Ollama run completed in two iterations with 2/2 successful tools, zero failures, and no connection or Pydantic error.
  • Focused planner/HA/Ollama/API set: 69 passed.
  • Full backend suite: 285 passed, 4 optional live-MCP tests skipped.
  • Frontend production build passed; npm audit found 0 vulnerabilities.
Assets 2
Loading