Problem (Med — data integrity, perpetually stale)
server/modules/github/service.js:239-249 (getDashboard) — if a GithubData doc exists it's returned unconditionally with no TTL/staleness check; the only refresh path is a manual POST /sync (rate-limited 1/15min). A user who never manually syncs sees GitHub stats frozen at first-fetch forever.
Worse, apexContextCompiler.js:123 feeds this same stale GithubData into the AI system prompt, so APEX reasons on outdated data.
Suggested fix (small)
Compare lastSyncedAt against a max-age (e.g. re-fetch if older than N hours) in getDashboard.
Happy to fix under GSSoC '26 if assigned.
Problem (Med — data integrity, perpetually stale)
server/modules/github/service.js:239-249(getDashboard) — if aGithubDatadoc exists it's returned unconditionally with no TTL/staleness check; the only refresh path is a manualPOST /sync(rate-limited 1/15min). A user who never manually syncs sees GitHub stats frozen at first-fetch forever.Worse,
apexContextCompiler.js:123feeds this same staleGithubDatainto the AI system prompt, so APEX reasons on outdated data.Suggested fix (small)
Compare
lastSyncedAtagainst a max-age (e.g. re-fetch if older than N hours) ingetDashboard.Happy to fix under GSSoC '26 if assigned.