understand-this-codebase.txt
I have this project and I don't know my way around it: <paste the file
list, then the entry point>

Give me a map, in this order:
1. What happens when a request arrives, step by step, file by file.
2. Where state lives — database, memory, browser, files.
3. The three or four files that matter most, and what each is for.
4. Anything here that looks unfinished, unused, or duplicated.

Plain English. I'll ask about specific files after.

Most vibe-coded projects stall the day the author stops knowing where anything is. Rebuilding the map is a fifteen-minute job you can do any time.