Overview: freshness badge — orange past a week, red past two#24
Merged
Conversation
The front page now carries a last-updated badge under the header. The
generated date is baked into the page, but the AGE is computed in the
viewer's browser at view time — a baked-in color would itself go stale.
Within 7 days it reads green ("up to date — last updated N days ago");
past 7 days it turns orange ("the weekly rebuild is overdue"); past 14,
red ("the scheduled rebuild has stopped"). With the weekly cron in
place, orange/red are an ops signal that CI has quietly failed, which
is exactly the dashboard's failure mode to guard against. Icon + words
on every state, never color alone.
Part of #20.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds a client-computed “freshness” badge to the audit dashboard overview header so viewers can immediately see whether the static site content is up to date (green), overdue (orange), or stale (red) based on the baked-in generated date.
Changes:
- Introduces
.freshnessstyling plus warn/critical variants. - Renders a new header badge with
data-generated=...and an inline JS snippet to compute age and set text/state at view time.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+476
to
+488
| var gen = new Date(el.dataset.generated + 'T00:00:00Z'); | ||
| var days = Math.floor((Date.now() - gen.getTime()) / 86400000); | ||
| if (isNaN(days)) return; | ||
| var age = days <= 0 ? 'today' : days === 1 ? 'yesterday' : days + ' days ago'; | ||
| if (days > 14) {{ | ||
| el.classList.add('crit'); | ||
| el.textContent = '✗ stale — last updated ' + age + ' (' + el.dataset.generated + '); the scheduled rebuild has stopped'; | ||
| }} else if (days > 7) {{ | ||
| el.classList.add('warn'); | ||
| el.textContent = '⚠ last updated ' + age + ' (' + el.dataset.generated + ') — the weekly rebuild is overdue'; | ||
| }} else {{ | ||
| el.textContent = '● up to date — last updated ' + age + ' (' + el.dataset.generated + ')'; | ||
| }} |
Contributor
Author
There was a problem hiding this comment.
Addressed in follow-up PR #25 — as a documented push-back rather than the suggested change. The run stamp is date-only (midnight UTC) and the weekly cron fires Mondays at 05:17 UTC, so comparing raw milliseconds against the 7-day threshold would flip the badge orange every Monday between 00:00 and the cron completing — a built-in weekly false alarm. Flooring to full calendar days is deliberate: orange means a full scheduled run has been missed, which is the signal the badge exists to give. The reasoning is now a code comment beside the calculation so it survives future reviews.
mmcky
added a commit
that referenced
this pull request
Jul 17, 2026
…#25) * Freshness badge: say "audit ran", document the floored-day thresholds Every build re-runs the full scan, so the badge date IS the last audit run — the wording now says so ("audit ran / audit up to date — last ran …"), answering the natural reader question of whether the audit itself is automated (it is: weekly cron + on push + on dispatch). Also documents why the age thresholds floor to full calendar days rather than comparing raw milliseconds (Copilot's suggestion on #24): the run stamp is date-only at midnight UTC and the cron fires Mondays 05:17 UTC, so raw-ms "> 7 days" would flip the badge orange every Monday between 00:00 and the cron completing — a weekly false alarm. Floored days means orange = a full scheduled run has been missed. Follow-up to #24. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Derive the repo count in page copy from the audit payload The freshness tooltip and both page ledes hard-coded "8" repos; the count now comes from audit["repos"], so a manifest change to the scanned set cannot silently falsify the copy. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #23, from Matt's review of the live dashboard.
The overview page now shows an up-to-dateness badge under the header. The generated date is baked into the static page, but the age is computed in the viewer's browser at view time — a color baked in at build time would itself go stale, defeating the purpose.
● up to date — last updated today (2026-07-17)⚠ last updated 10 days ago (2026-07-07) — the weekly rebuild is overdue✗ stale — last updated 20 days ago (2026-06-27); the scheduled rebuild has stoppedSince the site rebuilds on every push and weekly on schedule, a badge that has turned orange or red is an operational signal that the Actions workflow has quietly stopped — the exact silent-rot failure mode the dashboard exists to prevent. Every state carries an icon and words, never color alone; with JavaScript disabled the badge degrades to the plain generated date.
All three states verified by rendering the page with backdated
generatedvalues (screenshots reviewed in both the build and this PR's development).🤖 Generated with Claude Code