Spaces:
Running
Running
Commit History
-
feat(frontend): two-step blueprint flow
Moves the Next.js sources (lib/, configs, package manifest) from the project root down into frontend/ so the FastAPI app/ tree doesn't collide with the App Router. vercel.json now points at frontend/package.json. UI: / short explainer + entry /blueprint two-step flow step 1 — upload PDF / image → server extracts native text on all pages → page list with stamp + title excerpts. "Сводка по тексту" button calls /uploads/blueprint/{id}/extract-text which LLM-summarises the whole document. step 2 — multi-select pages → "VLM по выбранным (N)" button calls /uploads/blueprint/{id}/extract-sheets which runs the real VLM chain per selected page with sibling text context. lib/api.ts adds typed wrappers for all 5 new endpoints (uploadBlueprint, getBlueprintStatus, getPagePreview, extractProjectText, extractProjectSheets) plus matching request and response types. Page preview rendered inline as a dat…6d57e0d
-
deploy: backend 2026-06-22T05:07:40Z
0c46399
-
Phase 1: scaffold backend (FastAPI + Dockerfile) and frontend (Next.js + Vercel)
- backend/: FastAPI app skeleton with /health endpoint, pydantic-settings config - backend/Dockerfile: Python 3.11 slim, port 7860 for HF Spaces SDK - backend/requirements.txt: pinned deps (fastapi, pydantic, httpx, supabase, docxtpl) - backend/.env.example: env template (no secrets committed) - frontend/: Next.js 14 + Tailwind + TS, vercel.json with build env wiring - .gitignore: covers Python, Node, .env, HF, Vercel artifacts Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>93628d9