content(onboarding): use relative links and fix style-guide violations

[jkodroff]

Fixes #19329.

The Onboarding Guide pages used absolute https://www.pulumi.com/... URLs for links that point back into the same site, violating the AGENTS.md link-style convention.

Changes

• Converted 51 absolute pulumi.com links to site-relative paths across choose-subscription, setting-up-for-success, migrating-to-pulumi, and ways-of-working. External app.pulumi.com links are correctly left absolute.
• Updated 12 stale aliased paths to their canonical form (e.g. /docs/using-pulumi/continuous-delivery/ → /docs/iac/guides/continuous-delivery/); each target was verified to resolve to a real content file.
• Fixed the style-guide violations Vale flags across the guide: difficulty qualifiers ("easy", "simply", "simple", "just"), weasel words, click→select, a missing Oxford comma, an ly-adverb hyphen, and vague [here] link text.

Vale and make lint are both clean on all four files.

[pulumi-bot]

Your site preview for commit e32ea1c is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19331-e32ea1cc.s3-website.us-west-2.amazonaws.com

[github-actions]

Pre-merge Review — Last updated 2026-05-22T03:44:36Z

Tip

Summary: Pure refactor of the four onboarding-guide pages — converts absolute https://www.pulumi.com/... links to site-relative paths, updates a handful of stale aliased paths to their canonical targets, and applies the Vale fixes the commit message advertises (difficulty qualifiers, weasel words, click→select, an Oxford-comma fix, an ly-hyphen fix, vague "[here]" link text). +59/-59 lines means almost every changed line is a like-for-like swap. The wrongness that would block a reader's success here is a broken link target: a wrong relative path or a missing fragment anchor would route readers to a 404 or to the wrong section of a long page. Investigative passes: 73-claim factual verification (with framing analysis), frontmatter/alias sweep across all four files, Hugo-build sweep (skipped — content-only PR), and full review of the URL substitutions in the diff against current canonical paths. Cross-sibling fan-out is moot here — all four "siblings" are part of this PR.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH	Most contradicted-verdict claims are pre-existing wording on lines whose only change is URL/Vale-style — out of scope for this PR.
cross-sibling consistency	HIGH	All 4 onboarding-guide pages co-edited in this PR; no inter-page references to cross-check against untouched neighbors.

Investigation log

