fix(frontend): clear React Router audit gate

[proerror77]

Change contract

Upgrade the PLOY frontend from React Router 6.30.4 to 7.18.1 so the production dependency audit passes while preserving the existing route, redirect, navigation, lint, build, and bundle-size contracts.

Out of scope

Frontend redesign; unrelated dependency upgrades; Polymarket verifier or evidence changes; collector/cloud runtime; evaluator/MCTS; Paper or Live.

Dependency or merge order

Base: main@000efe141943422d3209f369252f073f609bedc3. Merge this focused PR before rebasing/re-running #298, which is independently blocked by the repository-wide frontend audit gate.

Focused validation

• Red proof: npm audit --omit=dev --audit-level=moderate failed on 6.30.4 with GHSA-wrjc-x8rr-h8h6 and GHSA-337j-9hxr-rhxg.
• npm ci --prefix rust_hft/prediction-markets/ploy-frontend — passed from the checked-in lockfile.
• npm run contracts:check --prefix rust_hft/prediction-markets/ploy-frontend — passed.
• npm run lint --prefix rust_hft/prediction-markets/ploy-frontend — passed.
• npm run build --prefix rust_hft/prediction-markets/ploy-frontend — passed; largest JavaScript chunk 244.73 KiB.
• npm audit --omit=dev --audit-level=moderate --prefix rust_hft/prediction-markets/ploy-frontend — 0 vulnerabilities.
• git diff --check — passed.
• Matt two-axis read-only review — Standards: APPROVE; Spec: APPROVE.

Rollout or rollback impact

Static frontend dependency/lockfile update. Rollback restores the vulnerable dependency and the intentional audit failure; no data or runtime migration.

Why no PRD

#299 is a reproduced dependency-security defect with one bounded compatibility surface, so Matt triage plus focused TDD/validation is sufficient.

Closes #299.

[coderabbitai]

Warning

Review limit reached

@proerror77, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4a047bc9-41f2-4d13-a7d0-7e986e68b138

📥 Commits

Reviewing files that changed from the base of the PR and between 000efe1 and 64e3296.

⛔ Files ignored due to path filters (1)

• rust_hft/prediction-markets/ploy-frontend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• rust_hft/prediction-markets/ploy-frontend/package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/frontend-react-router-audit-299

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}