Linegra

This repo contains everything you need to run Linegra locally or deploy it to Vercel.

Historical note: the very first UI mockups for Linegra were prototyped inside Google AI Studio; this repository now hosts the live codebase.

Agentic dev flow: start with AGENT.md for expectations, then use docs/CONTENT_MAP.md to locate feature-specific files quickly.

Run Locally

Prerequisites: Node.js

AI integration now uses OpenRouter. See docs/AI_SETUP.md for required OPENROUTER_API_KEY instructions before running locally or on CI.

1. Install dependencies: npm install
2. Create .env.local with OPENROUTER_API_KEY, SUPABASE_URL, and SUPABASE_PUBLISHABLE_KEY values (see docs/AI_SETUP.md + docs/SUPABASE_SETUP.md)
3. Run the app: npm run dev

⚠️ Linegra no longer ships with mock archives or an in-app Supabase connection form. You must provide valid SUPABASE_URL and SUPABASE_PUBLISHABLE_KEY values (as described in docs/SUPABASE_SETUP.md) before the UI will load.

DNA Workflows

The DNA workflow (Autosomal + Shared Autosomal imports, lineage resolution, and admin review) is documented in:

• docs/DNA_SETUP.md

This includes supported CSV formats (MyHeritage and FTDNA segment comparison), how shared matches are linked, and how the Administrator DNA panel resolves lineage paths.

Specification & Navigation

• Product/technical specification: SPEC.md
• Agent/developer entrypoint: AGENT.md
• Feature-to-file map: docs/CONTENT_MAP.md
• LLM-optimized knowledge base (architecture, schema, decisions, runbooks): wiki/index.md

Super Administrator Login

Linegra currently ships with a single local super administrator account. Use the header Login button and enter the bootstrap credentials:

Username	Password
linegra	linegra

On the first successful login you must immediately set a new username and password; this prompt cannot be skipped and ensures the archive is secured before edits occur. Updated credentials are stored in the browser/Electron localStorage, so if you clear storage or move to a new machine you will need to repeat the bootstrap process. Multi‑user registration is not yet available—only this super administrator can add, edit, or delete archival data in the current release.

Local development: when the app is served from localhost (or 127.0.0.1/*.local), you can sign in one‑step with admin / admin (the linegra / linegra bootstrap also works) and the forced credential‑reset prompt is skipped. This convenience is gated on the hostname at runtime, so deployments to a real domain are unaffected — there the forced reset still applies and only your stored credentials are accepted.