Polish strict Enterprise Lab cockpit monitoring

[RicheyWorks]

Summary

• Adds a strict Enterprise Lab Cockpit Monitor section to /routing-demo.html for controlled lab routing-proof review.
• Expands reviewer/operator how-question guidance for decision interpretation, reproduction, lab monitoring signals, edge cases, and evidence handoff.
• Adds browser-local Copy lab monitor explanation text assembled from visible local lab state only.
• Updates docs/REVIEWER_TRUST_MAP.md and guardrail tests for discoverability, strict lab wording, fallback text, and safety boundaries.

How-question inventory summary

• Already covered before this sprint: Routing Proof Summary, Scenario Comparison, Evidence Associations, Reviewer Workflow Checklist, Reviewer Confidence Signals, Evidence Navigation, copyable proof/association/walkthrough text, and several edge-case fallbacks.
• Strengthened in this sprint: what the cockpit monitors, how selected backend/strategy/signals should be interpreted, close-candidate limits, unchanged backend with changed signals, changed backend with same strategy, changed strategy with same backend, unhealthy/degraded/recovery interpretation, local reproduction, evidence-page relationship, clipboard fallback, empty/unavailable local API responses, and pre-run static guidance.
• Kept bounded: exact production scoring is not claimed unless exposed by the API; the route name /routing-demo.html remains for compatibility.

What the lab cockpit monitors

• Active lab scenario.
• Routing comparison request status.
• Selected strategy and selected backend/server.
• Backend health state and availability.
• Visible latency/load/active connection/capacity/weight-style signals where present.
• Scenario delta state.
• Degradation/fallback/recovery state.
• Evidence association path.
• Reviewer handoff readiness.
• Local lab boundary and production proof gaps.

Strict lab wording changes

• Reframes product-facing cockpit copy as an Enterprise Lab proof cockpit, controlled lab evidence, local lab proof, and pre-production evidence review.
• Reduces casual demo wording in visible cockpit/trust-map text while preserving the existing /routing-demo.html route and Postman folder names for compatibility.
• Adds explicit text that this is not a casual demo page and not a production monitoring surface.

Core scope completed

• Yes. Added/polished Enterprise Lab Cockpit Monitor, How This Routing Decision Was Made, What This Lab Needs to Monitor, How to Reproduce and Explain This Lab Proof, How to Read Lab Edge Cases, copyable lab monitor explanation, strict lab boundaries, and tests.

Stretch scope completed or deferred

• Completed. Added How Strategy Choice Matters, How Evidence Supports the Decision, and an Enterprise Lab cockpit monitoring/how-question guide in the reviewer trust map.

Tests run

• mvn -q -Dtest=RoutingDecisionDemoTest,ReviewerTrustMapDocumentationTest,CockpitDiscoverabilityDocumentationTest,EnterpriseReadinessAuditDocumentationTest test - PASS.
• mvn -q test - PASS.
• mvn -q -DskipTests package - PASS.
• mvn -B package - PASS, 1412 tests, 0 failures, 0 errors, 0 skipped.
• git diff --check - PASS.
• powershell -NoProfile -ExecutionPolicy Bypass -File scripts/smoke/enterprise-lab-workflow.ps1 -Package - PASS.
• Packaged resource check for target/classes/static/routing-demo.html and built JAR entry - PASS.
• Extracted inline script node --check - PASS.
• Loopback smoke for /routing-demo.html, linked static evidence pages, and /api/routing/compare - PASS.
• Secret scan over added lines - PASS.
• Unsafe command scan over added lines - PASS.
• External call/CDN/analytics scan for routing page - PASS.
• Upload/share/server-side export scan over added product text - PASS.
• Overclaim scan over added product text - PASS.
• Test weakening scan - PASS.
• Generated target evidence/log hygiene check - PASS; no generated target evidence tracked.

Safety boundaries

• Static dashboard/docs/tests only.
• No Java production/API/routing code changed.
• No external dashboard calls, CDNs, analytics, telemetry, upload/share endpoint, or server-side export/PDF/ZIP generation added.
• No releases, tags, GitHub Releases, registry login/publish, container signing, live cloud validation, private-network validation, branch deletion, or GitHub settings/rulesets/secrets/environment mutation.
• No tests were disabled, skipped, deleted, or weakened.

Not-proven limits

• No production traffic proof.
• No production telemetry proof.
• No live cloud proof.
• No real tenant proof.
• No SLA/SLO proof.
• No registry publication proof.
• No container signing proof.
• No governance-applied proof.
• No production certification claim.

Production code changed

No.

Runtime behavior changed

No. Static reviewer UI/docs/tests only; no routing/API/server behavior changed.