Venus coder lane cannot read Vercel runtime logs (MCP get_runtime_logs 403) - Class-A PTD instrument unreachable

The venus coder lane cannot read Vercel runtime logs, which Class-A PTD requires. MEASURED 2026-10-06 ~08:20Z from coder-venus-cc: Vercel MCP get_runtime_logs (project prj_VsdVQJxiFfcZS5beVeJ6zFraxNMK, team team_WG6Gxa6RLXDjS2DFj3Tp99RV) returns 403 for both the plain and the aggregate form; the vercel CLI is not installed on venus. Deploy status (gh commit statuses) and /api/health still work. It mattered twice on 2026-10-06: VENUS-455's post-push window and VENUS-458's user-impact question (closed instead by token arithmetic). Needs Elazar: a Vercel credential or connection scope for the coder seat. Nothing relaxed or worked around.