Bug
After running /interview and populating the TELOS files, the Telos dashboard (/telos) always displays the sample fixture data instead of the user's real content.
Root cause
Pulse/Observability/src/app/telos/_v7/use-telos-data.ts unconditionally returns the FALLBACK sample constant and never calls the API:
void version;
return { telos: FALLBACK, refetch, error: null };
The version state and refetch callback exist but are unused. /api/telos/overview is never called. Real TELOS data is completely inaccessible from the dashboard regardless of what the interview populated.
Impact
Affects any user who completes /interview and opens the dashboard — the intended first-run flow. The dashboard silently shows placeholder content with no error.
Fix
Replace the stub with a useEffect that fetches /api/telos/overview on mount and merges the real data over the fallback (using typed field mapping to satisfy required interface fields like horizon, blocks, overcomes).
Bug
After running
/interviewand populating the TELOS files, the Telos dashboard (/telos) always displays the sample fixture data instead of the user's real content.Root cause
Pulse/Observability/src/app/telos/_v7/use-telos-data.tsunconditionally returns theFALLBACKsample constant and never calls the API:The
versionstate andrefetchcallback exist but are unused./api/telos/overviewis never called. Real TELOS data is completely inaccessible from the dashboard regardless of what the interview populated.Impact
Affects any user who completes
/interviewand opens the dashboard — the intended first-run flow. The dashboard silently shows placeholder content with no error.Fix
Replace the stub with a
useEffectthat fetches/api/telos/overviewon mount and merges the real data over the fallback (using typed field mapping to satisfy required interface fields likehorizon,blocks,overcomes).