docs: reconcile architecture guidance - #518
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
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
Reconciles contributor and architecture guidance with the current repository structure and enforced coverage thresholds.
htmltrust boundaryWhy
The normative documentation and nearby comments had drifted from the Vitest configuration and current Dashboard architecture, which could mislead contributors and coding agents.
Validation
npm test(183 files, 6,079 tests)node build/check-boundaries.mjsnpx tsc --noEmitReview finding not changed
The Setup-role draft remains unchanged: its cited implementation site rejects Setup-role tile references, rather than implementing the draft's proposed setup wave.