Add decision replay evidence closure packet

[RicheyWorks]

Summary

• Add top-level decisionReplayEvidenceReviewerClosurePacket to /api/routing/compare as additive, read-only reviewer metadata derived from existing closure summary, rollup, and checklist data.
• Surface the packet in the static reviewer UI pages and document it as in-response metadata only, not an export/share/download packet.
• Add focused API/OpenAPI/UI/docs/no-healthy/scenario-replay coverage for deterministic packet behavior and explicit not-proven boundaries.

Verification

• mvn -B dependency:tree -Dincludes=org.apache.tomcat.embed
• mvn -q test -Dtest=RoutingDecisionReplayEvidenceReviewerClosurePacketServiceTest,ApiContractTest,RoutingOpenApiContractTest,RoutingDecisionVectorReadOnlyExposureTest,ScenarioReplayControllerTest,RoutingDecisionDemoTest,LoadBalancingCockpitDemoTest,EnterpriseLabDecisionReplayEvidenceClosurePacketDocumentationTest,EnterpriseLabDecisionVectorDocumentationTest,EnterpriseLabCockpitFramingDocumentationTest,ReviewerTrustMapDocumentationTest
• mvn -q test
• mvn -q -DskipTests package
• mvn -B package
• git diff --check
• git diff --check origin/main...HEAD
• .\scripts\smoke\enterprise-lab-workflow.ps1 -Package

Boundaries

This is additive reviewer metadata only. It does not change routing behavior, strategy selection, scoring internals, proxy behavior, replay execution, what-if mutation, persistence/storage, telemetry, fingerprints, upload/share/download/export/PDF/ZIP behavior, Docker, CI, release, signing, registry, or governance settings.

Remaining not-proven boundaries: not replay proof; not scoring proof; not correctness validation; not production readiness; not production certification; not guaranteed replay; not production validation.