fix(frontend): restore verification commands#2287
Open
anirudh5harma wants to merge 1 commit into
Open
Conversation
This was referenced Jun 29, 2026
anirudh5harma
force-pushed
the
codex/fix-frontend-verification
branch
from
14ec1f3 to
da6f591
Compare
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
Frontend contributors can now run the documented
npm run buildcommand on a clean checkout, and pull requests regain the TypeScript gate that the workflow still described as broken even though currentmaintypechecks successfully.Closes #2281.
This updates aoagents/ReverbCode#419 for the canonical repository: the obsolete Forge typing workaround is intentionally omitted.
Validation
npm run typechecknpm run buildnpm test -- --run(40 files, 370 tests)git diff --checkPost-Deploy Monitoring & Validation
Watch the first frontend pull-request workflow after merge. Healthy signals are a successful Typecheck step followed by Vitest, and successful desktop packaging from
npm run build. Any cross-platform typecheck failure or packaging regression is the rollback trigger.