fix(acquisition): require canonical updated_at identity - #485
Conversation
|
Warning Review limit reached
Next review available in: 10 minutes Limit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Purpose
Test-first acquisition evidence-integrity hardening. Buyer-facing
updated_atmetadata currently trims the supplied JSON string before ISO validation, so whitespace-padded timestamps can be normalized into freshness authority rather than rejected as non-canonical evidence.RED
2d8a07df19c5e9aa10887b8140d7768de237bea738f45505d2b901c1a4c13f7a0c28d8638963d6f6" 2026-08-21T12:00:00Z "must fail with the existingupdated_at must be an ISO date or timestampevidence-integrity contract, while canonical date-only and timezone-bearing timestamps remain validKeep Draft until exact-head CI proves the RED and the smallest metadata-boundary repair receives fresh full GREEN evidence.