fix(blog): project truthful publication and substantive edit timestamps

This commit is contained in:
Canina Hermes committed 2026-10-30 13:21:07 +00:00
1 parent 00ba4360cf
commit c97ea01ba9
8 files changed
+140 -8

No files matched your search

+24
View File
@@ -0,0 +1,24 @@
# Limited release receipt
Base and observed running production frontend/backend OCI revision: `00ba4360cf7b161995ee94f220b61f9547e01723`, both running, restartCount 0. Official main matches. Mixed develop `216e05ba258cf7882350f00da9d9b659885d9816` is NOT this release.
Only timestamp hunks ported; production imagery unchanged. Existing blogDates helper and BlogPostClient identical across main and mixed develop; no scoped dependency needed. All corporate, SEO-tracking, schema/migration, publisher, analytics, null-image work excluded.
Evidence directory `/opt/data/content-maintenance/recovery-evidence-20261030/`:
- `limited-timestamp-red.log`: initial ported tests fail; 11 failures includes missing fixture ogImageUrl (source main retains imagery fallback). Genuine metadata missing-fallback and clock/timezone failures present. Not all failures behavioral.
- `limited-timestamp-focused.log`: 3 files / 22 tests pass exit0.
- `limited-timestamp-full.log`: 100 files / 518 tests pass exit0, duration279.52 seconds.
- `limited-timestamp-typecheck.log`: typecheck exit0 (dedicated rerun; initial combined command hit external300s deadline after full suite passed).
- `limited-timestamp-lint.log`: scoped ESLint exit0. Full lint not rerun on limited base; prior mixed-branch lib/slug.ts error must not be represented as this artifact's complete lint result.
- `limited-timestamp-build.log`: first build fails because shared node_modules symlink lies outside Turbopack workspace.
- `limited-timestamp-build-localdeps.log`: build exit0 after reflink/copy existing dependencies inside worktree. No source config workaround. Warnings: multiple lockfiles and no local API on127.0.0.1:4400 during prerender. Not live API acceptance.
No backend/admin source changed; no claim their baseline tests certify a new SHA. Official CI rebuild and exact-SHA Stage runtime acceptance remain mandatory.
Existing Stage receipt `stage-216e05ba-release-receipt.json` reviewed: run1355 attests mixed SHA216e05ba and corporate acceptance only; cannot certify limited release. Its 52 Stage articles all have actual contentUpdatedAt later than publication, so an unedited fallback requires a suitable real record or authorized fixture; do not resave records merely to manufacture timestamps.
Release owner must resolve develop ref safely: current develop is mixed and limited branch from main is not a fast-forward. Do NOT merge current develop to main. Do NOT silently force/reset develop. Official workflow triggers only develop/main; parent must choose explicit authorized branch-ref reconciliation preserving mixed work before Stage push. Production promotion only after exact limited SHA Stage CI + container revision + HTTP HTML/JSON-LD/visible dates/noindex/canonical/image + unchanged source dates accepted.
Cause: null contentUpdatedAt correctly means no substantive edit, but renderer omitted modified metadata rather than falling back to real publication; visible formatting used host timezone; unknown publication schema fallback invented render-clock date. Technical updatedAt is not contentUpdatedAt. This changes projections only, never business timestamps or data.
Publisher remains untouched and gated until parent confirms production acceptance.
+4
View File
@@ -0,0 +1,4 @@
# Plan
Port only timestamp hunks from 216e05ba onto production main, not entire page from mixed branch. blogDates helper and BlogPostClient are identical across base and mixed source, no dependency port needed.
Graphify navigation graph hash 6a73473cee9e207543fdeeb668bea544f766200a1b16b8a3a9ce18d4e42e51af, bound to older e7ded849f6b1e3bdab2a20d89b3ec7dd0df79cab: stale navigation only. Existing edges show BlogPostPage -> safeLocalDate/safeIso/getBlog and generateMetadata -> getBlog; confirm direct source/tests at base before editing.
+5
View File
@@ -0,0 +1,5 @@
# Limited timestamp rendering release
Base official main and running production: 00ba4360cf7b161995ee94f220b61f9547e01723. Scope only article timestamp projection, tests and specifications. No corporate, SEO tracking, imagery, data/schema/migration, seed, publisher or cron changes.
Acceptance: metadata modified date uses real substantive contentUpdatedAt only when valid and later than publication; otherwise real publication/createdAt. Never invent dates from render clock. Visible update label requires genuine substantive timestamp; Persian dates use Tehran timezone. Preserve all article imagery and canonical behavior. Stage exact limited SHA must pass official CI and live HTML/read-only source-date acceptance before promotion. Parent exclusively owns pushes.
+8
View File
@@ -0,0 +1,8 @@
# Tasks
- [x] Verify official main, deployed production revision and scoped dependencies.
- [ ] Execute newly ported tests RED on production base.
- [ ] Apply only timestamp hunks and update existing assertion.
- [ ] Run focused/full storefront tests, typecheck, build, scoped lint.
- [ ] Commit limited artifact; parent pushes exact SHA to Stage, validates it, then promotes to main.
- [ ] After production accepted, independent publisher may continue.