test(ui): qualify denser dashboard discovery and offer date states
This commit is contained in:
@@ -4,4 +4,6 @@
|
||||
|
||||
RED: two western-timezone EN/NB failures, four other timezone cases passed and nine existing cases filtered. GREEN: all15 offer comparison tests passed, including six EN/NB combinations for Los Angeles, Oslo and Kiritimati plus timestamp, missing-value, navigation, salary, retry and read-only behavior. TypeScript and scoped ESLint passed. Independent read-only review found no actionable findings and ran no checks. Public-auth browser evidence predates this unbuilt change and does not qualify it.
|
||||
|
||||
Next: after sealing the public-auth export, build this fix and run affected rendered offer qualification. Rollback reverts the formatter and six added tests; no migration. This does not assert that deployed API records use literal date-only serialization, or resolve the separate original timezone/precision model gaps.
|
||||
Rendered PASSED on settled successora7d72673: six390px journeys/scans/captures, EN/NB across Los Angeles, Oslo and Kiritimati. Chromium timezone contexts preserve the literal application date and decision date while a genuine follow-up timestamp retains its local calendar day. Unknown facts remain visible. Zero browser errors or mutations. Static build passed; the existing secondary-route verifier's opt-in offer-only mode preserves earlier outputs. This is a targeted timezone check, not a new full secondary regression or real backend qualification.
|
||||
|
||||
Rollback reverts the formatter and six added tests; no migration. This does not assert that deployed API records use literal date-only serialization, or resolve the separate original timezone/precision model gaps.
|
||||
|
||||
Reference in New Issue
Block a user