fix(blog): correction notes carry the real correction date; disclose …

[csupenn]

…editorial dates

Owner decision (2026-09-27): publication dates keep the editorial calendar, but a correction note states when the correction was made. The 8 notes said "Updated June 17, 2026" for corrections made on September 27, 2026 (checkable against the linked design doc, commits and charliesu.com's correction dates).

• updatedAt + in-body notes: June 17, 2026 -> September 27, 2026 (JSON-LD dateModified and sitemap lastmod follow).
• /blog: one line disclosing that publication dates follow the editorial calendar and that engineering dates are in the linked commits and design docs.

What and why

How it was verified

• pnpm type-check and pnpm lint (0 errors)
• pnpm test:ci (tests + coverage thresholds)
• pnpm build, and affected pages checked on a local production build
• Security fixes: a test that fails on the old code for the right reason, and passes now

Public claims (README, pages, blog, images, badges)

• Every feature or number mentioned exists on main and is described at its real scope
• Sample or demo data is labeled as such where people see it
• No absolute security/compliance wording ("secure", "compliant", "sandboxed") without a scope
• Images show nothing the product doesn't do
• The public-claims guard passes (lib/__tests__/public-claims.test.ts)

Privacy and security

• No user content, keys or IPs added to logs
• New outbound requests go through the SSRF guard; new write endpoints check who is asking

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
top-flow	Ready	Preview	Sep 28, 2026 2:01am UTC