🛠️ Build Log – Session Management Online

This morning’s win was getting session management fully functional: log in, log out, front end and back end finally shaking hands without a hitch. It took longer than I’d hoped, but the real unlock came from a simple shift: opening both repos in the same Cursor window.

I’ve been trying to keep FE and BE work separated for sanity’s sake, but when the coordination is this tight, the context matters more than the purity of the setup. Once both codebases were visible, the LLM could see the whole picture and finally trace down the weirdness: the back end wasn’t setting or sending the session token properly on first login. Until then, I could use the token if I dug it out of the database manually, but the front end never got it to store for future requests.

The bigger takeaway is that VulcanForge’s Anvil might need a similar “cross-codebase context” mode in dev/live environments. Sometimes the problem isn’t in one repo. It’s in the seam between them.

I started the day thinking I’d work on minimalism (ensuring each capability is implemented once and killing off duplicates) but that effort immediately revealed a bigger shift: our planned schemas have evolved so far that the old validation scripts don’t apply anymore. So instead of trimming fat, I’m building version planning to handle evolving schema definitions.