Bug
The Telos dashboard always displays Sample User and Mon · 1 Jan in the owner/date header, regardless of who the user is or what day it is.
Root cause
handleTelosOverview in observability.ts hardcodes owner: null in its response:
return Response.json({
owner: null,
// ...
})
Since use-telos-data.ts (when working correctly) skips null fields and keeps the fallback, the dashboard renders the fixture's { name: 'Sample User', day: 'Mon · 1 Jan', streak: 7 } on every load.
Impact
Every user on every day sees the wrong name and a hardcoded date. Low severity but immediately visible and erodes trust in the dashboard.
Fix
Compute and return a real owner object from the API:
const now = new Date()
const owner = {
name: "Damien", // or read from settings/principal config
day: `${now.toLocaleDateString('en-US', { weekday: 'short' })} · ${now.toLocaleDateString('en-US', { day: 'numeric', month: 'short' })}`,
streak: 0,
}
Name should ideally be read from settings.json (principal.name) rather than hardcoded.
Bug
The Telos dashboard always displays
Sample UserandMon · 1 Janin the owner/date header, regardless of who the user is or what day it is.Root cause
handleTelosOverviewinobservability.tshardcodesowner: nullin its response:Since
use-telos-data.ts(when working correctly) skips null fields and keeps the fallback, the dashboard renders the fixture's{ name: 'Sample User', day: 'Mon · 1 Jan', streak: 7 }on every load.Impact
Every user on every day sees the wrong name and a hardcoded date. Low severity but immediately visible and erodes trust in the dashboard.
Fix
Compute and return a real owner object from the API:
Name should ideally be read from
settings.json(principal.name) rather than hardcoded.