Repository navigation
docs: glance cards as main draws them (toasts, dismiss, notice cards, no chat in agents' cards) - #271
Merged
Merged
Conversation
… no chat in agents' cards) The headless instrument run of the desktop shell showed where #269's README was wrong, and #273 and #274 have since changed the same ground: - Notifications (#273): a new card opens the glance panel unless a card window is up, and a notify card always posts a toast that opens it in its card window; while the panel is open, toasts stack left of it. Each card has a dismiss button, the panel a close button. Phone: a shade notification. - Notice cards (#274): every <app>.notify fills the shell's one notice card (crates/shell/resources/glance/notice.card, glance_notice.rs); Mail and News hand notify to the shell, Photos, Maps, YouTube and Camera are answered by its notice service. The app-agent table gains them. - No agent-published card has an in-card chat: the notice card and Calendar's event and agenda cards declare no sys.chat, so the card flow ends at the blackboard (steps 12-14 dropped from the sequence and its drawing; step 8 is "toast and glance panel (desktop), shade notification (phone)"). The only shipped card with a chat is the OCTOSENSE_GLANCE_DEMO=mail demo card, with canned replies. For the system apps the way in is "Ask <app>". English and Chinese, root and apps READMEs together. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ymote
force-pushed
the
docs/glance-card-truth
branch
from
October 2, 2026 07:29
686135f to
6ffa9f9
Compare
ymote
changed the title
This was referenced Oct 2, 2026
Merged
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
1 participant
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.
Correct the root and system-app READMEs to match Glance publication and notification behavior. The shared notice card and Calendar event/agenda cards contain no chat; users reach those app agents through “Ask ”. The Mail chat demo returns canned replies. Keep English and Chinese aligned and retain the corrected card-flow image.
The writing revision separates template publication, desktop/phone behavior, interactive cards and chat availability. A platform table replaces a long paragraph; repeated chat caveats link to one availability section. Clarify the kernel-issued peer identifier and the role of the approval router.
Validation for this writing revision: source review, relative file/heading links, bilingual consistency, Markdown fences and whitespace. No runtime behavior changed and no new GUI/device execution is claimed. Earlier image/runtime evidence is unchanged.
This PR overlaps #275 in the root/apps READMEs. Their shared explanations have been aligned, but reconcile the overlapping branches before merging. Both remain open.
Writing assessment after parallel revision and a separate review: 4.6/5 (A−), considering beginner orientation, terminology, worked examples, organization and consistency. This supersedes the earlier combined technical/writing score where present; it is our assessment, not an external approval.