Problem
(a) backend/README.md:32 says “25 tests” but there are 84 test functions across 8 files, and line 30 lists api/v1/ as “health, topics, daily” while the code also ships me.py, concepts.py, pages.py (the endpoint table lower down is accurate — internal inconsistency).
(b) Mobile developer onboarding is essentially absent: mobile/AGENTS.md is 3 lines, mobile/DEPLOYMENT.md covers EAS/OTA but not local dev; there is no “clone → npm install → expo start” path and no mobile architecture/state overview (Context providers, services, mutation queue, offline model) — the most complex part of the codebase.
Impact — Erodes trust in the docs and undercounts coverage; a new dev can stand up the backend but has no on-ramp for the app beyond “read Expo docs.” (docs/ARCHITECTURE.md is a good high-level overview but stops at the boundary.)
Suggested direction — Fix the README numbers/endpoint list; add a short mobile/README.md (local run, env vars, folder map, offline/sync model).
Problem
(a)
backend/README.md:32says “25 tests” but there are 84 test functions across 8 files, and line 30 listsapi/v1/as “health, topics, daily” while the code also shipsme.py,concepts.py,pages.py(the endpoint table lower down is accurate — internal inconsistency).(b) Mobile developer onboarding is essentially absent:
mobile/AGENTS.mdis 3 lines,mobile/DEPLOYMENT.mdcovers EAS/OTA but not local dev; there is no “clone → npm install → expo start” path and no mobile architecture/state overview (Context providers, services, mutation queue, offline model) — the most complex part of the codebase.Impact — Erodes trust in the docs and undercounts coverage; a new dev can stand up the backend but has no on-ramp for the app beyond “read Expo docs.” (
docs/ARCHITECTURE.mdis a good high-level overview but stops at the boundary.)Suggested direction — Fix the README numbers/endpoint list; add a short
mobile/README.md(local run, env vars, folder map, offline/sync model).