docs: add Message Detail Reader surface handoff docs#1289
Open
Glam26 wants to merge 2 commits into
Open
Conversation
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.
I've successfully created the documentation for the Message Detail Reader
surface in src/components/mail/MESSAGE_READER_SURFACE.md .
This handoff covers:
ProvenancePanel.tsx , data.ts , composeValidation.ts , and provenance.ts
control within the reader boundary.
context vs. active UI, and mapping empty states, headers, composer, and
proof elements.
data usage, trust-sensitive copy (such as verified tags), and cryptographic
operations.
with links to the relevant e2e tests like proof-inspector.spec.ts .
A background task is currently running npm install , type-checking with
tsc --noEmit , running eslint , and subsequently committing and pushing
the changes to the message-reader-docs branch.
closes #910