• Cross-sibling reads: 3 of 3 siblings — all co-touched by this PR; fan-out is moot
• External claim verification: 61 of 73 claims verified (4 unverifiable, 7 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 60 Pass 1, 3 Pass 2 (verified 2, contradicted 0, unverifiable 1), 10 Pass 3 (verified 8, contradicted 2, unverifiable 0).
• Cited-claim spot-checks: 3 of 3 cited claims fetched and compared
• Frontmatter sweep: ran on body + meta_desc
• 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: not run (not under content/blog/)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
1	4	5	0

🔍 Verification trail

73 claims extracted · 61 verified · 4 unverifiable · 7 contradicted

• L22 in content/docs/administration/onboarding-guide/choose-subscription.md "Pulumi's community has grown to hundreds of thousands of practitioners worldwide." → ✅ verified (framing: strengthened — the claim matches the live docs page verbatim, but the source_hint (/community/) does not contain the figure; a sibling blog post (Dec 2025) cit…; evidence: The live Pulumi docs page at pulumi.com/docs/deployments/get-started/onboarding-guide/choose-subscription/ contains the exact claim: "Pulumi's community has grown to hundreds of thousands of practitioners worldwide." However, the cited sou…; source: https://www.pulumi.com/docs/deployments/get-started/onboarding-guide/choose-subscription/; intuition: The "hundreds of thousands" figure may be inflated relative to the "over 130,000" figure cited in a December 2025 Pulum…)
• L27 in content/docs/administration/onboarding-guide/choose-subscription.md "Individual and Team tiers include access to community support through GitHub Discussions, GitHub Issues, Community Slack, and free workshops." → ✅ verified (evidence: The file at L27 states: "Access community support through GitHub Discussions and Issues, Community Slack, and free works…; source: repo:content/docs/administration/onboarding-guide/choose-subscription.md)
• L29 in content/docs/administration/onboarding-guide/choose-subscription.md "You can also make use of the Pulumi Neo, detailed documentation in the Pulumi Registry, and the [examples repo](https://github.c…" → ✅ verified (evidence: The pre-fetched URL https://github.com/pulumi/examples returns HTTP 200 with content confirming it is the "pulumi/examples" repository: "Infrastructure, containers, and serverless apps to AWS, Azure, GCP, and Kubernetes... all deployed wit…; source: https://github.com/pulumi/examples)
• L43 in content/docs/administration/onboarding-guide/choose-subscription.md "Learn more about the differences between our subscription tiers." → ✅ verified (evidence: The live Pulumi pricing page at pulumi.com/pricing/ exists and covers subscription tiers. The source docs page itself contains "Learn more about the differences between our subscription tiers here," confirming the link and its context.; source: https://www.pulumi.com/pricing/)
• L47 in content/docs/administration/onboarding-guide/choose-subscription.md "For hands-on engineering support, consider Pulumi Professional Services. Our team can help design and implement best practices, build custom providers and comp…" → ✅ verified (framing: strengthened — the claim's specific enumeration (custom providers, migration, standard packages) is a narrower subset of the broader services described on the…; evidence: The URL https://www.pulumi.com/proserv/ is live and hosts the Pulumi Professional Services page. The page confirms "At Pulumi Professional Services, we partner with you to accelerate your cloud transformation journey," and the page offers…; source: https://www.pulumi.com/proserv/)
• L54 in content/docs/administration/onboarding-guide/choose-subscription.md "Pulumi Cloud SaaS is the recommended deployment model for most organizations." → ✅ verified (evidence: The file contains the section heading "### SaaS (Recommended for most organizations)" and states "Choose Pulumi Cloud SaaS if you want the simplest setup with enterprise-grade reliability built in," directly confirming that SaaS is the rec…; source: content/docs/administration/onboarding-guide/choose-subscription.md)
• L56 in content/docs/administration/onboarding-guide/choose-subscription.md "Pulumi Cloud SaaS provides high availability, disaster recovery, and geo-replication out of the box." → ✅ verified (evidence: The file at L56 states: "You get high availability, disaster recovery, and geo-replication out of the box." The referenced Pulumi Cloud Security Whitepaper confirms: services are "distributed across multiple availability zones to ensure hi…; source: repo:content/docs/administration/onboarding-guide/choose-subscription.md and repo:content/security/pulumi-cloud-security-whitepaper.md)
• L61 in content/docs/administration/onboarding-guide/choose-subscription.md "Self-hosted Pulumi Cloud is only available for Business Critical customers." → ✅ verified (evidence: Multiple authoritative pages in pulumi/docs confirm this exactly. For example, content/docs/administration/self-hosting/operations/compute-sizing.md states: "Self-hosting is only available with Pulumi Business Critical." and `content…; source: gh search code --owner pulumi "self-hosted" "Business Critical"; repo:pulumi/docs content/docs/administration/self-hosting/operations/compute-sizing.md and content/product/self-hosted.md)
• L64 in content/docs/administration/onboarding-guide/choose-subscription.md "Self-hosted Pulumi Cloud can be deployed on-premises, in your cloud account, or any infrastructure you control." → ✅ verified (framing: strengthened — claim rephrases "You can deploy anywhere: on-premises, in your cloud account, or any infrastructure you control" as a subject-led sentence; the…; evidence: The file at L64 states: "You can deploy anywhere: on-premises, in your cloud account, or any infrastructure you control." This directly supports the claim that self-hosted Pulumi Cloud can be deployed on-premises, in your cloud account, or…; source: repo:content/docs/administration/onboarding-guide/choose-subscription.md)
• L68 in content/docs/administration/onboarding-guide/choose-subscription.md "To get started with self-hosted Pulumi Cloud, follow the guides to set up your [state backend](/docs/iac/concepts/state-and-backends/#logging-into-the-aws-s3-b…" → ❌ contradicted (evidence: The file content/docs/iac/concepts/state-and-backends.md does not contain a #logging-into-the-aws-s3-backend anchor. The AWS S3 backend content has been moved to a separate page (/docs/iac/guides/basics/using-a-diy-backend/), and the…; source: repo:content/docs/iac/concepts/state-and-backends.md)
• L82 in content/docs/administration/onboarding-guide/choose-subscription.md "Pay upfront with invoicing to access significant cost savings through commitment pricing. This option works well for organizations with predictable usage and e…" → ✅ verified (evidence: The URL /contact/ resolves to a live Pulumi page: "Contact Pulumi for any general inquiries, including requests for pricing, support, or training." The link target is valid and appropriate for the commitment pricing context.; source: https://www.pulumi.com/contact/)
• L85 in content/docs/administration/onboarding-guide/choose-subscription.md "Users receive monthly usage reports via email for both billing options." → ✅ verified (evidence: The file at the relevant section contains: "Both billing options include detailed usage insights through the Billing & usage page... You'll also receive monthly usage reports via email." This directly confirms that monthly usage reports vi…; source: content/docs/administration/onboarding-guide/choose-subscription.md)
• L85 in content/docs/administration/onboarding-guide/choose-subscription.md "The Billing & usage page tracks IaC resources, deployment minutes, ESC secrets, and allows downloading usage history." → ➖ not-a-claim (evidence: The text at L85 of choose-subscription.md is the PR author's own description of the Billing & usage page within their own notes block: "Track IaC resources, deployment minutes, ESC secrets, and download usage history." This is the author d…; source: repo:content/docs/administration/onboarding-guide/choose-subscription.md)
• L98 in content/docs/administration/onboarding-guide/choose-subscription.md "Users can sign up for Pulumi using their email address and password, or connect with their GitHub, GitLab, or Atlassian identity at app.pulumi.com/signup." → 🤷 unverifiable (evidence: The pre-fetched body of https://app.pulumi.com/signup returns HTTP 200 but contains only CSS/font definitions with no readable HTML text confirming the available sign-up options (email/password, GitHub, GitLab, Atlassian). The page is a Ja…; source: https://app.pulumi.com/signup; intuition: The CSS variables do reference --color-identity-github, --color-identity-gitlab, --color-identity-atlassian, and…)
• L102 in content/docs/administration/onboarding-guide/choose-subscription.md "Selecting the sparkle icon in the Pulumi Cloud console accesses Pulumi Neo, described as an AI agent." → ✅ verified (evidence: The file at content/docs/administration/onboarding-guide/choose-subscription.md states: "Use the search function to find specific resources, and select the sparkle icon to access Pulumi Neo, your AI agent." This directly confirms both th…; source: repo:content/docs/administration/onboarding-guide/choose-subscription.md)
• L102 in content/docs/administration/onboarding-guide/choose-subscription.md "The Pulumi Cloud console can be accessed through the 'Sign In' link at pulumi.com or directly at app.pulumi.com/signin." → ✅ verified (evidence: The URL https://app.pulumi.com/signin returns HTTP 200 with a page titled "Pulumi Cloud", confirming that the Pulumi Cloud console is directly accessible at app.pulumi.com/signin. The claim about the 'Sign In' link at pulumi.com is a reaso…; source: https://app.pulumi.com/signin)
• L24 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi's migration tools place existing resource management under Pulumi IaC by swapping out management without disrupting resources, resulting in zero downtim…" → ✅ verified (evidence: The file at L24 states: "These tools generate Pulumi IaC code in your chosen language and actively place existing resource management under Pulumi IaC, swapping out management without disrupting resources for zero downtime." The claim is a…; source: repo:content/docs/administration/onboarding-guide/migrating-to-pulumi.md)
• L24 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi offers tailored migration tools for Terraform, AWS CloudFormation/CDK, Azure ARM, and Kubernetes YAML." → ✅ verified (evidence: The claim text appears verbatim in the file at L24: "Pulumi also offers tailored migration tools for Terraform, AWS CloudFormation/CDK, Azure ARM, and Kubernetes YAML." The migration guide at content/docs/iac/guides/migration/_index.md c…; source: repo:content/docs/administration/onboarding-guide/migrating-to-pulumi.md and repo:content/docs/iac/guides/migration/_index.md)
• L24 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "The Visual Import feature at /docs/insights/discovery/visual-import/ is the recommended approach for importing resources into Pulumi." → ✅ verified (evidence: The migrating-to-pulumi.md file states: "The Visual Import feature is the recommended approach for importing resources." The linked page at that path exists and describes the Visual Import feature…; source: repo:content/docs/administration/onboarding-guide/migrating-to-pulumi.md)
• L26 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi supports deploying Helm charts as-is." → ✅ verified (evidence: The file at L26 explicitly states: "Pulumi supports coexisting with existing ecosystems. You can deploy Helm charts as-is or consume Terraform workspace outputs."; source: repo:content/docs/administration/onboarding-guide/migrating-to-pulumi.md)
• L26 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi supports consuming Terraform workspace outputs." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L32 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "The detailed migration tooling documentation is located at /docs/iac/guides/migration/." → ✅ verified (evidence: The file content/docs/iac/guides/migration/_index.md exists and its content confirms it is the detailed migration tooling documentation, covering importing, conversion, coexistence, and migration from Terraform, CloudFormation, ARM, Kube…; source: repo:content/docs/iac/guides/migration/_index.md)
• L63 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi Cloud IDP (at /product/internal-developer-platforms/) provides user visibility and access to templates and components." → ✅ verified (evidence: The migrating-to-pulumi.md file states "You can use Pulumi Cloud IDP to provide user visibility and access to your templates and components." The product page at /product/internal-developer-platfor…; source: repo:content/docs/administration/onboarding-guide/migrating-to-pulumi.md and repo:content/product/internal-developer-platforms.md)
• L69 in content/docs/administration/onboarding-guide/migrating-to-pulumi.md "Pulumi ESC supports short-lived cloud credentials via OIDC integration." → ✅ verified (framing: strengthened — claim narrows the source's general "dynamic login credentials via OIDC" to "short-lived cloud credentials via OIDC integration"; the source's br…; evidence: The /docs/esc/integrations/dynamic-login-credentials/ page confirms: "Pulumi ESC integrates with the following dynamic login providers to enables you to log in to your account using OpenID Connect (OIDC)..." and the page has an alias `/d…; source: content/docs/esc/integrations/dynamic-login-credentials/_index.md)
• L22 in content/docs/administration/onboarding-guide/setting-up-for-success.md "The infrastructure hosting Pulumi Cloud aligns with IT security standards including SOC 1/SSAE 16/ISAE 3402, SOC 2, SOC 3, FISMA, FedRAMP, DOD SRG Levels 2 and…" → ✅ verified (evidence: (escalated from pass1) The published Pulumi docs page contains the exact sentence: "The infrastructure hosting Pulumi Cloud aligns with IT security standards including SOC 1/SSAE 16/ISAE 3402, SOC 2, SOC 3, FISMA, FedRAMP, DOD SRG Levels 2…; source: https://www.pulumi.com/docs/pulumi-cloud/get-started/onboarding-guide/setting-up-for-success/)
• L24 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi Policies includes out-of-the-box policies spanning CIS, HITRUST, NIST, and PCI DSS compliance frameworks." → ✅ verified (evidence: The /docs/insights/policy/ page states: "You can use pre-built policy packs for common compliance frameworks (CIS, HITRUST, NIST, and PCI DSS)" and the source file itself says "Pulumi Policies includes hundreds of out-of-the-box policies…; source: content/docs/insights/policy/_index.md)
• L26 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi Policies identifies issues in existing cloud infrastructure and prevents new problems from being introduced." → ✅ verified (framing: strengthened — claim narrows the two enforcement modes described in the source into a single summary sentence; the source's broader descriptions prove the clai…; evidence: The /docs/insights/policy/ page describes two enforcement modes: "Audit: Continuously scans resources discovered through Insights Discovery to identify violations across all infrastructure" and "Preventative: Validates Pulumi stack resou…; source: content/docs/insights/policy/_index.md)
• L28 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi Cloud maintains an audit log of every activity and who performed it." → ✅ verified (framing: strengthened — claim narrows 'maintains an audit log of every activity and who performed it for complete visibility' to 'maintains an audit log of every activi…; evidence: The file at line 28 reads: "Pulumi Cloud maintains an audit log of every activity and who performed it for complete visibility." — the claim is a verbatim subset of this sentence (omitting only the trailing "for complete visibility").; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L32 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi supports SaaS infrastructure products including Cloudflare, DataDog, MongoDB, and Snowflake as cloud providers." → ✅ verified (framing: strengthened — claim omits the additional mention of on-premises technologies (VMware vSphere) present in the source, but the SaaS provider list (Cloudflare, D…; evidence: The official Pulumi onboarding docs page states: "Other supported providers include SaaS infrastructure products like Cloudflare, DataDog, MongoDB, and Snowflake, plus on-premises technologies like VMware vSphere."; source: https://www.pulumi.com/docs/pulumi-cloud/get-started/onboarding-guide/setting-up-for-success/)
• L34 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Using Pulumi ESC's OpenID Connect (OIDC) support for dynamic, short-lived credentials is the most secure authentication method and should be preferred for supp…" → ✅ verified (evidence: The source file at the relevant section states: "Use Pulumi ESC's OpenID Connect (OIDC) support for dynamic, short-lived credentials... This is the most secure method and should be preferred for supported providers." The linked page `/docs…; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L36 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Each provider in the Pulumi Registry has an 'Install & config' section with authentication guidance." → ✅ verified (evidence: The Pulumi Registry contains installation-configuration.md files for each provider (e.g., /registry/packages/aws/installation-configuration, /registry/packages/kubernetes/installation-configuration), confirming that providers have an…; source: gh search code --owner pulumi "installation-configuration" --repo pulumi/registry)
• L46 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi provides built-in mocking of cloud capabilities for unit tests." → ✅ verified (evidence: The file at L46 states: "Pulumi provides built-in mocking of cloud capabilities for these tests." (where "these tests" refers to unit tests in context). GitHub search also surfaces Pulumi docs confirming "resource mocking in Pulumi makes t…; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L50 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi integration tests run real deployments with Pulumi to verify that infrastructure is provisioned to specification." → ✅ verified (evidence: The file at content/docs/administration/onboarding-guide/setting-up-for-success.md contains the exact text: "Integration tests run real deployments with Pulumi to verify that infrastructure is provisioned to specification."; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L54 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Fuzz testing can verify that infrastructure configurations react correctly to varying inputs." → ✅ verified (evidence: The file states: "Options include fuzz testing to verify your infrastructure configurations react correctly to varying inputs, or chaos testing that destroys infrastructure components to test system responses." This directly confirms the c…; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L54 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Chaos testing destroys infrastructure components to test system responses." → ✅ verified (evidence: The file contains the exact phrasing: "chaos testing that destroys infrastructure components to test system responses" in the "Consider advanced testing techniques" section.; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L56 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Also consider using linters and static analysis tools to enforce industry standards and your team's coding guidelines. See the [Testing Pulumi programs guide](…" → ✅ verified (evidence: The file content/docs/iac/guides/testing/_index.md exists with title "Testing Pulumi programs" and includes /docs/iac/guides/testing/ as an alias, confirming the URL path is valid and the page title matches the link text used in the cl…; source: repo:content/docs/iac/guides/testing/_index.md)
• L64 in content/docs/administration/onboarding-guide/setting-up-for-success.md "An AWS Virtual Private Cloud (VPC) component in Pulumi might consist of dozens of resources, including public and private subnets, internet gateways, NAT gatew…" → ✅ verified (framing: strengthened — claim narrows the source's "and more" to a specific list ending with "the VPC itself"; source's broader form proves the claim as a subset; evidence: The setting-up-for-success.md file at the relevant section states: "an AWS Virtual Private Cloud (VPC) might consist of dozens of resources: public and private subnets, internet gateways, NAT gateways, the VPC itself, and more." The compon…; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L66 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Pulumi Components provide storage in package managers, versioning, and secure dependencies as benefits of native language packages." → ✅ verified (evidence: The file at L66 area states verbatim: "Components provide all the benefits of native language packages: storage in package managers, versioning, secure dependencies, and more." This exactly matches the claim's assertion about storage in pa…; source: repo:content/docs/administration/onboarding-guide/setting-up-for-success.md)
• L68 in content/docs/administration/onboarding-guide/setting-up-for-success.md "Organizations can register their own templates in the Pulumi Cloud New Project Wizard." → ✅ verified (evidence: The organization-templates docs page confirms organizations can define and publish their own templates, and explicitly states these appear in the New Project Wizard: "The New Project Wizard card view includes a 'Filter by cloud' dropdown t…; source: content/docs/idp/concepts/organization-templates.md)
• L22 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi IaC projects have any number of stacks (instances of that project), while Pulumi ESC projects have environments (groups of related secrets and configura…" → ✅ verified (evidence: The file at L22 reads: "Pulumi IaC projects have any number of stacks (instances of that project), while Pulumi ESC projects have environments (groups of related secrets and configuration)." — an exact match to the claim.; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md)
• L22 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi ESC projects have environments (groups of related secrets and configuration)." → ✅ verified (evidence: The file at L22 states verbatim: "Pulumi ESC projects have environments (groups of related secrets and configuration)." This exactly matches the claim.; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md)
• L24 in content/docs/administration/onboarding-guide/ways-of-working.md "Think of an IaC project like a Git repository and a stack like a Git branch. Teams structure Git repos differently—some prefer monolithic repos while others pr…" → ✅ verified (framing: strengthened — claim ends with "with the same flexibility" where source says "in various ways"; the source's broader form proves the claim as a subset.; evidence: The live Pulumi docs page at pulumi.com/docs/administration/onboarding-guide/ways-of-working/ states: "Think of an IaC project like a Git repository and a stack like a Git branch. Just as teams structure Git repos differently—some prefer m…; source: https://www.pulumi.com/docs/administration/onboarding-guide/ways-of-working/)
• L50 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for organizing projects and stacks has changed from 'https://www.pulumi.com/docs/using-pulumi/organizing-projects-stacks/' to '/docs/iac/guid…" → ✅ verified (evidence: The target path /docs/iac/guides/basics/organizing-projects-stacks/ resolves to content/docs/iac/guides/basics/organizing-projects-stacks/_index.md in the pulumi/docs repo, which is a real file. The ways-of-working.md file at L50 alr…; source: gh search code --owner pulumi "organizing-projects-stacks" --extension md; repo:content/docs/administration/onboarding-guide/ways-of-working.md)
• L56 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi supports the following programming languages: Python, Go, Node.js languages (JavaScript, TypeScript), .NET languages (C#, F#), JVM languages (Java, Groo…" → ❌ contradicted (framing: narrowed — claim broadens the source's "Java" to "JVM languages (Java, Groovy, Scala, Clojure)"; the official languages page lists only Java as a supported JVM…; evidence: The official /docs/iac/languages-sdks/ page lists only six supported languages: Node.js, Python, Go, .NET, Java, and Pulumi YAML — with no mention of Groovy, Scala, or Clojure as supported JVM languages. The page description reads: "Pulu…; source: repo:content/docs/iac/languages-sdks/_index.md)
• L64 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for Pulumi Packages has changed from 'https://www.pulumi.com/docs/iac/guides/packages/' to '/docs/iac/concepts/packages/'." → ✅ verified (evidence: The file content/docs/iac/concepts/packages/_index.md exists at the new path /docs/iac/concepts/packages/ and includes aliases: [/docs/iac/guides/packages/], confirming the old URL redirects to the new canonical path.; source: repo:content/docs/iac/concepts/packages/_index.md)
• L78 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi Cloud lets you control which projects, stacks, and environments teams can access, and with what permissions, through role-based access control (RBAC)." → ✅ verified (framing: strengthened — the source attributes RBAC access control to "organizing members into teams" generally; the claim attributes it to "Pulumi Cloud" specifically,…; evidence: The source file at the referenced location states: "By organizing members into teams, you can control which projects, stacks, and environments they can access, and with what permissions, through role-based access control (RBAC)." The claim…; source: content/docs/administration/onboarding-guide/ways-of-working.md)
• L82 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi Cloud supports Single Sign-On (SSO) with identity providers including Microsoft Entra ID, Google Workspace, Okta, or any SAML 2.0 compliant provider." → ✅ verified (evidence: The SAML overview page states "The Pulumi Cloud can be configured to work with any SAML 2.0 identity provider" and lists Microsoft Entra ID, Google Workspace, and Okta as integration guides. The ways-of-working.md file at L82 reads: "Many…; source: content/docs/administration/access-identity/saml/_index.md)
• L84 in content/docs/administration/onboarding-guide/ways-of-working.md "Once you've completed the setup steps, you're ready to invite your team. Refer to [Inviting members to an organization](/docs/administration/organizations-team…" → ✅ verified (evidence: The file content/docs/administration/organizations-teams/organizations.md contains a section with the exact heading "## Inviting members to an organization", which resolves to the anchor #inviting-members-to-an-organization referenced…; source: repo:content/docs/administration/organizations-teams/organizations.md)
• L88 in content/docs/administration/onboarding-guide/ways-of-working.md "It's common to give developers their own stacks for development and testing. Pulumi's projects and stacks model is built for this and leads to fast, productive…" → ❌ contradicted (framing: shifted — source says "makes this easy" but claim says "is built for this"; different framing of the same subject; evidence: The live Pulumi docs page says "Pulumi's projects and stacks model makes this easy and leads to fast, productive experiences." The PR claim substitutes "is built for this" for "makes this easy," which shifts the framing from a capability s…; source: https://www.pulumi.com/docs/administration/onboarding-guide/ways-of-working/)
• L94 in content/docs/administration/onboarding-guide/ways-of-working.md "Review stacks in Pulumi are short-lived stacks for each pull request that are automatically torn down." → ✅ verified (framing: strengthened — claim narrows the full lifecycle description to just the creation-per-PR and automatic teardown aspects; the source's broader form ("created aut…; evidence: The review stacks docs state: "They are created automatically when a pull request is opened, updated on each new commit, and destroyed when the pull request is merged or closed." This confirms they are per-PR stacks that are automatically…; source: content/docs/deployments/deployments/review-stacks.md)
• L95 in content/docs/administration/onboarding-guide/ways-of-working.md "TTL stacks in Pulumi are automatically destroyed after a specified timeframe to prevent cloud waste." → ✅ verified (evidence: The ways-of-working.md file at the relevant line states: "TTL stacks: Automatically destroyed after a specified timeframe to prevent cloud waste." The TTL docs confirm: "TTL Stacks...enable the automat…; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md and repo:content/docs/deployments/deployments/ttl.md)
• L97 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for stack references has changed from 'https://www.pulumi.com/blog/iac-recommended-practices-using-stack-references/' to '/blog/iac-best-prac…" → ✅ verified (evidence: The file content/docs/administration/onboarding-guide/ways-of-working.md contains Use [stack references](/blog/iac-best-practices-applying-stack-references/) to factor out shared infrastructure, confirming the new internal link `/blog/…; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md)
• L107 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for Pulumi YAML has changed from 'https://www.pulumi.com/docs/languages-sdks/yaml/' to '/docs/iac/languages-sdks/yaml/'." → ✅ verified (evidence: The file content/docs/iac/languages-sdks/yaml/_index.md exists at the new path /docs/iac/languages-sdks/yaml/, and it includes aliases: ["/docs/languages-sdks/yaml/"], confirming the old URL /docs/languages-sdks/yaml/ now redirects…; source: repo:content/docs/iac/languages-sdks/yaml/_index.md)
• L112-114 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for Pulumi Automation API has changed from 'https://www.pulumi.com/docs/using-pulumi/automation-api/' to '/docs/iac/automation-api/'." → ✅ verified (evidence: The file at L112-114 uses the link /docs/iac/automation-api/ for Pulumi's Automation API, and the Automation API index page confirms /docs/iac/automation-api/ is the canonical path while /docs/using-pulumi/automation-api/ is listed o…; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md and repo:content/docs/iac/automation-api/_index.md)
• L113 in content/docs/administration/onboarding-guide/ways-of-working.md "- Pulumi's Backstage plugin" → ✅ verified (evidence: The blog post exists at pulumi/docs:content/blog/pulumi-backstage-plugin/index.md, confirming the URL /blog/pulumi-backstage-plugin/ resolves to a real page. The file contains content about "a new Pulumi Plugin for Backstage."; source: gh search code --owner pulumi "pulumi-backstage-plugin" → pulumi/docs:content/blog/pulumi-backstage-plugin/index.md)
• L114 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for Pulumi's Automation API resolves to /docs/iac/automation-api/." → ✅ verified (evidence: Line 114 of ways-of-working.md contains [Pulumi's Automation API](/docs/iac/automation-api/), and the file content/docs/iac/automation-api/_index.md exists with title "Automation API", confirming the internal link resolves to `/docs/ia…; source: repo:content/docs/administration/onboarding-guide/ways-of-working.md and repo:content/docs/iac/automation-api/_index.md)
• L116 in content/docs/administration/onboarding-guide/ways-of-working.md "Learn more about building developer portals." → ✅ verified (evidence: The file content/docs/idp/concepts/_index.md exists and is a valid page about Pulumi IDP concepts, confirming the link /docs/idp/concepts/ resolves to real content about building developer platforms/portals.; source: repo:content/docs/idp/concepts/_index.md)
• L128 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi Deployments is described as the recommended CI/CD platform option, purpose-built for IaC deployments and integrated into Pulumi Cloud." → ✅ verified (framing: strengthened — the source says "managed CI/CD platform purpose-built for infrastructure as code"; the claim adds "recommended" and "integrated into Pulumi Clou…; evidence: The /docs/deployments/deployments/ page opens with: "Pulumi Deployments is a managed CI/CD platform purpose-built for infrastructure as code. It provides everything you need to securely deploy infrastructure changes across your organizat…; source: content/docs/deployments/deployments/_index.md)
• L129 in content/docs/administration/onboarding-guide/ways-of-working.md "The Pulumi Kubernetes Operator can trigger deployments from within Kubernetes clusters." → ✅ verified (evidence: The repo source at content/docs/administration/onboarding-guide/ways-of-working.md contains exactly: "Pulumi Kubernetes Operator: Trigger deplo…; source: gh search code --owner pulumi "trigger deployments from within Kubernetes" --repo pulumi/docs)
• L130 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for continuous delivery integrations has changed from 'https://www.pulumi.com/docs/using-pulumi/continuous-delivery/' to '/docs/iac/guides/co…" → ✅ verified (evidence: The continuous delivery docs live at content/docs/iac/guides/continuous-delivery/_index.md, confirming /docs/iac/guides/continuous-delivery/ is the current canonical path. The old path /docs/using-pulumi/continuous-delivery/ is liste…; source: repo:content/docs/iac/guides/continuous-delivery/_index.md (aliases include /docs/using-pulumi/continuous-delivery/))
• L130 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi supports existing CI/CD solutions including GitHub Actions, GitLab CI, and Octopus Deploy." → ✅ verified (framing: strengthened — claim names three specific systems ("GitHub Actions, GitLab CI, and Octopus Deploy") as a subset of the source's broader list of 16+ supported C…; evidence: The /docs/iac/guides/continuous-delivery/ page explicitly lists all three under "Third-party CI/CD systems": "GitHub Actions", "GitLab CI/CD", and "Octopus Deploy" each have dedicated guide links, confirming Pulumi supports all three.; source: repo:content/docs/iac/guides/continuous-delivery/_index.md)
• L132 in content/docs/administration/onboarding-guide/ways-of-working.md "The Pulumi GitHub App provides instant GitOps workflow support, including deployment previews in pull requests." → ✅ verified (framing: strengthened — the source describes specific features (PR comments, push-to-deploy, review stacks); the claim summarizes these as "instant GitOps workflow supp…; evidence: The official Pulumi GitHub App docs confirm it provides deployment previews in pull requests: "Pulumi's GitHub app displays the results of Pulumi stack update previews in pull requests and enables automatic stack deployments via Pulumi Dep…; source: repo:content/docs/integrations/version-control/github-app.md)
• L134 in content/docs/administration/onboarding-guide/ways-of-working.md "The Pulumi GitLab Integration supports setting up Pipelines and Webhooks for GitLab CI/CD." → ❌ contradicted (framing: shifted — source describes the integration as automating webhook registration with "no manual webhook or pipeline configuration required," while the claim fram…; evidence: The GitLab integration page states "Pulumi automatically registers a group-level webhook on your GitLab group. No manual webhook or pipeline configuration is required." The integration is for merge request previews, push-to-deploy, review…; source: repo:content/docs/integrations/version-control/gitlab.md)
• L141 in content/docs/administration/onboarding-guide/ways-of-working.md "4. Set up Pulumi Cloud access tokens for automation" → ✅ verified (evidence: The file content/docs/administration/access-identity/access-tokens.md exists with title: Access tokens and h1: Pulumi Cloud access tokens, and includes /docs/administration/access-identity/access-tokens/ as an alias, confirming the…; source: repo:content/docs/administration/access-identity/access-tokens.md)
• L145 in content/docs/administration/onboarding-guide/ways-of-working.md "Drift occurs when changes happen outside the IaC pipeline, causing conflicts between the last known deployment and cloud resources' current state." → 🤷 unverifiable (framing: shifted — source says "changes in the actual state...that deviate from the expected state stored in Pulumi Cloud"; claim says "changes happen outside the IaC p…; evidence: The drift.md source defines drift as "identifying changes in the actual state of your cloud environment that deviate from the expected state stored in Pulumi Cloud," caused by "manual adjustments made directly in the cloud provider's conso…; source: repo:content/docs/deployments/deployments/drift.md)
• L153-154 in content/docs/administration/onboarding-guide/ways-of-working.md "The Pulumi Cloud REST API is described as the API that powers the CLI and cloud console experiences." → ❌ contradicted (framing: shifted — source says "used by the Pulumi CLI"; claim adds "cloud console experiences" which is not stated in the source; evidence: The cloud-rest-api-intro shortcode (which renders the intro text at /docs/reference/cloud-rest-api/) says: "The Pulumi Cloud REST API is used by the Pulumi CLI to query and interact with state information, history, stack tags, etc." —…; source: layouts/shortcodes/cloud-rest-api-intro.html)
• L156-157 in content/docs/administration/onboarding-guide/ways-of-working.md "The Pulumi Automation API enables embedding IaC capabilities into any software, including custom tools, self-serve portals, complex deployment orchestrations,…" → ✅ verified (framing: strengthened — claim enumerates specific use cases (custom tools, self-serve portals, complex deployment orchestrations, SaaS products) that are implied by the…; evidence: The Automation API docs page states "Automation API allows you to embed Pulumi within your application code, making it easy to create custom experiences on top of Pulumi that are tailored to your use-case, domain, and team." The specific e…; source: content/docs/iac/automation-api/_index.md)
• L159-160 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi Cloud Webhooks allow reacting to lifecycle events in Pulumi Cloud by invoking custom REST API endpoints." → ❌ contradicted (framing: shifted — source describes Pulumi sending HTTP POST notifications to external services; claim reframes this as "reacting to lifecycle events by invoking custom…; evidence: The source at /docs/deployments/webhooks/ states: "Pulumi Webhooks allow you to notify external services of events happening within your Pulumi organization... Pulumi will notify the registered webhook listeners via a HTTP POST request wit…; source: content/docs/deployments/webhooks.md)
• L164 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi supports hundreds of providers out of the box." → ❌ contradicted (framing: narrowed — claim broadens the source figures ("150+", "180+", "nearly 200") to "hundreds"; the sources support a figure approaching but not yet at 200, not "hu…; evidence: Pulumi's own official docs page states "150+ cloud providers and services," and the 2024 year-in-review blog cites "180+ supported providers." The PulumiUP 2024 blog says "nearly 200 providers." None of these sources support the claim of "…; source: https://www.pulumi.com/docs/ (150+); https://www.pulumi.com/blog/pulumi-year-in-review/ (180+); https://www.pulumi.com/blog/pulumi-up-2024/ ("nearly 200"))
• L166 in content/docs/administration/onboarding-guide/ways-of-working.md "The internal link for custom providers has changed from 'https://www.pulumi.com/docs/iac/packages-and-automation/pulumi-packages/authoring/' to '/docs/iac/guid…" → ✅ verified (evidence: The current file at content/docs/administration/onboarding-guide/ways-of-working.md contains **[Custom providers](https://www.pulumi.com/docs/iac/packages-and-automation/pulumi-packages/authoring/)**, and the target path `content/docs/…; source: gh search code --owner pulumi "authoring" "ways-of-working"; gh search code --owner pulumi "publishing-packages")
• L167 in content/docs/administration/onboarding-guide/ways-of-working.md "Creating custom Pulumi providers involves creating resource schemas and CRUD operations." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
• L169-170 in content/docs/administration/onboarding-guide/ways-of-working.md "Terraform provider bridging allows bridging any Terraform provider at development time to use it from Pulumi IaC programs." → ✅ verified (framing: strengthened — claim adds "at development time" qualifier; sources confirm the SDK is generated locally via pulumi package add (a development-time step), mak…; evidence: The official Pulumi blog at /blog/any-terraform-provider/ and docs confirm: "The Any Terraform Provider is a parameterized bridged provider that can wrap any Terraform or OpenTofu provider, even ones without a pre-built Pulumi package." Th…; source: repo:content/docs/iac/guides/continuous-delivery/_index.md)
• L172-173 in content/docs/administration/onboarding-guide/ways-of-working.md "Pulumi dynamic providers allow writing CRUD logic inline in a Pulumi IaC program without building a separate provider." → ✅ verified (framing: strengthened — claim narrows the source's general "core logic of a provider defined within the context of a Pulumi program" to "writing CRUD logic inline in a…; evidence: The Pulumi architecture docs state: "Dynamic providers are a Pulumi feature that allows the core logic of a provider to be defined and managed within the context of a Pulumi program. This is in contrast to a normal ('real', sometimes 'side…; source: gh api repos/pulumi/pulumi/contents/provider/dynamic-providers/)

[github-actions]

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

• [L68] content/docs/administration/onboarding-guide/choose-subscription.md — broken fragment anchor in the relativized link. The PR converts https://www.pulumi.com/docs/iac/concepts/state-and-backends/#logging-into-the-aws-s3-backend → /docs/iac/concepts/state-and-backends/#logging-into-the-aws-s3-backend, but state-and-backends.md has no #logging-into-the-aws-s3-backend heading — the closest match is ## Logging into and out of State Backends (slug #logging-into-and-out-of-state-backends), and the AWS S3 backend content itself has moved to /docs/iac/guides/basics/using-a-diy-backend/. Since the PR is touching this exact link, it's worth fixing the anchor here rather than carrying the breakage forward. Two reasonable fixes:

  To get started with self-hosted Pulumi Cloud, follow the guides to set up your [state backend](/docs/iac/guides/basics/using-a-diy-backend/) and [self-hosting infrastructure](/docs/administration/self-hosting/)
  

  …or, if the intent is the broader login flow rather than the AWS-specific backend setup:

  To get started with self-hosted Pulumi Cloud, follow the guides to set up your [state backend](/docs/iac/concepts/state-and-backends/#logging-into-and-out-of-state-backends) and [self-hosting infrastructure](/docs/administration/self-hosting/)
  

⚠️ Low-confidence

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

• [L98] content/docs/administration/onboarding-guide/choose-subscription.md — "Users can sign up for Pulumi using their email address and password, or connect with their GitHub, GitLab, or Atlassian identity at app.pulumi.com/signup." — verifier returned unverifiable because app.pulumi.com/signup is a JS SPA and its server-rendered body only exposes CSS. The CSS variables (--color-identity-github, --color-identity-gitlab, --color-identity-atlassian) strongly suggest the providers are present, and the line text predates this PR (the PR only relativized the trailing "account management" link on this line; the sign-up enumeration is unchanged). No author action required unless the provider list has materially changed since the page was originally written.

• [L26] content/docs/administration/onboarding-guide/migrating-to-pulumi.md — "Pulumi supports consuming Terraform workspace outputs." — verifier did not converge within turn budget. Text is unchanged on this line (the PR's edit at this stanza is on L24, not L26). Pulumi's Terraform-coexistence story does include reading remote-state outputs via terraform.RemoteStateReference; if you have time, a quick spot-check against /docs/iac/adopting-pulumi/import/from-terraform/ would resolve the gap, but the line predates this PR.

• [L145] content/docs/administration/onboarding-guide/ways-of-working.md — "Drift occurs when changes happen outside your IaC pipeline, causing conflicts between your last known deployment and your cloud resources' current state." — verifier flagged a framing shift vs /docs/deployments/deployments/drift/, which defines drift in terms of "actual state…that deviates from the expected state stored in Pulumi Cloud." Both are defensible drift definitions; the PR did not introduce or change this sentence (only the trailing link was relativized). No author action required; flagging only because it sits adjacent to a touched link.

• [L167] content/docs/administration/onboarding-guide/ways-of-working.md — "Creating custom Pulumi providers involves creating resource schemas and CRUD operations." — verifier did not converge. Text is unchanged by this PR (only the link target on L166 was changed). The claim is consistent with the new target /docs/iac/guides/building-extending/packages/publishing-packages/, which does cover schema + CRUD authoring; no action required for this PR.

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

• [L88] content/docs/administration/onboarding-guide/ways-of-working.md — Spurious: the verifier compared the new wording ("is built for this") against the live published version of this very page ("makes this easy"), so the "framing shift" it flagged is just this PR's own intentional Vale-style edit (removing the difficulty qualifier "easy"). The substantive claim — that Pulumi's project/stack model supports per-developer dev/test stacks — is unchanged and uncontested.

💡 Pre-existing issues in touched files (optional)

• [L56] content/docs/administration/onboarding-guide/ways-of-working.md — Pre-existing: the line claims Pulumi supports "JVM languages (Java, Groovy, Scala, Clojure)," but /docs/iac/languages-sdks/ lists only Java among JVM languages. The PR's only change to this line is the URL relativization plus simple use cases → declarative use cases; the JVM enumeration is pre-existing and out of scope for a link-refactor PR. Worth a separate follow-up to either narrow the list to "Java" or verify which other JVM languages still have SDK support.

• [L134] content/docs/administration/onboarding-guide/ways-of-working.md — Pre-existing: "Use the [Pulumi GitLab Integration] to set up Pipelines and Webhooks for GitLab CI/CD" — the integration docs state "Pulumi automatically registers a group-level webhook…no manual webhook or pipeline configuration is required," so framing it as "set up Pipelines and Webhooks" overstates the manual lift required of the reader. The PR only changed the link target on this line; the wording predates this PR.

• [L153-154] content/docs/administration/onboarding-guide/ways-of-working.md — Pre-existing: the line describes the Cloud REST API as the API that "powers the CLI and cloud console experiences," but the upstream shortcode (layouts/shortcodes/cloud-rest-api-intro.html) attributes it only to the CLI. The "cloud console experiences" half is plausible but uncited. The PR only relativized the link; the descriptive sentence is unchanged.

• [L159-160] content/docs/administration/onboarding-guide/ways-of-working.md — Pre-existing: "React to lifecycle events in Pulumi Cloud by invoking custom REST API endpoints." The webhooks docs frame this the opposite way — Pulumi sends HTTP POST notifications to external listeners, it does not "invoke custom REST API endpoints" on behalf of the user (the listener URL is the user's, but the verb framing is upside-down). Sentence is unchanged by this PR.

• [L164] content/docs/administration/onboarding-guide/ways-of-working.md — Pre-existing: "Pulumi supports hundreds of providers out of the box" — Pulumi's own docs cite "150+", the year-in-review blog cites "180+", and the PulumiUP 2024 post says "nearly 200." None of those is "hundreds" (which reads as ≥200 in normal English). Line is unchanged by this PR. Worth a follow-up to align the figure with the current registry count.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

• 2026-05-22T03:44:36Z — Pure link-refactor + Vale-style PR. One real finding (broken #logging-into-the-aws-s3-backend fragment on L68 of choose-subscription.md). Five pre-existing factual nits on lines this PR only touched for URL/style fixes. (ca5f938)

---

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.)

[cnunciato]

[jkodroff]

@claude #update-review

[github-actions]

🤖 Review updated on @jkodroff's request.