Repository navigation
Conversation
…ndoffs Signed-off-by: egerev <egor@gosync.ai>
egerev
marked this pull request as ready for review
November 13, 2026 11:07
egerev
enabled auto-merge
November 13, 2026 11:07
This branch has not been deployed
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
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.
Active Android orders currently depend on separate status requests. This adds a private durable observation/wake seam, agent-chosen restart-safe check timers and explicit acknowledged responsibility handoff, plus a minimal USB-only NotificationListener source.
Notifications remain untrusted references. Exact order bindings are checked; an unidentified order stays an explicit app-level observation for active candidates. Repeated events coalesce. A downstream timeout or lost reply stays unknown until positive receipt reconciliation and never triggers a resend. New tasks preserve earlier obligations. Question/reply transport retains every native correlation ID and cannot answer approval RPCs.
The source modules expose injectable core/caller callbacks; existing core/API/native/device admission is unchanged. Missing receiver is a visible hold. DK-6 owns that integration. Root owns installation/access, OEM USB peer verification and the released Grok callback/receipt proof. These live criteria remain OPEN on ANYM-997; this PR makes no installed push or delivery claim.
Validation:
Change path: AUTO (additive source seam; no live authority, provider, access, global messaging schema, CI or applied migration changes)
Review record: none (owner 11-11: no reviews)
Spec: ANYM-997
Tiden branch: proposal/2026-11-13-android-order-events
Spec impact:
Settle text: none
Undo: revert this additive source commit before integration. Any later root rollout disconnects only this companion's forward and revokes its own notification access, preserving host obligations and existing native/provider sessions.