Fix /projects Vercel build status

bearlabs.net /projects page: the bearlabs.net chip shows a gray Unknown build dot, or no dot at all when /api/vercel/status fails. Diagnosed 2026-10-08: GET https://api.vercel.com/v6/deployments?teamId=team_pfIUJgOA4IPo1BRxxxzvGmcr&projectId=prj_i8EkDG9rFSbQAZ6WGVwuYcgNVOQN&target=production with VERCEL_TOKEN returns 403 (Not authorized: trying to access resource under scope bearlabs-nets-projects; VERCEL_TOKEN_BEARLABS also 403). The token lacks access to the bearlabs-nets-projects Vercel team; src/app/api/vercel/status/route.ts maps any non-OK Vercel response to UNKNOWN, and useVercelBuildStatus renders no dot when the status fetch itself fails (e.g. 401 for signed-out viewers). Fix: (1) create a Vercel token scoped to the bearlabs-nets-projects team and set it as VERCEL_TOKEN in benben/bearlabs.net/.env.local and in the bearlabs.net Vercel project env for Production (consider standardizing on VERCEL_TOKEN_BEARLABS via TOKEN_ENV_SUFFIX in src/config/vercel.ts). (2) Verify: /api/vercel/status returns READY for bearlabs.net and the /projects chip renders a green Ready dot. (3) Surface the Vercel HTTP code in the UNKNOWN payload (e.g. error: vercel-403) so future token regressions are diagnosable from the chip title. Files: src/config/vercel.ts, src/app/api/vercel/status/route.ts, src/hooks/useVercelBuildStatus.ts, src/components/react/project/ProjectChips.tsx.