content(concepts): refresh Projects, add org docs

[jkodroff]

Refreshes the Concepts → Projects page and related concept content.

Changes

• Convert the Pulumi.yaml examples on the Projects page to language choosers; remove JavaScript references (TypeScript only).
• Add the awsx-root-directory-java example program so the root-relative paths example covers Java.
• Add an Organizations section to the Pulumi Cloud page, with code samples for reading the current organization.
• Cross-link the Projects page to "getting the current stack".

Closes #19324

[github-actions]

Pre-merge Review — Last updated 2026-05-22T15:10:52Z

Tip

Summary: This PR refreshes the Projects concept page (content/docs/iac/concepts/projects/_index.md) and adds a new Pulumi Cloud concept page (content/docs/iac/concepts/pulumi-cloud.md) that parallels existing siblings (stacks.md, state-and-backends.md, etc.), along with a new Java variant of the awsx-root-directory example program to round out language coverage (the other five — TypeScript, Python, Go, C#, YAML — already existed). Wrongness that would block reader success here would be incorrect runtime: values or options.binary paths in the Pulumi.yaml examples, broken anchor links into stacks.md / the Pulumi.yaml reference, or wrong SDK call shapes for getOrganization across the six languages. Investigative passes: 47-claim verification (44 verified · 1 contradicted-but-spurious · 2 non-claims), cross-sibling reads of project-file.md / stack-settings-file.md / stacks.md / state-and-backends.md, frontmatter + alias sweep, link-target spot-checks for the new Pulumi Cloud page, code-examples checks on the new Java program (3 specialists, 0 findings), and a Vale prose pass.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH
cross-sibling consistency	HIGH
code correctness	HIGH

Investigation log

• Cross-sibling reads: 4 of 12 siblings (projects/: project-file.md, stack-settings-file.md; iac/concepts/: stacks.md anchor #getting-the-current-stack-programmatically, state-and-backends.md)
• External claim verification: 44 of 47 claims verified (0 unverifiable, 1 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 44 Pass 1, 0 Pass 2, 3 Pass 3 (verified 0, contradicted 1, unverifiable 2).
• Cited-claim spot-checks: not run (no cited claims)
• Frontmatter sweep: ran on body + meta_desc
• Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
• Code execution: ran static/programs/awsx-root-directory-java (CI test harness gates parse + imports)
• Code-examples checks: ran (3 specialists: structural, existence, body-code-coverage); 0 findings
• Editorial-balance pass: not run (not under content/blog/)

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

🔍 Verification trail

47 claims extracted · 44 verified · 0 unverifiable · 1 contradicted

• L31 in content/docs/iac/concepts/projects/_index.md "The Pulumi project file must begin with a capital 'P', and either '.yml' or '.yaml' extension will work." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md states: "The project file must begin with a capital P, although either .yml or .yaml extension will work." This is an exact match to the claim.; source: repo:content/docs/iac/concepts/projects/_index.md)
• L41 in content/docs/iac/concepts/projects/_index.md "The runtime value for a TypeScript Pulumi project is 'nodejs' in Pulumi.yaml." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md explicitly shows the TypeScript choosable block with runtime: nodejs in the Pulumi.yaml example: "```yaml\nname: webserver\nruntime: nodejs\ndescription: A minimal Pulumi program…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L50 in content/docs/iac/concepts/projects/_index.md "The runtime value for a Python Pulumi project is 'python' in Pulumi.yaml." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md explicitly shows a Python Pulumi.yaml example: runtime: python, and states "Supported runtimes are nodejs, python, dotnet, go, java, and yaml."; source: repo:content/docs/iac/concepts/projects/_index.md)
• L59 in content/docs/iac/concepts/projects/_index.md "The runtime value for a Go Pulumi project is 'go' in Pulumi.yaml." → ✅ verified (evidence: The file content/docs/iac/concepts/projects/_index.md explicitly shows a Go Pulumi.yaml example with runtime: go, and the prose states "Supported runtimes are nodejs, python, dotnet, go, java, and yaml."; source: repo:content/docs/iac/concepts/projects/_index.md)
• L68 in content/docs/iac/concepts/projects/_index.md "The runtime value for a C#/.NET Pulumi project is 'dotnet' in Pulumi.yaml." → ✅ verified (evidence: The docs file itself shows runtime: dotnet in the csharp choosable block, and the pulumi/pulumi source confirms DotNetRuntime = "dotnet" (pkg/testing/integration/program.go) and runtime: dotnet in project test files.; source: repo:content/docs/iac/concepts/projects/_index.md and gh search code pulumi/pulumi DotNetRuntime)
• L77 in content/docs/iac/concepts/projects/_index.md "The runtime value for a Java Pulumi project is 'java' in Pulumi.yaml." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md explicitly shows a Java Pulumi.yaml example with runtime: java, and lists java among the supported runtimes: "Supported runtimes are nodejs, python, dotnet, go, java,…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L86 in content/docs/iac/concepts/projects/_index.md "The runtime value for a Pulumi YAML program is 'yaml' in Pulumi.yaml." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md explicitly lists yaml as a supported runtime and shows a YAML program example with runtime: yaml in Pulumi.yaml. The docs state: "Supported runtimes are nodejs, python, `…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L94 in content/docs/iac/concepts/projects/_index.md "For TypeScript, the working directory should contain a package.json file that points to an entrypoint such as index.ts." → ✅ verified (evidence: The file content/docs/iac/concepts/projects/_index.md contains the exact sentence: "For TypeScript, the working directory should contain a package.json file that points to an entrypoint such as index.ts."; source: repo:content/docs/iac/concepts/projects/_index.md)
• L94 in content/docs/iac/concepts/projects/_index.md "For Python, the presence of a __main__.py or setup.py file defines the entrypoint." → ✅ verified (evidence: The exact claim text appears verbatim in the docs file at the stated line: "For Python, the presence of a __main__.py or setup.py file defines the entrypoint." The Pulumi Python language host source (`sdk/python/cmd/pulumi-language-pyt…; source: repo:content/docs/iac/concepts/projects/_index.md (L94); gh search code pulumi/pulumi main.py → sdk/python/cmd/pulumi-language-python/main.go)
• L94 in content/docs/iac/concepts/projects/_index.md "Go, .NET, and Java follow the conventions of their respective build tools for locating the program's entrypoint." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md contains the exact sentence: "Go, .NET, and Java follow the conventions of their respective build tools." in the paragraph describing entrypoint conventions for each language.; source: repo:content/docs/iac/concepts/projects/_index.md)
• L100 in content/docs/iac/concepts/projects/_index.md "For Go, .NET, and Java Pulumi projects, you can point the runtime at a pre-built executable or assembly using the 'binary' option in Pulumi.yaml, which skips t…" → ✅ verified (framing: strengthened — claim adds "Pulumi projects" and "at deployment time" qualifiers, which are consistent with the source's broader statement; the source's form pr…; evidence: The file at content/docs/iac/concepts/projects/_index.md explicitly states: "For Go, .NET, and Java, you can point the runtime at a pre-built executable or assembly with the binary option. This skips the build step at deployment time" wi…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L106 in content/docs/iac/concepts/projects/_index.md "A precompiled Go Pulumi program can be configured in Pulumi.yaml using runtime name 'go' with an options.binary field set to the executable name (e.g., 'mybina…" (also L108, L113) → ✅ verified (evidence: The file content at the referenced lines shows exactly: runtime: name: go with options: binary: mybinary under a section titled "Compiled languages with a pre-built executable", matching the claim precisely.; source: repo:content/docs/iac/concepts/projects/_index.md)
• L118-119 in content/docs/iac/concepts/projects/_index.md "A precompiled .NET Pulumi program can be configured in Pulumi.yaml using runtime name 'dotnet' with an options.binary field set to the assembly path (e.g., 'bi…" (also L125) → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md contains exactly this YAML snippet: runtime:\n name: dotnet\n options:\n binary: bin/MyInfra.dll under the section "Compiled languages with a pre-built executable", described…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L130-131 in content/docs/iac/concepts/projects/_index.md "A precompiled Java Pulumi program can be configured in Pulumi.yaml using runtime name 'java' with an options.binary field set to the JAR path (e.g., 'target/my…" (also L137) → ✅ verified (evidence: The file content/docs/iac/concepts/projects/_index.md contains exactly the described YAML snippet: runtime: name: java with options: binary: target/my-project-1.0-SNAPSHOT-jar-with-dependencies.jar, under the section "Compiled langua…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L145 in content/docs/iac/concepts/projects/_index.md "A Pulumi YAML program can include its resources inline in Pulumi.yaml, using the 'resources' key with resource entries specifying a 'type' field." (also L153) → ✅ verified (evidence: The file at lines ~145-153 contains: "A Pulumi.yaml file for a YAML program can include its resources inline:" followed by a YAML example using a resources key with a bucket entry specifying type: aws:s3:Bucket.; source: repo:content/docs/iac/concepts/projects/_index.md)
• L147 in content/docs/iac/concepts/projects/_index.md "A YAML Pulumi program with inline resources uses runtime: yaml and defines resources under a resources key, with each resource specifying a type (e.g., …" (also L153) → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.mdcontains the exact example under "Inline resources with the YAML runtime":runtime: yaml, a resourceskey, and each resource specifying atype(e.g.,type: aws:s3:Bucket`).; source: repo:content/docs/iac/concepts/projects/_index.md)
• L155 in content/docs/iac/concepts/projects/_index.md "Valid Pulumi project metadata is documented in the Pulumi.yaml reference at /docs/reference/pulumi-yaml/." → 🤝 matches (evidence: The source file content/docs/iac/concepts/projects/_index.md contains the exact text: "For more information on valid Pulumi project metadata, see the Pulumi.yaml reference." — which matches the claim preci…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L165 in content/docs/iac/concepts/projects/_index.md "The directory containing the Pulumi.yaml file may differ from the working directory if the project sets a main option." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md states: "You can get the directory containing the Pulumi.yaml file, which may differ from your working directory if the project sets a main option (see [main attribute](/docs/ref…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L167 in content/docs/iac/concepts/projects/_index.md "The path returned by the ProjectDirectory function (or language equivalent) is an absolute path." → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md in the "Root-relative paths" section states: "The path returned is an absolute path." This directly confirms the claim about the ProjectDirectory function (or language equivalent)…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L223 in content/docs/iac/concepts/projects/_index.md "There is a section titled 'Getting the current stack programmatically' in the Pulumi stacks documentation at /docs/iac/concepts/stacks/#getting-the-current-sta…" → ✅ verified (evidence: The file content/docs/iac/concepts/stacks.md in the pulumi/docs repo contains the heading ## Getting the current stack programmatically, which would render as the anchor #getting-the-current-stack-programmatically at `/docs/iac/conce…; source: gh search code --owner pulumi "getting the current stack programmatically" → pulumi/docs:content/docs/iac/concepts/stacks.md)
• L227 in content/docs/iac/concepts/projects/_index.md "Each stack created in a project has a file named 'Pulumi..yaml' that contains the configuration specific to that stack, and this file typically resi…" → ✅ verified (evidence: The file at content/docs/iac/concepts/projects/_index.md (under "Stack settings files") states verbatim: "Each stack that is created in a project will have a file named Pulumi.<stackname>.yaml that contains the configuration specific to…; source: repo:content/docs/iac/concepts/projects/_index.md)
• L3 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud adds the following capabilities for teams: access control, reusable configuration and secrets, policy enforcement, cloud resource inventory, sched…" (also L16) → ✅ verified (evidence: The file at L16 states exactly: "adds the capabilities teams need to operate Pulumi at scale: access control, reusable configuration and secrets, policy enforcement, cloud resource inventory, scheduled drift detection, managed deployments,…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L16 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud is the default state backend for the Pulumi CLI." → ✅ verified (evidence: The file at L16 states "Pulumi Cloud is the default state backend for the Pulumi CLI." The state-and-backends.md source also confirms: "It is the default backend and requires no additional configur…; source: content/docs/iac/concepts/pulumi-cloud.md and content/docs/iac/concepts/state-and-backends.md)
• L16 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi also works with a self-managed (DIY) backend as an alternative to Pulumi Cloud." → ✅ verified (evidence: The file at content/docs/iac/concepts/pulumi-cloud.md line 16 states verbatim: "Using Pulumi Cloud is optional; Pulumi also works with a self-managed (DIY) backend." The linked guide confir…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L20-25 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud provides managed deployments that run Pulumi operations remotely, for example in response to Git pushes, and emit webhooks for event-driven workfl…" → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md contains the exact statement: "Managed deployments that run Pulumi operations remotely, for example in response to Git pushes, and emit [webhooks](/docs…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L22 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud's policy as code enforcement is applied centrally to every update." → ✅ verified (evidence: The file at content/docs/iac/concepts/pulumi-cloud.md line 22 states: "Policy as code enforcement applied centrally to every update, with pre-built policy packs for common security, compliance, and cost rules."; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L22 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud includes pre-built policy packs for common security, compliance, and cost rules." → ✅ verified (evidence: The file at content/docs/iac/concepts/pulumi-cloud.md contains the exact text: "Policy as code enforcement applied centrally to every update, with pre-built policy packs for common security, compliance, and…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L23 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud's cloud resource inventory discovers resources across cloud accounts, including resources not managed by Pulumi." → ✅ verified (evidence: The file at content/docs/iac/concepts/pulumi-cloud.md contains the exact statement: "Cloud resource inventory that discovers resources across your cloud accounts, including resources not managed by Pulumi."; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L24 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud's scheduled drift detection alerts you or remediates automatically when deployed infrastructure diverges from its declared state." → ✅ verified (evidence: The file at content/docs/iac/concepts/pulumi-cloud.md contains the exact bullet: "Scheduled drift detection that alerts you or remediates automatically when deployed infrastructure diverges fro…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L25 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud's managed deployments run Pulumi operations remotely, for example in response to Git pushes." → ✅ verified (framing: strengthened — claim narrows the full bullet (which also mentions webhooks) to just the remote-operations/Git-push aspect; source's broader form proves the cla…; evidence: The file at line ~25 states: "Managed [deployments] that run Pulumi operations remotely, for example in response to Git pushes, and emit [webhooks] for event-driven workflows." The claim accurately captures the first part of this bullet.; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L26 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Neo is an AI agent that helps debug deployments, write infrastructure as code, and answer questions about your environment." → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md at line 26 contains verbatim: "Pulumi Neo, an AI agent that helps debug deployments, write infrastructure as code, and answer questions about your environment." — an exa…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L27 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud supports ephemeral environments such as Review Stacks and TTL Stacks." → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md contains the exact bullet: "Ephemeral environments such as Review Stacks and TTL Stacks." — directly matching the claim.; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L29 in content/docs/iac/concepts/pulumi-cloud.md "Pulumi Cloud is available as a hosted SaaS and as a self-hosted edition you can run in your own environment." → ✅ verified (evidence: The exact sentence appears verbatim in the file at line 29: "Pulumi Cloud is available as a hosted SaaS and as a self-hosted edition you can run in your own environment."; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L31 in content/docs/iac/concepts/pulumi-cloud.md "A page comparing Pulumi Cloud and open source Pulumi, including which features are available with each option and what operational concerns each one entails, e…" → ✅ verified (evidence: The file content/docs/iac/guides/basics/pulumi-cloud-vs-oss.md exists and its content explicitly compares Pulumi Cloud and open source Pulumi: "This guide explains how Pulumi Cloud relates to open source Pulumi. It clarifies which capabi…; source: repo:content/docs/iac/guides/basics/pulumi-cloud-vs-oss.md)
• L35 in content/docs/iac/concepts/pulumi-cloud.md "The organization name is the first segment of a stack's fully qualified name, in the form <organization>/<project>/<stack>." → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md contains the exact sentence at the end of the "Organizations" section: "The organization name is also the first segment of a stack's fully qualified name, in the form `/<pr…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L35 in content/docs/iac/concepts/pulumi-cloud.md "Teams, role-based access control, billing, and shared Pulumi ESC environments all belong to an organization in Pulumi Cloud." → ✅ verified (framing: strengthened — claim consolidates "[teams] and [role-based access control]" from the source into "Teams, role-based access control"; the source's broader form…; evidence: The file at L35 (Organizations section) states: "[teams] and [role-based access control], billing, and shared [Pulumi ESC] environments all belong to an organization." The claim accurately paraphrases this, listing teams, role-based access…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L37 in content/docs/iac/concepts/pulumi-cloud.md "When you sign up for Pulumi Cloud, you automatically get a personal organization named after your username." → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md contains the exact sentence at the relevant line: "When you sign up for Pulumi Cloud, you automatically get a personal organization named after your username."; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L41 in content/docs/iac/concepts/pulumi-cloud.md "A Pulumi program can read the name of the organization it is deploying into at runtime." → ✅ verified (evidence: The file at L41 states: "Your program can read the name of the organization it is deploying into at runtime, which is useful for naming or tagging resources or for constructing references to other stacks." The pulumi/pulumi repo confirms…; source: repo:content/docs/iac/concepts/pulumi-cloud.md and gh search code --owner pulumi "getOrganization")
• L48 in content/docs/iac/concepts/pulumi-cloud.md "In TypeScript, the current Pulumi organization can be retrieved at runtime using pulumi.getOrganization()." → ✅ verified (evidence: The file content/docs/iac/concepts/pulumi-cloud.md contains a TypeScript code snippet showing const organization = pulumi.getOrganization(); under the "Getting the current organization programmatically" section, exactly matching the cl…; source: repo:content/docs/iac/concepts/pulumi-cloud.md)
• L55 in content/docs/iac/concepts/pulumi-cloud.md "In Python, the current Pulumi organization can be retrieved at runtime using pulumi.get_organization()." → ✅ verified (evidence: The Pulumi Python SDK's __init__.py exports get_organization from .metadata in __all__, and settings.py defines def get_organization() -> str with docstring "Returns the current organization name." — confirming `pulumi.get_orga…; source: gh api repos/pulumi/pulumi/contents/sdk/python/lib/pulumi/init.py and sdk/python/lib/pulumi/runtime/settings.py)
• L62 in content/docs/iac/concepts/pulumi-cloud.md "In Go, the current Pulumi organization can be retrieved at runtime using ctx.Organization()." → ✅ verified (evidence: The Go SDK defines func (ctx *Context) Organization() string in sdk/go/pulumi/context.go, and the doc file itself shows organization := ctx.Organization() in the Go choosable block. Test data in sdk/go/pulumi-language-go/testdata a…; source: gh search code pulumi/pulumi "Organization()" --language Go → pulumi/pulumi:sdk/go/pulumi/context.go; repo:content/docs/iac/concepts/pulumi-cloud.md L62)
• L69 in content/docs/iac/concepts/pulumi-cloud.md "In C#, the current Pulumi organization can be retrieved at runtime using Deployment.Instance.OrganizationName." → ✅ verified (evidence: The DeploymentInstance.cs source in pulumi/pulumi-dotnet contains public string OrganizationName => _deployment.OrganizationName; with the doc comment /// Returns the current organization name., confirming that `Deployment.Instance…; source: https://github.com/pulumi/pulumi-dotnet/blob/main/sdk/Pulumi/Deployment/DeploymentInstance.cs)
• L76 in content/docs/iac/concepts/pulumi-cloud.md "In Java, the current Pulumi organization can be retrieved at runtime using ctx.organizationName()." → ✅ verified (evidence: The Pulumi Java SDK (pulumi/pulumi-java) defines default String organizationName() in com.pulumi.Context, and integration tests use it as ctx.organizationName() — e.g., `"%s/%s/%s", ctx.organizationName(), ctx.projectName(), ctx.st…; source: gh search code --owner pulumi --repo pulumi/pulumi-java "organizationName"; pulumi/pulumi-java:sdk/java/pulumi/src/main/java/com/pulumi/Context.java)
• L84 in content/docs/iac/concepts/pulumi-cloud.md "In Pulumi YAML, the current organization can be referenced using the variable expression ${pulumi.organization}." → ✅ verified (evidence: The local file at L84 shows a YAML code snippet using ${pulumi.organization} to reference the current organization, and the pulumi/pulumi-yaml repo confirms this syntax in multiple test files (e.g., `organizationOutput: ${pulumi.organiza…; source: repo:content/docs/iac/concepts/pulumi-cloud.md and gh search code --owner pulumi "pulumi.organization" --language yaml)
• L2 in static/programs/awsx-root-directory-java/pom.xml "<project xmlns='http://maven.apache.org/POM/4.0.0'" → ➖ not-a-claim (evidence: The text xmlns="http://maven.apache.org/POM/4.0.0" is a standard XML namespace declaration in a Maven POM file, not a falsifiable assertion. It is a boilerplate XML namespace URI used in every Maven POM 4.0.0 file and does not constitute…; source: Standard Maven POM XML namespace convention; no external claim to verify.)
• L3 in static/programs/awsx-root-directory-java/pom.xml "xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'" → ➖ not-a-claim (evidence: This is a standard XML namespace declaration (xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance") found in a Maven pom.xml file. It is a boilerplate XML attribute referencing the W3C XML Schema Instance namespace, not a falsifiable…; source: static/programs/awsx-root-directory-java/pom.xml L3 — standard Maven POM XML namespace declaration)
• L4 in static/programs/awsx-root-directory-java/pom.xml "xsi:schemaLocation='http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd'>" → ❌ contradicted (framing: shifted — claim uses http://maven.apache.org/xsd/maven-4.0.0.xsd; authoritative sources require https://maven.apache.org/xsd/maven-4.0.0.xsd (HTTPS, not HT…; evidence: The claim uses http://maven.apache.org/xsd/maven-4.0.0.xsd (HTTP) for the XSD schema location. The official Apache Maven POM reference and Apache JIRA (MRELEASE-1032) both state the current correct form is `https://maven.apache.org/xsd/m…; source: https://issues.apache.org/jira/browse/MRELEASE-1032)

🚨 Outstanding in this PR

These must be resolved or refuted before merging.

No outstanding issues.

⚠️ Low-confidence

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

Style findings

Found by pattern-based linting; Findings may be false positives.

• line 165: [style] directional reference — Directional reference ('in the example below') -- link directly to the target (an #anchor or relative path) rather than relying on 'above'/'below' (STYLE-GUIDE.md §Inclusive Language).
• line 35: [style] wordiness — 'It is' is too wordy.
• line 41: [style] wordiness — 'it is' is too wordy.

📋 Triaged verifier findings

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

• [L4] static/programs/awsx-root-directory-java/pom.xml — xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" — verdict recorded as ❌ contradicted (framing: HTTP vs HTTPS XSD URL). Spurious: every other Java pom.xml under static/programs/ (50+ files) uses the identical http:// form — it's the canonical Maven boilerplate emitted by mvn archetype:generate and Maven recognizes both schemes. The XSD URL is also an xmlns-style namespace identifier, not a fetchable URL, so the HTTP/HTTPS distinction is cosmetic.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

• 2026-05-22T15:10:52Z — Refreshed Projects concept page + new Pulumi Cloud concept page review: no blockers; the one ❌ contradicted verdict (Maven pom.xml HTTP-vs-HTTPS XSD URL) is triaged as spurious — matches every other Java POM in the repo. 3 ⚠️ Vale style nags. (6834965)

---

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 6834965 is ready! 🎉

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