Improve dashboard maintainability before the next release

The dashboard had several oversized orchestration, component, and CSS files that made product-copy changes and mobile/performance work risky. This refactor preserves behavior while splitting scan terminal CSS, opportunity helpers, future forecast panels, history/detail charts, and probability/model sections into smaller ownership boundaries. Constraint: No user-visible version bump because this batch is architecture and performance cleanup, not a release announcement. Rejected: Rewrite dashboard state management in the same batch | too broad for a safe upload after CSS and component splitting. Confidence: high Scope-risk: moderate Reversibility: clean Directive: Keep new component/CSS boundaries instead of moving product copy back into the large dashboard files. Tested: npm run build; npm run test:business; git diff --check Not-tested: Browser visual smoke test after push
2026-04-28 20:19:17 +08:00
parent 20516000a2
commit 2b1d7c0b65
56 changed files with 15303 additions and 15063 deletions
@@ -0,0 +1,87 @@
+"use client";
+
+import { formatConfidenceLabel } from "./FutureForecastModal.utils";
+
+export function FutureForecastTodayDecisionBrief({
+  anchorRuleText,
+  anchorSourceLabel,
+  baseCaseBucket,
+  confidence,
+  displayName,
+  downsideBucket,
+  gapToBaseText,
+  locale,
+  meteorologyHeadline,
+  nextObservationLabel,
+  nextObservationTime,
+  pathStatus,
+  settlementStationName,
+  upsideBucket,
+}: {
+  anchorRuleText: string;
+  anchorSourceLabel: string;
+  baseCaseBucket: string;
+  confidence: string | null | undefined;
+  displayName: string;
+  downsideBucket: string | null | undefined;
+  gapToBaseText: string;
+  locale: string;
+  meteorologyHeadline: string;
+  nextObservationLabel: string;
+  nextObservationTime: string;
+  pathStatus: string;
+  settlementStationName: string;
+  upsideBucket: string | null | undefined;
+}) {
+  return (
+    <section className="future-v2-meteorology-brief">
+      <div className="future-v2-meteorology-copy">
+        <div className="future-v2-anchor-row">
+          <div className="modal-section-kicker">
+            {locale === "en-US" ? "Professional meteorology read" : "专业气象判断"}
+          </div>
+          <span className="future-v2-anchor-source">{anchorSourceLabel}</span>
+        </div>
+        <h3>{meteorologyHeadline}</h3>
+        <p className="future-v2-anchor-rule">{anchorRuleText}</p>
+        <div className="future-v2-meteorology-meta">
+          <span>
+            {locale === "en-US" ? "Confidence" : "置信度"} ·{" "}
+            {formatConfidenceLabel(confidence, locale)}
+          </span>
+          <span>
+            {locale === "en-US" ? "Path state" : "路径状态"} · {pathStatus}
+          </span>
+          <span>
+            {nextObservationLabel} · {nextObservationTime}
+          </span>
+        </div>
+      </div>
+      <div className="future-v2-decision-rail" aria-label={displayName}>
+        <div className="future-v2-decision-anchor">
+          <span>{locale === "en-US" ? "Anchor" : "锚点"}</span>
+          <strong>{settlementStationName}</strong>
+          <small>{anchorSourceLabel}</small>
+        </div>
+        <div className="future-v2-decision-grid">
+          <div>
+            <span>{locale === "en-US" ? "Base" : "基准"}</span>
+            <strong>{baseCaseBucket || "--"}</strong>
+          </div>
+          <div>
+            <span>{locale === "en-US" ? "Upside" : "上修"}</span>
+            <strong>{upsideBucket || "--"}</strong>
+          </div>
+          <div>
+            <span>{locale === "en-US" ? "Downside" : "下修"}</span>
+            <strong>{downsideBucket || "--"}</strong>
+          </div>
+          <div>
+            <span>{locale === "en-US" ? "Gap to base" : "距基准还差"}</span>
+            <strong>{gapToBaseText}</strong>
+          </div>
+        </div>
+      </div>
+    </section>
+  );
+}