Repository navigation
Prepare the registry developer trial and live install verification - #30
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.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
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.
The registry pilot is live after #29. This adds a copyable Next demo, a short developer trial guide and repeatable checks against the public installation URLs. Developer outreach is skipped at Simone’s request; the trial material is available for later use.
--registry-baseto compare all four published payloads and llms.txt with the checkout, then run fresh Next/Vite URL installs against that host.Validation: npm test and all CI checks passed. Fresh public URL installs passed strict TypeScript, production builds and the Chrome browser matrix. The optional WebKit 26.4 matrix also passed. The demo typechecked and built in Next; real KERN H.264 media passed forward/reverse seeking, reduced motion and no-JS checks in WebKit.
After Safari automation was enabled, native Safari 26.6.2 passed the real-media demo: decoding, pointer tilt, Option-Tab link navigation, forward/reverse seeking, narrow-window poster/media release, wide-window recovery and failed-media fallback. Screenshots were inspected. Its OS reduced-motion setting was left unchanged; automated reduced-motion coverage comes from Chrome/WebKit.
Limits: the WebKit runner resets reload scroll even on a plain static HTTP control page, so its test explicitly restores the host position and checks frame mapping; Chrome separately proves native reload restoration. A narrow Safari window is not a physical iPhone test. Physical iPhone testing remains unverified; no participant feedback has been collected.