Align judge bundle provenance with optional deploy/publish evidence

[Web-pixel-creator]

What changed

This PR aligns the judge-facing evidence bundle with deploy/publish provenance without making deploy summaries mandatory for ordinary local judge flows.

The judge bundle now surfaces compact provenance when available:

• Railway deploy status, deployment id, public URL, and badge endpoints
• repo-publish verification script and deploy flags

When the optional artifacts are absent:

• provenance sections are omitted instead of showing unavailable / null
• judge-facing markdown does not embed or foreground raw deploy/publish JSON

Main updates

• updated scripts/judge-visual-evidence-pack.mjs to build a compact optional provenance snapshot
• updated scripts/judge-presentation-bundle.mjs to reuse compact provenance from the visual manifest or derive it from optional summaries
• updated judge docs:
  • docs/judge-visual-evidence.md
  • docs/judge-quickstart.md
• updated directly related judge script/alignment tests
• stabilized full unit validation by:
  • adding explicit provenance contract markers in scripts/release-readiness.ps1
  • isolating tests/unit/skills-catalog.test.ts from global process.env

Behavior

• missing deploy summaries remain optional
• judge presentation stays concise
• only compact provenance is surfaced, not raw oversized JSON
• ordinary local judge flows continue to work without deploy/publish artifacts

Validation

• npm run test:unit ✅
• npm run build ✅
• npm run demo:e2e:visual-pack ✅
• npm run demo:e2e:visual:bundle ✅
• npm run verify:release not run because release behavior did not change