[codex] ci: add public harness guard - #63
Merged
Merged
Conversation
PerishCode
marked this pull request as ready for review
May 18, 2026 12:25
lefarcen
approved these changes
May 18, 2026
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.
What changed
mainpushes.@html-anything/nextowns the complete Next app undernext/.@html-anything/e2eowns Playwright as the sole browser-test source undere2e/.scripts/guard.ts.scripts/guard.tsto enforce the root /next/e2eproject shape.tests/uitoe2e/ui.next/font/googlefrom the app shell so public CI builds do not depend on external Google font downloads.pnpm -F @html-anything/next ...andpnpm -F @html-anything/e2e ....Why
This establishes the minimal public harness boundary before large feature branches such as export-target work rebase onto
main. The goal is to make directory shape, app tests, browser smoke, and CI expectations explicit without requiring secrets.Validation
pnpm install --frozen-lockfilepnpm exec tsx scripts/guard.tspnpm -F @html-anything/next typecheckpnpm -F @html-anything/e2e typecheckpnpm -F @html-anything/next testpnpm -F @html-anything/next buildpnpm -F @html-anything/e2e testgit diff --checkpnpm -F @html-anything/next buildstill emits the existing Turbopack NFT tracing warning throughnext/src/lib/agents/invoke.ts, but the build exits successfully.