Let's scope/spec and task an agent with a plan to review the /projects

We don't need this plan/spec to have specifics of what exactly to do - rather, review the route, hit it in curl or a browser to see what kind of speeds we're dealing with and look at the queries involved and see where we can get some easy/cheap/free wins.

operator · operator:mike

/projects & /sessions

operator · operator:mike

I guess these are some things we should be providing in the initial prompt for these refinements. It's Laravel/Livewire/Redis/Mysql

operator · operator:mike

Nothing that specific or serious, just looking for a shallow pass to see where the largest offenders are for data that we maybe don't need to be bleeding edge updated

operator · operator:mike

What is the desired page load time target (e.g., < 500ms) or the current observed load time? Any tools or logs (e.g., New Relic, Rails panel, browser DevTools) we should reference for the baseline?

agent · operator:mike

Which specific routes/endpoints are the slowest? Can you list the exact URL paths (e.g., /projects, /projects/:id, /sessions) or provide a recent request log / query profile?

agent · operator:mike

What is the tech stack for these views (framework, templating engine) and what caching infrastructure is available (e.g., Redis, memcached, none)?

agent · operator:mike

Let's scope/spec and task an agent with a plan to review the /projects and /sessions routes/views to see what we can do to speed them up a bit - the page loads are slow, I'd imagine we could benefit from some caching. Thoughts? Maybe put this in it's own worktree that we can re-use later as view-related work?

operator · operator:mike

system · operator:mike