---
name: project-lemongraphfront-setup
description: How the LemonGraphFront self-target validation environment is wired (project id, live db, port) — needed to independently re-test #/graph and other frontend changes
metadata:
  type: project
---

The graphlemon project being self-developed under target_folder_path
`/Users/yibo/Documents/lemonAI/graphlemon/frontend/` is tracked as project
`LemonGraphFront` (project_id `e713f5a1-3edf-4f1a-a3c9-02745513e3f7`) in a
**separate** sqlite db at `/tmp/graphlemon-visual-check/graphlemon.db` — not
the default `~/.graphlemon/graphlemon.db`. A `backend_server` process is
typically kept running against that db on port 8791 for manual browser
verification (`server.log` in the same dir confirms
"graphlemon backend listening on 127.0.0.1:8791").

**Why:** this setup predates this memory; discovered 2026-08-03 while
validating the `v_graph_console` (#/graph) task (task_id
`7400d876-a797-4d87-bcff-4e59a3befba1`).

**How to apply:**
- The long-running server on 8791 is a snapshot of whatever code existed
  when it was started — it does NOT hot-reload. If you need to test
  against the *current* (possibly uncommitted) working-tree code, start a
  fresh `python3 -m src.backend_server --host 127.0.0.1 --port <free-port>
  --db-path /tmp/graphlemon-visual-check/graphlemon.db` instead of trusting
  curl results from 8791 — a 404 on a route you can see in the diff usually
  just means the long-running process predates that route, not that the
  route is broken. Kill your temp server when done; don't leave stray
  listeners around.
- `sqlite3 /tmp/graphlemon-visual-check/graphlemon.db` is a legitimate way
  to inspect real task/artifact/work_graph_run/work_node_execution state
  for this project when validating — cross-reference with
  `frontend/.graphlemon/runs/<task_id>/` for the actual artifact file
  contents (brd/prd/sdd/benchmark/code_diff/test_report .md/.patch files).