Continuous enhancement: Quantamental breakout diagnostic

[ryun6249]

Continuous Enhancement Report

1. Current Status

• Project purpose: FastAPI-served local financial research workstation with static UI, deterministic Quantamental engines, local LLM interpretation guardrails, and browser-validated dashboard surfaces.
• Existing structure preserved: Yes. This is a stacked PR on automation/continuous-enhancement-20260519-1330; it keeps existing API defaults, UI flow, model selection, data providers, and Quantamental signal/composite contracts.
• Main issues found: QAM was already present, but the Quantamental layer still had room for another auditable QUANT diagnostic that explains breakout quality without changing the deterministic signal.

2. Changes Made

Compatibility

• Added a secondary Quantamental diagnostic only; no trading/order execution, strategy entry/exit, provider selection, .env, secrets, or composite weighting was changed.
• used_in_composite_score=false is explicit for the new algorithm.

Data Consistency

• Added volatility_adjusted_breakout_v1 under quant.metrics.algorithms.volatility_adjusted_breakout.
• The algorithm carries required/available observations, prior-high window, component scores, inputs, warnings, and score direction.

UI/UX

• Quantamental overview and score summary now show VAB Score and VAB Class next to QAM.
• Korean/English labels and a clear not-in-composite note were added.

Visualization

• Overview KPI surface now exposes the new diagnostic in the same aligned metric grid and summary style as existing Quantamental metrics.

AI Briefing

• Quantamental AI context now includes quant_snapshot.volatility_adjusted_breakout and quant_snapshot.algorithms.
• Deterministic fallback adds secondary_quant_algorithm to key changes without letting AI override deterministic signals.

Translation

• Korean and English UI module contracts passed; tickers, numbers, dates, and units remain untouched by translation logic.

Performance

• No new provider call, background polling, or LLM call was added. VAB reuses the existing loaded price/volume vectors.

Tests / Validation

• Targeted Python, JS, UI contract, Browser desktop/mobile, and Quantamental Playwright smoke checks passed.

3. Changed Files

File	Change	Reason
pipelines/quantamental/quant_engine.py	Added volatility_adjusted_breakout_v1 and component exposure	Add auditable QUANT diagnostic without changing composite scoring
pipelines/quantamental/ai_service.py	Added VAB to AI context/key changes	Keep AI briefing grounded in deterministic data
pipelines/quantamental/service.py	Added capability marker	Surface supported algorithm capability
app/web/modules/quantamental-ui.js	Added VAB labels, metrics, and summary	Make the diagnostic visible and understandable
scripts/check_ui_contract.py	Added VAB markers	Prevent static UI regressions
tests/test_quantamental_engines.py	Added engine/context assertions	Verify algorithm data and AI guard behavior
tests/test_quantamental_api.py	Added API shape assertions	Verify API exposes VAB safely
tests/test_ui_modules.py	Added module render assertions	Verify UI renders VAB in EN/KO flows
tests/test_ui_routing_contract.py	Added static contract markers	Verify bundled UI contract
docs/CONTINUOUS_ENHANCEMENT_LOG.md	Added 14:03 run report	Document scope, validation, and safety notes

4. Validation Results

Check	Command / Tool	Result	Notes
Lint/static	git diff --check	Passed	Windows line-ending warnings only; no whitespace errors
Build	node --check app/web/modules/quantamental-ui.js; node --check app/web/app.js	Passed	Repo has no frontend package build manifest
Test	python -m pytest tests/test_quantamental_engines.py tests/test_quantamental_api.py tests/test_ui_modules.py tests/test_ui_routing_contract.py -q	Passed	80 passed, 4 subtests passed
UI validation	Browser at http://127.0.0.1:8407/ui/?range=1Y#quantamental	Passed	Desktop/mobile, All view, quality badge, QAM/VAB, no console errors, no horizontal overflow
Data validation	python scripts/check_ui_contract.py and Quantamental API/UI smoke	Passed	VAB markers and data shape validated
AI briefing validation	Quantamental engine/API tests	Passed	Secondary algorithm appears in AI context; signal preserved
Browser smoke	python scripts/quantamental_ui_smoke.py --base-url http://127.0.0.1:8407 --output reports/quantamental_ui_smoke_continuous_20260519_1403.json	Passed	Required tickers, invalid ticker, styles, GLOBAL resolver, Top 5, score screen, overview axes, Q&A, audit smoke

5. Remaining Risks

• volatility_adjusted_breakout_v1 is diagnostic only. Promoting it to screening filters or composite scoring should require a separate approval and validation pass.
• Full repo pytest was not rerun in this stacked slice; targeted Quantamental/API/UI tests and smoke were run.

6. Next Enhancement Suggestions

1. Add VAB as an optional score-screen filter only if the user wants secondary diagnostics to become searchable.
2. Add a compact algorithm-method tooltip with component weights and observation requirements.
3. Extend AI briefing copy to compare QAM vs VAB when both disagree, while keeping deterministic signal unchanged.

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.