Skip to content

Release: staging → main#259

Merged
djl11 merged 12 commits intomainfrom
staging
Apr 16, 2026
Merged

Release: staging → main#259
djl11 merged 12 commits intomainfrom
staging

Conversation

@djl11
Copy link
Copy Markdown
Member

@djl11 djl11 commented Apr 16, 2026

Merge all staging changes to main.

YushaArif99 and others added 12 commits April 13, 2026 19:22
Parse scheduled task wake reasons, validate current activations, and surface
live trigger candidates so the slow brain can start the right task.
The live runtime was validating due and trigger activations against the SDK default project, so staging sessions saw empty machine-state rows even when Orchestra had projected them correctly. Pin machine-state reads to the Unity project and log wake-reason replay and due-task rejection outcomes so live failures are visible.
Add the headless offline runner, enforce offline task contracts, and rearm recurring scheduled tasks from the previous occurrence. This also mirrors due and trigger context into the voice fast brain before the opening greeting.
Move task due, trigger matching, and fast-brain wake context into a dedicated domain module so event handlers stay focused on event routing. Keep the existing communication handling intact while making the task activation path easier to read.
Restore the pre-refactor room-name behavior when WhatsApp permission is granted before an assistant id is populated. Add a focused regression test so the handler stays behavior-preserving.
Use the richer wake contract to give the slow brain and fast brain clearer scheduled and triggered task context. This keeps wake handling more colleague-like without exposing offline work or internal task-machine jargon.
The startup greeting should stay social even when buffered task wake notifications are already present in history. Move the greeting-specific guardrail into the prompt builders and align the first-turn eval with the real fast_brain_greeting path so the test matches production.
Task activations and runs now live in Assistants, so Unity should query the same project for due validation and run updates.
Add a public deploy-runtime seam with local defaults so Unity can stay local-first while hosted session assignment, metrics, and job lifecycle logic move behind private runtime backends.
Capture scheduled and triggered provenance before live execution begins so Unity can create or adopt the durable run row at task start and patch terminal state back to Orchestra.
Align queue and offline execution updates with the assistant-scoped run contract and cover the new behavior in task scheduler and activation tests.
Point the ConversationManager fast-brain defaults and prompt test fixture at gpt-5.4-mini so voice calls use the newly supported low-latency model by default.
Clarify Unity's positioning as persistent AI colleagues and move the demo, architecture, and evaluator entry points above the fold so the repo is easier to assess quickly.
@djl11 djl11 merged commit 6226cb2 into main Apr 16, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants