blog(why-switch-to-pulumi): refresh AI section for Pulumi Neo

[joeduffy]

What changed

Refreshes content/blog/why-switch-to-pulumi/index.md to remove retired Pulumi Copilot product references (Copilot has been replaced by Pulumi Neo) and rewrite the AI-assistance passages around Neo's actual agentic workflow.

Specifically:

• Removed the top-of-post "this post discusses Pulumi Copilot" caveat note — no longer needed once the body itself is accurate.
• Rewrote the "Increased Productivity" bullet under "Why Pulumi vs. Terraform?" to describe Pulumi Neo (proposes changes, runs previews, responds to failures, opens pull requests, grounded in the real state of your infrastructure in Pulumi Cloud) instead of the retired Copilot product.
• Rewrote the "AI-Powered" paragraph to describe Neo's agentic capabilities instead of a dated "familiar GPT experience" framing.
• Modernized generic "AI copilots" references to "AI coding agents" in three other spots, since Copilot is a specific (retired) Pulumi product name and "AI copilots" reads as a reference to it.
• Reinforced the core positioning angle: because Pulumi infrastructure is defined in real general-purpose languages (Python, TypeScript, Go, C#, Java) rather than a proprietary DSL, AI agents can read, reason about, test, and ship it the same way they already handle the rest of a codebase — this is presented as a fair comparison (Terraform's HCL is described as "harder for agents to reason about reliably," not "lacks testing," since terraform test has existed since Terraform 1.6).
• Marked the post updated: 2026-07-05 per the existing site convention (original date frontmatter preserved; updated field added, matching precedent in other refreshed posts such as content/blog/drift-detection/index.md).
• Lightly refreshed meta_desc to mention Pulumi Neo instead of generic "AI."

Why

Part of an ongoing SEO/AEO content-freshness pass: this post is a bottom-of-funnel comparison piece that AI answer engines and search crawlers actively cite when users ask about switching from Terraform. Leaving a retired product name (Pulumi Copilot) in a heavily-trafficked comparison post erodes both user trust and LLM citation accuracy. Rewriting the AI section around Neo's real, current capabilities keeps the post's strongest argument — "Pulumi speaks real code, which is exactly what makes it AI-agent-ready" — accurate and current for 2026.

Notes for reviewers

• Byline is unchanged (aaron-kao) — no pulumi-content-team (or similar) author key exists in data/team/team/, and inventing one would break the Hugo author lookup, so the original author was kept rather than substituting an unverified byline.
• No new numeric proof points were added to this post; the existing claims were left as-is except for the Copilot/Neo swap, to minimize fact-check surface area.
• Terraform testing comparison was deliberately kept fair — the old copy implied Terraform lacks testing tooling, which is no longer true (terraform test / .tftest.hcl since Terraform 1.6). The new copy frames the gap as HCL being harder for AI agents to reason about, not an testing-capability gap.

---

🧠 This PR was created by workprentice on behalf of @joeduffy.

[github-actions]

Pre-merge Review — Last updated 2026-07-05T13:54:41Z

Tip

Summary: This PR refreshes the AI-related sections of the "Why Switch to Pulumi" blog post to lead with Pulumi Neo instead of the older Pulumi Copilot references — it rewrites the "AI-Powered" and "Increased Productivity" passages, adds an updated: 2026-07-05 frontmatter field, updates meta_desc, and removes the now-obsolete Copilot→Neo transition note. Both issues flagged in the previous pass are fixed: the inaccurate "proprietary" label on HCL is gone, and the overstated "the gap that leads teams to switch" framing is softened to "one more reason teams switch," matching the suggested rewrites. The wordy "on the other hand" was also tightened to "by contrast." Fact-check verification, a frontmatter sweep, a temporal-trigger sweep, an editorial-balance pass, and style linting all ran.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH	Both previously-flagged issues (proprietary HCL, overstated framing) resolved in commit 9de00be; no new factual errors introduced. Pre-existing vague/unverified claims on untouched lines remain, noted below.
coherence	MEDIUM	The rewritten Neo description still repeats an earlier passage nearly verbatim (unchanged from previous pass).

Investigation log

• Cross-sibling reads: not run (not in a templated section)
• External claim verification: 36 of 51 claims verified (3 unverifiable, 5 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 32 Pass 1, 0 Pass 2, 19 Pass 3 (verified 14, contradicted 3, unverifiable 2). Not re-run from scratch — the fix-response only touched the two flagged sentences plus one style tightening; re-verified those against the new diff (below).
• Cited-claim spot-checks: not run (no cited claims)
• Frontmatter sweep: ran on body + meta_desc + social.{linkedin, twitter}
• Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
• Code execution: not run (no static/programs/ change)
• Code-examples checks: not run (no fenced code blocks in content files)
• Editorial-balance pass: ran (single-subject, N/A)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	3	3	2

🔍 Verification trail

52 claims extracted · 36 verified · 3 unverifiable · 5 contradicted

• L4 in content/blog/why-switch-to-pulumi/index.md "updated: 2026-07-05" → ➖ not-a-claim (evidence: This is a front-matter metadata field (updated: 2026-07-05) recording the last edit date of the blog post, not a falsifiable factual assertion that can be externally verified.; source: content/blog/why-switch-to-pulumi/index.md)
• L4 in content/blog/why-switch-to-pulumi/index.md "This blog post was last updated on 2026-07-05." → ✅ verified (evidence: Frontmatter of content/blog/why-switch-to-pulumi/index.md contains updated: 2026-07-05, matching the claim exactly (a future date, but it is the value actually present in the file's metadata).; source: repo:content/blog/why-switch-to-pulumi/index.md; intuition: The 2026-07-05 date is in the future relative to typical PR review time, which is unusual but reflects the literal fron…)
• L5 in content/blog/why-switch-to-pulumi/index.md "Pulumi Neo can be used to automate infrastructure management with AI." → ✅ verified (evidence: The same blog post describes Pulumi Neo as "an agentic infrastructure engineer that understands the real state of your cloud environments... Neo runs multi-step tasks, generates previews for approval, and opens pull requests for the change…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L39-40 in content/blog/why-switch-to-pulumi/index.md "Pulumi gives 10x better scale, productivity, and time to value for thousands of companies worldwide." → ✅ verified (evidence: The live Pulumi blog post "Why Switch to Pulumi for Infrastructure as Code?" states verbatim: "Enter Pulumi – the open source infrastructure as code (IaC) platform that gives 10x better scale, productivity, and time to value for thousands…; source: https://www.pulumi.com/blog/why-switch-to-pulumi/)
• L39-40 in content/blog/why-switch-to-pulumi/index.md "Pulumi is an open source infrastructure as code (IaC) platform." → ✅ verified (evidence: Pulumi's own homepage states: "Pulumi is an open-source infrastructure as code platform that helps humans and agents build and manage cloud infrastructure with real programming languages." The same blog post itself also states Pulumi is "a…; source: https://www.pulumi.com/)
• L48-49 in content/blog/why-switch-to-pulumi/index.md "Pulumi is an infrastructure as code platform that allows you to manage infrastructure, configurations, policies, and secrets with programming languages." → ✅ verified (evidence: This is a standard description of Pulumi's platform consistent with Pulumi's own marketing/docs, which describe Pulumi as an IaC platform supporting infrastructure, config, policy-as-code (CrossGuard), and secrets management using general-…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L55-56 in content/blog/why-switch-to-pulumi/index.md "Pulumi takes a 10x better approach to infrastructure as code compared to alternatives." → ✅ verified (evidence: The official Pulumi blog post itself states: "Pulumi takes a unique and 10x better approach to infrastructure as code by empowering you with the familiar languages and tools you love for application development." This is the source content…; source: https://www.pulumi.com/blog/why-switch-to-pulumi/)
• L58-59 in content/blog/why-switch-to-pulumi/index.md "Modern programming languages have evolved to provide AI coding agents, Intellisense, linting tools, testing frameworks, and CICD pipelines." → ➖ not-a-claim (evidence: This is a general framing/opinion statement about the broader software ecosystem (IDEs, linting, CI/CD, AI tooling), not a specific, falsifiable factual assertion about Pulumi's product or a third-party's claim that can be checked against…; source: content/blog/why-switch-to-pulumi/index.md)
• L68-70 in content/blog/why-switch-to-pulumi/index.md "Pulumi Neo is an AI agent technology built into the core Pulumi user experience." → ✅ verified (evidence: The same blog post describes Neo consistently: "Pulumi builds AI into the core infrastructure management experience through Pulumi Neo, an agentic infrastructure engineer that understands the real state of your cloud environments and works…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L86-92 in content/blog/why-switch-to-pulumi/index.md "Pulumi Neo is an agentic infrastructure engineer that understands the real state of a user's cloud environments and works inside their existing workflows." → ➖ not-a-claim (evidence: This is Pulumi's own first-party marketing description of its own product, Pulumi Neo ("an agentic infrastructure engineer that understands the real state of your cloud environments and works inside your existing workflows"), repeated cons…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L96-97 in content/blog/why-switch-to-pulumi/index.md "Pulumi is trusted/adopted by hundreds of thousands of developers." → ✅ verified (evidence: The source page itself states: "there are some compelling reasons to adopt the platform trusted by hundreds of thousands of developers," and Pulumi's own PR release confirms "It's used by over 3,000 innovative companies and hundreds of tho…; source: https://www.pulumi.com/blog/why-switch-to-pulumi/)
• L110-114 in content/blog/why-switch-to-pulumi/index.md "Terraform altered its licensing and introduced uncertainty, and Terraform is no longer true open source and ties its previously open source software to its com…" → ✅ verified (evidence: Multiple sources confirm: "The license change means Terraform is no longer open source," and BUSL "blocks hosting or embedding Terraform in a cloud service that competes with HashiCorp's own Terraform Cloud or Enterprise offerings," which…; source: https://spacelift.io/blog/terraform-license-change)
• L120-122 in content/blog/why-switch-to-pulumi/index.md "Users expect their infrastructure tools and workflows to keep up with the industry, including AI coding agents, Intellisense, linting tools, testing frameworks…" → ➖ not-a-claim (evidence: This is a general opinion/expectation statement about industry trends, not a falsifiable factual assertion about Pulumi's product or a third party's specific claim that can be verified against a source.; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L142 in content/blog/why-switch-to-pulumi/index.md "Customers of Pulumi frequently experience 100% productivity increases, 99% time saved, and 10x acceleration when using Pulumi compared to what they were using…" → ✅ verified (evidence: The live Pulumi blog page contains this exact sentence verbatim: "Customers of Pulumi frequently experience 100% productivity increases, 99% time saved, and 10x acceleration when using Pulumi compared to what they were using before."; source: https://www.pulumi.com/blog/why-switch-to-pulumi/; intuition: Figures are unsourced marketing aggregates (no linked case-study citation), but they match the published page text exac…)
• L215-222 in content/blog/why-switch-to-pulumi/index.md "Pulumi allows you to use standard programming languages, including YAML, to manage cloud infrastructure." → ❌ contradicted (framing: shifted — claim conflates "standard programming languages" with YAML, a declarative config format that the same post elsewhere (L327-333) explicitly treats as…; evidence: The claimed line (L215-217) says Pulumi's advantage is "its ability to use standard programming languages, including YAML," but YAML is a data/config format, not a programming language — and the same blog post later (L327-333) explicitly s…; source: repo:content/blog/why-switch-to-pulumi/index.md; intuition: Calling YAML a "standard programming language" is a category error — YAML lacks loops, conditionals-as-code, and functi…)
• L219-220 in content/blog/why-switch-to-pulumi/index.md "Pulumi Automation API makes it possible to code a custom user interface for a developer portal or CLI." → ✅ verified (evidence: The source text itself states: "Pulumi Automation API makes it simple to code any user interface for a developer portal / CLI." This is a faithful paraphrase of the actual file content, and aligns with Pulumi's documented Automation API us…; source: repo:content/blog/why-switch-to-pulumi/index.md L219-222)
• L221-222 in content/blog/why-switch-to-pulumi/index.md "Pulumi provides private templates that integrate with developer portals like AWS Proton and Backstage." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L224-226 in content/blog/why-switch-to-pulumi/index.md "Pulumi Automation API can embed IaC programs directly in applications, resulting in 10x greater management of resources per engineer." → ❌ contradicted (framing: shifted — source's "10x faster time to market" claims refer to deployment speed, not "resources managed per engineer," which is a fabricated/unsupported metric; evidence: Pulumi's own materials confirm Automation API lets you embed Pulumi programs directly in applications, but no source ties this to a "10x greater management of resources per engineer" metric. The only "10x" figures found in Pulumi marketing…; source: WebSearch ran query "Pulumi Automation API 10x resources per engineer" and "Pulumi Automation API embed IaC programs directly in applications"; intuition: The specific "10x greater management of resources per engineer" figure looks like an invented precise metric not tracea…)
• L226-228 in content/blog/why-switch-to-pulumi/index.md "Pulumi can take advantage of all existing testing frameworks supported by the selected programming language." → ✅ verified (evidence: The blog itself, consistent throughout, states Pulumi programs are written in general-purpose languages (Python, TypeScript, Go, C#, Java) giving access to "testing frameworks" and that "Pulumi's deep integration between language and runti…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L230-232 in content/blog/why-switch-to-pulumi/index.md "Pulumi Insights adds advanced search, analytics, and AI to any cloud infrastructure." → ✅ verified (evidence: Pulumi's own pricing/docs page confirms Insights includes Resource search, Property search, and Policy analytics under an "Insights & Governance" table, consistent with the blog's description of "advanced search, analytics, and AI" — this…; source: repo:content/pricing/_index.md (Insights & Governance table: Resource search, Property search, Policy Enforcement))
• L232-234 in content/blog/why-switch-to-pulumi/index.md "Pulumi partners with leading observability solutions to manage monitoring and logging resources through IaC." → 🤷 unverifiable (evidence: The claim is a general marketing statement about Pulumi partnering with observability vendors; Pulumi does maintain providers for Datadog, New Relic, Grafana, etc., but there's no specific authoritative source enumerating a formal "partner…; source: repo:content/blog/why-switch-to-pulumi/index.md; intuition: Vague marketing claim ("partners with leading observability solutions") without naming specific partners, hard to falsi…)
• L236 in content/blog/why-switch-to-pulumi/index.md "Pulumi CrossGuard provides policy as code with auto-remediation." → ✅ verified (evidence: Pulumi's pricing page lists Policy as Code (CrossGuard) "Enforcement Modes" as including "Advisory, Mandatory & Remediation" for higher tiers, confirming CrossGuard supports policy as code with an auto-remediation enforcement mode.; source: repo:content/pricing/_index.md (Enforcement Modes: Advisory, Mandatory & Remediation))
• L237-238 in content/blog/why-switch-to-pulumi/index.md "Pulumi ESC makes it easy to manage secrets and configurations for every environment." → ✅ verified (evidence: Pulumi's own repo description for pulumi/esc states: "Pulumi ESC is a centralized, secure service for environments, secrets, and configuration management, optimized for multi-cloud infrastructures and applications," directly confirming ESC…; source: gh search repos --owner pulumi esc)
• L238-239 in content/blog/why-switch-to-pulumi/index.md "Access to each cloud resource and secret in Pulumi can be granularly controlled and audited." → ✅ verified (evidence: Pulumi pricing page lists "Role-based access control (RBAC)", "Custom Roles", "Tag-based access control", and "Audit Logs" as features across Team/Enterprise/Business Critical tiers, confirming granular access control and auditing capabili…; source: repo:content/pricing/_index.md (RBAC, Audit Logs, Tag-based access control sections))
• L241-243 in content/blog/why-switch-to-pulumi/index.md "Pulumi supports modern cloud architectures such as Kubernetes, containers, serverless, generative AI, machine learning, data lakes, and hybrid cloud/on-premise…" → ✅ verified (evidence: Pulumi's provider ecosystem and documentation cover Kubernetes, Docker/containers, serverless (AWS Lambda, Azure Functions, Google Cloud Functions), AI/ML services (SageMaker, Azure OpenAI, Bedrock), data lake services (S3, Azure Data Lake…; source: General knowledge of Pulumi's provider registry (pulumi/pulumi, registry.pulumi.com) covering Kubernetes, AWS/Azure/GCP serverless, VMware/OpenStack providers, and AI/ML integrations.)
• L243-245 in content/blog/why-switch-to-pulumi/index.md "Pulumi makes it simple to create components that abstract away the complexity of managing thousands of resources across hundreds of distinct clouds." → ✅ verified (evidence: The exact sentence appears verbatim on the live Pulumi blog page: "Pulumi makes it simple to create components that abstract away the complexity of managing thousands of resources across hundreds of distinct clouds." This is marketing lang…; source: https://www.pulumi.com/blog/why-switch-to-pulumi/; intuition: Numerically odd — Pulumi's registry has 150-300+ providers (SaaS + cloud), but "hundreds of distinct clouds" overstates…)
• L267-270 in content/blog/why-switch-to-pulumi/index.md "Pulumi provides an abstraction across the different layers of the AI stack as a simple Python library." → ➖ not-a-claim (evidence: The claim is a verbatim paraphrase of the blog's own text: "Pulumi provides an abstraction across all the different layers of the AI stack (web framework, LLM, containers, databases, secrets, policies, configurations, etc) as a simple Pyth…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L294-295 in content/blog/why-switch-to-pulumi/index.md "Cloud or devops subreddits, Slack groups, or Discord servers commonly discuss that manual infrastructure provisioning via cloud console is a bad idea." → 🤷 unverifiable (evidence: This is a vague generalization about sentiment in unspecified online communities (subreddits, Slack groups, Discord servers) with no specific source cited. It reflects commonly-known DevOps best practice sentiment (avoiding manual console…; source: WebSearch not run; claim is a general attribution to informal online community discussion with no specific, checkable source; intuition: Claim is an unfalsifiable generalization about "common" opinions in unnamed online communities—more of a rhetorical fra…)
• L303-306 in content/blog/why-switch-to-pulumi/index.md "Both Pulumi and Terraform include the ability to create, deploy, and manage infrastructure as code on any cloud." → ➖ not-a-claim (evidence: This is a general, non-falsifiable comparative statement about both tools' broad capability (IaC on any cloud), typical of blog framing rather than a specific checkable fact about either product's feature set, version, or limit.; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L303-311 in content/blog/why-switch-to-pulumi/index.md "Both Pulumi and Terraform support many cloud providers, including AWS, Azure, and Google Cloud, plus other services like CloudFlare and Digital Ocean." → ✅ verified (evidence: Pulumi's registry lists official providers for AWS, Azure, Google Cloud, Cloudflare, and DigitalOcean, and Terraform likewise maintains providers for all of these same clouds/services on its registry — matching the general claim that both…; source: https://www.pulumi.com/registry/ (providers: aws, azure-native, gcp, cloudflare, digitalocean))
• L317-320 in content/blog/why-switch-to-pulumi/index.md "When writing Pulumi code, users have access to AI coding agents that can pair program with them." → ➖ not-a-claim (evidence: This is a general marketing statement about AI coding agents pair-programming with users writing Pulumi code — not a specific, falsifiable feature/version claim requiring a source citation; it reflects broadly available industry tooling (C…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L320-327 in content/blog/why-switch-to-pulumi/index.md "Pulumi Neo is an agentic infrastructure engineer that works inside a user's existing workflow: it proposes changes, runs previews, responds to failures, and op…" → 🤝 matches (evidence: The same blog post earlier describes Pulumi Neo identically: "an agentic infrastructure engineer that understands the real state of your cloud environments and works inside your existing workflows. Neo runs multi-step tasks, generates prev…; source: repo:content/blog/why-switch-to-pulumi/index.md (lines 86-92 and 320-327))
• L327-333 in content/blog/why-switch-to-pulumi/index.md "Because Pulumi infrastructure is defined in general-purpose programming languages rather than a bespoke configuration language, Neo can read, reason about, tes…" → ✅ verified (evidence: Pulumi's own reporting confirms this framing: general-purpose languages let Neo work like existing coding agents. The New Stack notes "This is where Pulumi's bet on using general-purpose programming languages is paying off," and a DZone pi…; source: https://thenewstack.io/pulumi-infrastructure-agent-era/; intuition: This is a soft, interpretive marketing claim (not a specific measurable fact) — hard to falsify definitively, but consi…)
• L328-330 in content/blog/why-switch-to-pulumi/index.md "Pulumi Neo can read, reason about, test, and ship Pulumi infrastructure code the same way an AI coding agent handles the rest of a codebase." → ✅ verified (evidence: The claim is a direct paraphrase of the source document itself: "Neo can read, reason about, test, and ship it the same way an AI coding agent already handles the rest of your codebase," describing Pulumi's own product Neo, consistent with…; source: repo:content/blog/why-switch-to-pulumi/index.md)
• L330-333 in content/blog/why-switch-to-pulumi/index.md "Terraform is defined in HCL, a proprietary domain-specific language." → ❌ contradicted (evidence: HCL (HashiCorp Configuration Language) is an open-source project (hashicorp/hcl on GitHub) licensed under the Mozilla Public License 2.0, not a proprietary language. While Terraform itself changed to the Business Source License in 2023, HC…; source: https://github.com/hashicorp/hcl (LICENSE: MPL-2.0); intuition: "Proprietary" is the wrong word for HCL specifically — it's open source (MPL 2.0); the proprietary/BSL confusion applie…) — superseded: commit 9de00be dropped "proprietary"; see ✅ Resolved below.
• L330-333 in content/blog/why-switch-to-pulumi/index.md "The unreliability of AI agents generating and reasoning about HCL compared to general-purpose programming languages is the gap that leads teams to switch from…" → ❌ contradicted (framing: narrowed/shifted — claim elevates one factor (AI-agent HCL reliability) from a benchmark blog post into "the gap" causing all Terraform-to-Pulumi switches; sou…; evidence: Pulumi's own comparison and blog content frame AI-agent reliability with HCL as one benchmark data point among many reasons teams consider switching (licensing changes, IBM acquisition frustrations, lack of general-purpose language feature…; source: https://www.pulumi.com/blog/all-iac-including-terraform-and-hcl/; intuition: Claim uses absolute/singular framing ("the gap") for what sources treat as one of several contributing factors — a comm…) — superseded: commit 9de00be reworded to "one more reason teams switch"; see ✅ Resolved below.
• L0 in content/blog/why-switch-to-pulumi/index.md "Pulumi builds AI into the core infrastructure management experience through Pulumi Neo, an agentic infrastructure engineer that understands the real state of yo" → 🚩 flagged (readthrough: self-redundancy)

📊 Editorial balance

Single-subject post; balance check N/A.

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

No outstanding findings — both previously-flagged issues were fixed in this push.

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

• [L0] content/blog/why-switch-to-pulumi/index.md — the rewritten "AI-Powered" section and the rewritten "Increased Productivity" section (L317-336) both describe Pulumi Neo as an agentic infrastructure engineer that reads the real state of your cloud, runs multi-step tasks, and opens pull requests — in nearly identical language. On a single read-through the second passage lands as a duplicate of the first. Consider trimming or differentiating one of the two Neo descriptions. Non-blocking — the page still reads and reaches its point.

• [L221-222] content/blog/why-switch-to-pulumi/index.md — "Pulumi provides private templates that integrate with developer portals like AWS Proton and Backstage." — 🤷 unverifiable (verification didn't converge). This sentence is on a line this PR doesn't touch, so it isn't a blocker for this change — flagging for future cleanup: if Pulumi still positions Proton/Backstage integration this way, an author could confirm it, otherwise update it.

• [L232-234] content/blog/why-switch-to-pulumi/index.md — "Pulumi partners with leading observability solutions to manage monitoring and logging resources through IaC." — 🤷 unverifiable (vague phrasing, no named partners; Pulumi does maintain Datadog/New Relic/Grafana providers). On a line this PR doesn't touch, so not a blocker.

• [L294-295] content/blog/why-switch-to-pulumi/index.md — "Cloud or devops subreddits, Slack groups, or Discord servers commonly discuss that manual infrastructure provisioning via cloud console is a bad idea." — 🤷 unverifiable (a generalization about sentiment in unnamed communities, no checkable source). On a line this PR doesn't touch.

💡 Pre-existing issues in touched files (optional)

Flagged during verification but on lines this PR doesn't touch — outside this change's scope.

• [L215-222] content/blog/why-switch-to-pulumi/index.md — "Pulumi allows you to use standard programming languages, including YAML, to manage cloud infrastructure." — Pre-existing: flagged as ❌ contradicted because YAML is a declarative config format, not a programming language (the post itself treats YAML as the "if you don't want to program" option elsewhere). Worth a future edit but not part of this PR.

• [L224-226] content/blog/why-switch-to-pulumi/index.md — "Pulumi Automation API can embed IaC programs directly in applications, resulting in 10x greater management of resources per engineer." — Pre-existing: flagged as ❌ contradicted — the "10x greater management of resources per engineer" figure isn't traceable to any Pulumi source (published 10x figures refer to scale and time-to-value, not resources per engineer). Not part of this PR.

• [L396-398] content/blog/why-switch-to-pulumi/index.md — "CDK only permits assertions against synthesized CloudFormation templates and lacks offline testing capabilities." — Pre-existing: flagged as ❌ contradicted — CDK's assertions library tests synthesized templates entirely offline without an AWS account, so "lacks offline testing capabilities" is inaccurate. Not part of this PR.

✅ Resolved since last review

• [L330-333] content/blog/why-switch-to-pulumi/index.md — "Terraform, on the other hand, is defined in HCL, a proprietary domain-specific language…" — dropped "proprietary"; now reads "Terraform, by contrast, is defined in HCL, a domain-specific configuration language…" (resolved in 9de00be).

• [L330-333] content/blog/why-switch-to-pulumi/index.md — "…which is exactly the gap that leads teams to switch." — reworded to "— one more reason teams switch," no longer framing AI-agent reliability with HCL as the singular cause (resolved in 9de00be).

📜 Review history

• 2026-07-05T13:42:30Z — Neo refresh reads clean; flagged one factual error in new content (HCL called "proprietary"), a soft framing overstatement, and mild Neo-description redundancy, plus three pre-existing contradicted claims on untouched lines. (b5f28f4)
• 2026-07-05T13:54:41Z — re-reviewed after fix push (1 new commit, 9de00be): both outstanding findings resolved exactly per the suggested rewrites; "on the other hand" also tightened to "by contrast" per the style note (@joeduffy).

---

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

[pulumi-bot]

Your site preview for commit 9de00be is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-20085-9de00bef.s3-website.us-west-2.amazonaws.com

[joeduffy]

Fixed both outstanding issues: dropped the inaccurate "proprietary" label on HCL (it's MPL-2.0 open source) and softened "the gap that leads teams to switch" to avoid overstating a single factor, per the review's suggested rewrite. Also tightened the wordy "on the other hand" per the style note. @claude #update-review

[github-actions]

🤖 Review updated on @joeduffy's request.