docs(dashboard): stop pinning the false-negative caveat to v0.3.0#825
Closed
ojongerius wants to merge 1 commit into
Closed
docs(dashboard): stop pinning the false-negative caveat to v0.3.0#825ojongerius wants to merge 1 commit into
ojongerius wants to merge 1 commit into
Conversation
The known-issue caution hard-coded "(v0.3.0)", which goes stale as the dashboard ships new releases (currently v0.8.0) and tells a reader nothing about whether the caveat still applies to their build. #719 is still open and is the live source of truth, so reference it for current status instead of pinning a version.
Contributor
Author
|
Superseded by the dashboard content pass: that PR removes the #719 caveat entirely (the false negative was fixed in dashboard v0.4.0 and ar#719 is now closed), rather than just de-pinning it from v0.3.0. |
ojongerius
added a commit
that referenced
this pull request
Jun 13, 2026
…o README (#827) The site dashboard pages described a ~v0.2-0.3 dashboard. Bring them current and adopt a 'README is canonical, site links out' model so they stop re-drifting: - overview: drop the 'early prototype' caution; replace the thin feature list with current capabilities (verification incl. signatures, forensic decryption + auto- load, multi-agent attribution, analytics, JSON export) at overview altitude, each pointing to the dashboard README for full detail. - overview: remove the stale #719 false-negative caveat — fixed in dashboard v0.4.0 (verification recomputes from verbatim receipt_json bytes); ar#719 now closed. - installation: note AR_DASHBOARD_POLL_INTERVAL and add a Forensic decryption section (loopback auto-load from the default key path) linking to the README. Supersedes #825 (which only de-pinned the caveat that is now removed).
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
1 participant
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.
What
The dashboard
overview.mdx"Known issue: false negatives" caution hard-coded(v0.3.0). The shipped dashboard is now v0.8.0, so the pin is stale and tells a reader nothing about whether the caveat applies to their build.Surfaced by the doc-e2e Priya/dashboard persona (#708 harness).
Change
(v0.3.0)version pin; reference #719 (still open) as the live source of truth for current status.The caveat itself stays — #719 is open and the false negative is unconfirmed-fixed on later builds.