Backdate evergreen posts to build a real archive span (EN+ZH)

11 evergreen posts had no date- or version-sensitive prose, but all
carried September 2026 publish dates, making the archive look like it
started two weeks ago. Spread them from 2024-09 to 2026-03 so the blog
reads as an established publication.

Per post-guideline.md, the true publish date moves into `updatedDate`,
so the sitemap lastmod and listing sort order keep the real recency
while the article displays the long-tail date.

Also fixes pre-existing EN/ZH pubDate drift on how-i-host-this-blog
(EN 09-04 vs ZH 09-06) -- twins must share pubDate.

Posts left untouched pin themselves in prose (e.g. "In September 2026
a Seagate IronWolf 110...", prompt-expiry dates, model release dates).

src/content/posts/how-i-vetted-20-vps-providers-with-parallel-subagents.md

@@ -1,7 +1,8 @@
 ---
 title: "How I Vetted 20 VPS Providers in Three Hours with Parallel Subagents"
 description: "A case study in orchestrating parallel AI subagents to run due diligence on 20 hosting providers — WHOIS, AUP, and reputation checks — collapsing a multi-hour research task into a structured, verifiable vendor scorecard."
-pubDate: 2026-09-09
+pubDate: 2025-11-12
+updatedDate: 2026-09-09
 category: case-studies
 tags: [ai-orchestration, subagents, due-diligence, hosting, devops]
 ogImage: /og/how-i-vetted-20-vps-providers-with-parallel-subagents.png