docs: document legacy Anycast design - #4
Open
musepy wants to merge 1 commit into
Open
Conversation
musepy
marked this pull request as ready for review
July 30, 2026 07:48
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.
What changed
DESIGN.mdas a factual baseline of the shipped Anycast product structure and visual language.legacy-baselineso it is not confused with the 2.0 redesign.Why
A stable description of the existing product is needed before updating the first screen toward the 2.0 design. Keeping that baseline separate makes later UI changes easier to review without conflating existing behavior with proposed design work.
Impact
Documentation only. No runtime code, dependencies, persistence, configuration, or release behavior changes.
Validation
git diff --check origin/main...HEADstatus: legacy-baselineFlutter checks were not run locally because this PR changes documentation only; required repository checks can run on the PR.