The Pulse Observability dashboard has a working backend route for projects (/api/projects returns 200, reading from USER/PROJECTS.md), but there's no corresponding frontend page — visiting /projects in the dashboard returns 404.
Every other dashboard section has both the API route and a page: agents, air, amber, arbol, assets, assistant, books, bunker, business, conduit, content, docs, finances, growth, health, hooks, hypotheses, knowledge, life, local, memory, performance, skills, system, telos, usage, work — projects is the one gap.
Verified independently: app/projects/ doesn't exist under LIFEOS/PULSE/Observability/src/app/, while /api/projects does work and returns real data ({"count":1,"source":"USER/PROJECTS.md",...}).
Minor, not urgent — just flagging so it's tracked. A page.tsx modeled on one of the simpler existing pages (e.g. health or usage) rendering the existing API response would close this.
The Pulse Observability dashboard has a working backend route for projects (
/api/projectsreturns 200, reading fromUSER/PROJECTS.md), but there's no corresponding frontend page — visiting/projectsin the dashboard returns 404.Every other dashboard section has both the API route and a page:
agents,air,amber,arbol,assets,assistant,books,bunker,business,conduit,content,docs,finances,growth,health,hooks,hypotheses,knowledge,life,local,memory,performance,skills,system,telos,usage,work—projectsis the one gap.Verified independently:
app/projects/doesn't exist underLIFEOS/PULSE/Observability/src/app/, while/api/projectsdoes work and returns real data ({"count":1,"source":"USER/PROJECTS.md",...}).Minor, not urgent — just flagging so it's tracked. A
page.tsxmodeled on one of the simpler existing pages (e.g.healthorusage) rendering the existing API response would close this.