chore: format .claude/settings.json as the standard does - #10
Merged
Conversation
Same settings, written compact where termlens and mossaic write them formatted. Functionally identical and textually different, which is exactly the drift the ecosystem repo's sync tool exists to catch — and it caught this one on its first dry run, before anybody had to notice by eye. Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
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.
Same settings, written compact here where termlens and mossaic write them formatted. Functionally identical, textually different.
Caught by the new ecosystem repo's
tools/sync.sh --dry-runon its first run — which is the point of having it: two files that mean the same thing but do not match are indistinguishable from two files that disagree, until something compares them.