1.6 KiB
1.6 KiB
Truthful article timestamp metadata
Scope and decisions
Bound to base 18094f91a6 (dirty shared develop; unrelated backend/SEO/corporate files parent-owned). Only blog/[slug] page/tests and these specs are owned here. No record, cron, configuration, commit, push or deployment changes.
The Oct29 household-cleaner article has real publishedAt 2026-10-29T07:11:40.925Z and null contentUpdatedAt. Image attachment is not editorial freshness.
Acceptance
- JSON-LD dateModified and OG modifiedTime equal valid substantive contentUpdatedAt, else the real publication timestamp. Generic updatedAt never creates freshness.
- Publication fallback preserves existing valid createdAt compatibility, consistently across metadata and JSON-LD. No render-clock fallback when both are invalid/missing; unknown dates are omitted.
- Visible update remains substantive-only through unchanged validContentUpdatedAt; publication display remains Persian calendar in Asia/Tehran (not daily report's dual timezone header).
- Retain Stage noindex, canonical, author, image and content behavior.
- RED behavior tests then GREEN full frontend unit suite, typecheck, lint and Next build. Local proof is not Stage acceptance or production authorization.
Policy
SEO governance SKILL.md:19-20 and daily-content-publisher:139,145 require truthful complete timestamps without artificial freshness. Daily report dual timestamps apply at line150, not article display. Independent read-only policy review deleg_3a59d15b concurs with publication fallback and flags render-clock fabrication.