Continuous enhancement: range routing and UI stability

[ryun6249]

Continuous Enhancement Report

1. Current Status

• Project purpose: Local FastAPI + static UI financial research workstation for market, macro, Quant Lab, Quantamental, ML Forecast, AI Portfolio, and local LLM-assisted briefings.
• Existing structure preserved: yes; this PR is stacked on automation/continuous-enhancement-20260519-0920 and does not touch master directly.
• Main issues found: standard ranges could reuse stale custom date bounds; /ui/quantamental returned 404 instead of the SPA shell; date inputs and mobile tabs had readability issues.

2. Changes Made

Compatibility

• Added UiStaticFiles so extensionless /ui/<client-route> paths serve index.html, while missing asset paths still return 404.

Data Consistency

• Standard global ranges now recalculate from current local date bounds instead of stale custom start/end values.

UI/UX

• Dashboard date fields fit full YYYY-MM-DD values.
• Mobile dashboard tabs now scroll horizontally and align the active tab without vertical page jumps.

Visualization

• Range support text and visible controls now reflect the active standard period without stale custom anchors.

AI Briefing

• No model/provider behavior changed; Qwen/Gemma remain runtime-checked, and deterministic guardrail stays default.

Translation

• No translation logic changed; Korean/English static contract remained clean.

Performance

• No new background polling, LLM calls, or heavy synchronous work.

Tests / Validation

• Syntax, contract, targeted pytest, live route checks, and Playwright screenshots passed.
• Quantamental API regression remains blocked on this clean stacked branch because the broader pipelines.quantamental.service implementation is not tracked in the branch.

3. Changed Files

File	Change	Reason
app/api/server.py	Added SPA client-route fallback static handler	Keep /ui/quantamental reachable without masking missing assets
app/web/app.js	Reset standard range bounds and align active tab horizontally	Prevent stale period anchors and improve mobile tab usability
app/web/styles.css	Wider date columns and scrollable dashboard tabs	Avoid clipped dates/tabs
app/web/index.html	Bumped asset query version	Ensure updated static assets load
scripts/check_ui_contract.py	Added markers for range reset and tab alignment	Guard the new behavior
scripts/ai_portfolio_ui_smoke.py	Bumped app bundle version	Keep smoke selector current
tests/test_ui_routing_contract.py	Added route/range/UI contract assertions	Prevent regression
docs/CONTINUOUS_ENHANCEMENT_LOG.md	Added run analysis, plan, validation, checklist	Keep automation record current

4. Validation Results

Check	Command / Tool	Result	Notes
Lint	git diff --check -- ...	Passed	Only CRLF normalization warnings
Build	N/A	Excluded	No repo package.json/pnpm-lock.yaml; static UI validated by Python/Playwright
Test	python -m pytest tests/test_ui_routing_contract.py tests/test_ui_modules.py tests/test_quantamental_ui_ai_panel.py tests/test_api_routing_contract.py -q	Passed	55 passed, 4 subtests passed
UI validation	npx playwright screenshot desktop/mobile	Passed	Captured 1440x1000 and 390x900 Quantamental screenshots
Data validation	python scripts/check_ui_contract.py + live route checks	Passed	/ui/quantamental 200, missing asset 404, range markers present
AI briefing validation	tests/test_quantamental_ui_ai_panel.py + /api/v1/config	Passed	Used-data UI fixture passed; Qwen/Gemma remain runtime-checked

5. Remaining Risks

• This PR is stacked on the prior open automation branch, not directly on master.
• tests/test_quantamental_api.py is blocked in this clean stacked branch because only pipelines/quantamental/ai_service.py is tracked; pipelines.quantamental.service is outside this branch as prior dirty/untracked work.

6. Next Enhancement Suggestions

1. Reconcile and commit or intentionally drop the untracked Quantamental backend implementation so full pytest can run from a clean clone.
2. Add a small browser/DOM smoke that asserts no horizontal overflow on mobile without relying only on screenshots.
3. Extend range-bound tests to a real JS unit harness once the static UI has a configured frontend test runner.

7. Safety Notes

• main/master was not modified directly.
• Auto-merge was not enabled.
• Secrets were not touched.
• Trading/order execution logic was not modified.
• Unsupported facts were not presented as verified.