feat(runtime): add desktop-neutral runtime event contract #96
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/zara!96
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/runtime-events"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #82.
Summary
Introduces the first P0 runtime boundary for Zara Desktop without adding Qt to the runtime core.
AgentManagerand LangGraph; existing voice turns reuse their latency trace ID and future RuntimeHost callers can supply theTurnCoordinatorID directlyzara.petsimportsArchitecture
The desktop will consume queue subscriptions in later issues. Runtime publishers never invoke Qt/UI callbacks directly.
Compatibility
zara.pets.runtime_bridgekeeps its old function surface for current wake/Pet callers, but each call now publishes a generic runtime event first. Existing Pet event classes and ZMQ names remain intact. The large wake state-machine file is intentionally not rewritten in this PR; its existing Pet bridge calls therefore retain behavior while entering the generic stream.Existing
AgentManager.process_async(...)callers remain source-compatible. It now returns the assignedturn_idin addition to the existing response/tool results.Testing
New tests cover:
GitHub Actions /
scripts/test-all.shis the authoritative merge gate because the local/home/unseen/Documents/Projectsworking tree is not mounted in this execution environment.