Conversation
…ff, buffer short finals, and make distinct-voice merging deterministic
… floor-gate audio, and stop dropping speaker profiles on meets and subprocess calls
…ffected the join flow before this
Bump global-agent-rules and regenerate AGENTS.md so agents search ~/shared_context.
Pin unifyai/shared_context under shared_context/ and refresh AGENTS.md for the yours/{login} layout.
The reactive brain only ever saw a generic dispatch string (original_request) next to a completed task's result -- never the task's own authored description, which is the only place any delivery intent (e.g. "deliver this summary unprompted") lives today. Add optional task_description plumbing on _register_live_task_handle and render it as a new <task_description> tag alongside <original_request> when present. No caller populates the field yet; this is groundwork for wiring the actual live dispatch sites.
…patch Both the due-task and REST-triggered live dispatch paths now surface the task's authored description to _register_live_task_handle, so completed-actions rendering carries it to the reactive brain alongside the generic dispatch string. The due path already had the description in scope via the activation snapshot; the trigger path adds a lookup through the scheduler and tolerates a missing task gracefully.
The live provider-event dispatch path (the one behind today's Twin 2693 incident: a GitHub-issue-triggered task completed with a valid summary but the reactive brain never delivered it) already fetches the task definition internally but never surfaced its description back to the caller. Extend LiveProviderEventDispatchOutcome with a description field, resolve it concurrently alongside the existing revision/context lookups, and thread it through to _register_live_task_handle so completed-actions rendering carries it.
Keep transcript archive as a private sibling clone so public unify cloners are unaffected.
The running-state PATCH for provider-event dispatch never included started_at, unlike the scheduled-task path. This left started_at (and therefore client-computed duration) null for every provider-event triggered run in the console's run history.
The provider-event branch of task deletion called the typed revision-CAS delete and then redundantly bulk-deleted the same already-gone row by id, which now 404s under the collapsed task-identity data model. The actor recovered and reported correctly, but only after extra retries triggered by the spurious error.
…listing the trigger catalog The catalog tool always returned every connected app's full trigger listing with no way to narrow it, which forced an actor authoring a provider-event task to either guess trigger slugs or read past a truncated response. Thread canonical_app_slug/limit/offset through to Orchestra's catalog endpoint, mirroring the parameter shape already used by list_provider_trigger_connections.
magic-marty
approved these changes
Jul 28, 2026
magic-marty
left a comment
magic-marty
left a comment
Collaborator
There was a problem hiding this comment.
Release approval: staging → main.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| return False | ||
| return any( | ||
| cookie.get("name") in GOOGLE_AUTH_COOKIE_NAMES | ||
| and "google.com" in (cookie.get("domain") or "") |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Test plan