fix: strict calendar time-lock validation, LaTeX syntax repair, and repository sync
This commit is contained in:
@@ -167,6 +167,9 @@ The workstation enforces zero silent caching or historical data ingestion:
|
||||
* *Amber Badge (`⚠️ ARCHIV-DATEN (API OFFLINE)`)*: Live API timeout, failure, or developer shield fallback active (`isLiveApi: false`).
|
||||
* **Crypto Bayes Module**:
|
||||
* *Full-Width Scannability*: Layout structured into 100%-width, centered grids containing the Walk-Forward Ensemble Radar and Active Learning Feedback Loop.
|
||||
* *Strict Calendar Time-Locks*: Enforces an ironclad delta check against the fixed system date (`2026-06-17`) through `isHorizonPending`. Horizons (1 day, 5 days, 10 days) remaining within their lock duration strictly display countdowns and remain in a pending state, preventing look-ahead evaluations.
|
||||
* *Row Expulsion*: Clicking "Hide Row" updates the forecast record with `isHidden: true` locally and saves it to LocalStorage. Hidden rows are filtered out from table rendering but remain intact for the metrics engine.
|
||||
* *Hit Ratio Counter*: Formatted as `Hit Ratio Counter: [True Count] True / [Total Resolved Count] Total` using `{tracker.alpha} True / {tracker.alpha + tracker.beta} Total`.
|
||||
* *Countdown Formatter*: Remaining seconds under pending targets are formatted to human-readable durations (e.g. `Verbleibend: 1 Tag, 19 Std`) using `formatRemainingTime`.
|
||||
* *Accordion Matrix*: Each log row is expandable via Chevron toggle, displaying the individual model prediction direction and success/failure correctness status checkmarks upon resolution.
|
||||
* *Multi-Accuracy Tracking*: Shows distinct columns for `T+1 Acc`, `T+5 Acc`, and `T+10 Acc` rather than a single aggregated metric.
|
||||
|
||||
Reference in New Issue
Block a user