policyengine.org/scorecard is a second, hand-fed Vercel project — script the dual-mount build or consolidate the rewrite

www.policyengine.org/scorecard is proxied (policyengine-app-v2 website/vercel.json:169-176) to the policyengine-scorecard Vercel project — separate from the repo-linked policyengine--policyengine-scorecard that app/.vercel deploys. The proxied copy only updates when someone hand-ships it, so the site fell behind main (it predated #82 until 2026-08-22).

The proxy shape also has a mount subtlety: the exact /scorecard rewrite serves the app at a no-trailing-slash document URL, where the Vite base: "./" build's relative assets resolve to /assets on the website origin and 404. The working deploy ships the static output twice — at root and under scorecard/ — with <base href="scorecard/"> (relative) in the root index and <base href="/scorecard/"> (absolute) in the nested index. Recipe preserved in the ops notes; first attempt without it briefly broke the site path on 2026-08-22.

Options:

1. Script it: a build:site step in app/package.json that emits the dual-mount output + base tags, and a documented deploy command for the second project (or a CI job on main-push, mirroring the Supabase DB publish).
2. Consolidate: point the website rewrite at the repo-linked project's alias and give that build the dual-mount layout, retiring the second project.

Either way the site surface stops being hand-fed folklore.

Read app/package.json, policyengine-app-v2 website/vercel.json lines 169-176, and the ops notes; inspect the existing Vite output and deploy path first. Decide whether to automate the second project or consolidate it, then verify that main updates the deployed scorecard and that /scorecard assets resolve correctly in both mount forms.