Why:
- Final benchmark selected fixed_size with neighbor expansion ±3 as the winning Candidate.
Changes:
- Set neighbor_prev/neighbor_next defaults to 3 in Settings.
- Default Query tab to fixed_size ±3/3 and Benchmarks to single-strategy fixed_size.
Impact:
- API and Dashboard runs use ±3 unless explicitly overridden.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why:
- Compare is the wrong surface for two-stage family selection over the 10-doc set.
Changes:
- Add the Decision Tab; raise GET /experiments default/max so the board can load the grid client-side.
Impact:
- Operators pick fixed_size ±N vs semantic@Boundary from existing Experiments.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why:
- Avoid a forked PDF UI while scoping Word vs PDF workflows.
Changes:
- formatFilter on shared tabs, PDF Workspace accordion tab, word-only defaults elsewhere.
Co-authored-by: Cursor <cursoragent@cursor.com>
Why:
- Swagger UI is not user-friendly for non-technical users
- Need a proper web app for document management, querying, benchmarking, and administration
Changes:
- Babel-in-browser React dashboard with 5 tabs (Home, Documents, Query, Benchmarks, Admin)
- Dark blue theme matching benchmark report pages (#0F1419, #1A2332, #F59E0B)
- Comparison view for strategy analysis across documents
- Expandable experiment details with delete
- Admin panel with collapsible sections (Health, Qdrant, Chunk Preview, Questions, Cost Estimator)
- Document upload, processing, and strategy selection
- Query interface with chunk inspection
Impact:
- Dashboard served at /app/ via FastAPI StaticFiles
- All Swagger functionality available through web UI
