feat!: move to StackOne AI SDK 3.0 and its search and execute tools (ENG-3175)
Part of ENG-3175. Moves the plugin to StackOne AI SDK 3.0. uv.lock pins stackone-ai 3.0.0 from PyPI (published 2026-10-29); CI passes on 3.11–3.13.
This branch includes #26 (the CI workflow and lock refresh, approved) as a merge commit, so its diff shows here too. Merge #26 first and this diff shrinks to the plugin change.
- Dependencies:
stackone-ai>=3.0.0,<4.0.0(the[mcp]extra no longer exists); Python 3.11+, as the SDK requires; the CI matrix is 3.11–3.13. Version 0.3.0. - Public APIs only: the plugin's own
GET /accountsdiscovery and its call to the private_build_tools()are gone; the SDK discovers accounts itself. If tools can't be loaded, the plugin still logs a warning and registers none. mode="search_and_execute"maps to the SDK'stool_mode="search_execute": StackOne'sstackone_search_actions,stackone_execute_actionandstackone_list_accounts, served by the server.search=,SearchConfigandSearchModeare removed.- Tools declare the served schema and
requiredlist (to_openai_function()) and return the server's{isError, result}as written. - Tests rewritten (20); examples, README and CHANGELOG (with a 0.3.0 migration note) updated.
Checks: 20 tests pass; ruff and mypy clean. sdk-conformance's smoke_adk.py and the plugin's search mode pass through the real SDK branch (StackOneHQ/stackone-ai-python#231) against the mock API.
Live (production API, Gemini 3.1 Pro, a Google Calendar account): ADK agents passed in individual and search mode. Production still serves the per-account pair, so search mode there exercised that; the trio needs unified-cloud-api#9417 (merged).
Update: on the merged server (#9417) the plugin needs no code change: the SDK presents one account's own pair as stackone_search_actions / stackone_execute_action, so the plugin registers those names however many accounts are in scope (stackone_list_accounts only with several, at most 50). README, CHANGELOG and docstrings updated to say so.