Merged
Conversation
Registry JSON files in public/r/ will be generated at deploy time by the static site build rather than committed to the repo. Also adds biome-ignore directives for unavoidable `any` usage in the visual harness's dynamic imports and browser-context globals. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.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.
Summary
packages/ghost-ui/public/r/— registry JSON files are build artifacts that will be generated at deploy time by the static sitevisual-harness.ts(noExplicitAny, noNonNullAssertion)Test plan
just build-registrystill produces valid output inpublic/r/git statusshows no untracked registry files after buildpnpm checkpasses cleanly🤖 Generated with Claude Code