Repository navigation
Render crossing patterns as validated history instead of live advice - #139
Merged
Merged
Conversation
sbc1-code
added a commit
that referenced
this pull request
Oct 22, 2026
Close existing CHANGELOG, ROADMAP and runbook records after PR #139 passed production EN/ES desktop/mobile verification. Documentation CI passed. Three Markdown files only; no new application deployment requested.
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.
A crossing's Sunday pattern appeared under “Today vs. the 30-day pattern” on Wednesday, while lowest_today generated “Right now” prose from 30-day weekday medians. “Last checked” also displayed a retained first-detection timestamp. Reproduced against the served app in EN/ES with isolated synthetic input.
Render typed weekday/hour evidence instead: retain real zero medians, show sample counts and port-local snapshot/generation dates, and keep dated history separate from current lane reports. Missing/invalid/future UTC source times, unsupported types or malformed numerical evidence produce a neutral unavailable interpretation. No detector, feed, threshold or current-wait change.
Validation: fresh npm ci/build PASS; 126/126 unit tests PASS; full npm test PASS with 402 desktop/mobile route navigations plus new EN/ES isolated fixtures covering Sunday-on-Wednesday, another evidenced weekday, zero, invalid/future/missing data, recovery, dark mode and navigation between ports. Existing Compare freshness/recovery, favorites/storage, sharing, feedback, keyboard, language and metadata regressions pass. Frozen-clock fixtures use their own browser contexts to avoid contaminating the existing suite.
The requested audit review is recorded in the existing runbook: 8 moderate package entries across 3 chains; 6 build-only entries absent from rendered browser chunks and 2 React Router entries present with reviewed exploitation preconditions absent. A same-major parser backport 6.1.5 exists but Typography still pins 6.0.10 and npm's advisory range differs from the maintainer's range; keep that untested override separate from this one user-facing correction. No dependency/lockfile, audit exception, credential, access, security-setting, ad or paid-service changes. Original 18 changed paths and other worktrees preserved.
Publication is authorized after CI, using the existing workflow once and then checking the served app. Revert only this PR merge via a normal revert PR and the existing gates; preserve newer collector snapshots. Limited tests do not certify security/accessibility or the statistical accuracy of CBP inputs.