docs: show mobile decision portal - #109
Merged
Merged
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.
What
Why
The public Desktop README did not show the mobile decision interface. Existing wording also implied that evidence never left one computer, although the paired phone receives it inside the customer-controlled boundary. The request and result states and their trust boundary were not clear.
Impact
Operators can now see the request, allowed actions, runner receipt, and evidence boundary before installation. This change does not alter runtime decision semantics.
Validation
uv run pytest -q tests/test_portal tests/test_public_metadata.py— 144 passednpm run build— passednpm run test:ui— 70 passedgit diff --check— passed