3.2 KiB
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.