Verification trail
#4
✅ Verified
content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:11
The Policy violations section appears on GitHub, GitLab, Bitbucket, and Azure DevOps.
evidence: The version-control integrations docs page confirms GitHub, GitLab, Bitbucket, and Azure DevOps are exactly the four native VCS integrations that provide "Pull request previews and comments" and "Commit status checks" ("The native…; source: repo:content/docs/integrations/version-control/_index.md
source: repo:content/docs/integrations/version-control/_index.md
pass1
#5
✅ Verified
content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:13
The version control integrations documentation page exists at /docs/integrations/version-control/ and provides details relevant to this policy violations…
evidence: content/docs/integrations/version-control/_index.md exists at that path and documents pull request comments, commit status checks across GitHub, GitLab, Bitbucket, and Azure DevOps — directly relevant to the policy violations feature…; source: repo:content/docs/integrations/version-control/_index.md
source: repo:content/docs/integrations/version-control/_index.md
pass1
#2
➖ Not a claim
content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:3
date: 2026-09-14
evidence: This is a frontmatter date field matching the changelog file's own filename date convention (content/releases/changelog/2026-09-14-*.md), not a falsifiable external assertion.; source: content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md
source: content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md
pass3
#1
🤷 Unverifiable
content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:2
Pulumi Cloud now includes a 'Policy violations' section in the pull request comment and commit check it posts when a preview or update runs with a policy pack.
evidence: (escalated from pass1) Public docs confirm Pulumi Cloud already posts pull request comments and commit status checks with preview/update summaries via its GitHub App and other VCS integrations, e.g. "Pulumi GitHub App — rich pull request…; source: WebSearch ran query "Pulumi Cloud pull request comment policy pack preview commit status check"; top results describe existing PR comment/commit check features but not the new Policy violations section; intuition: This claim's implementing change is in the private pulumi-service repo; a pass1 lane with gh access to that repo (if…
source: WebSearch ran query "Pulumi Cloud pull request comment policy pack preview commit status check"; top results describe existing PR comment/commit check features but not the new Policy violations section
pass3
#3
🤷 Unverifiable
content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:11
Commit check run details include the full list of policy violations, without the 40-item cap applied to pull request comments.
evidence: (escalated from pass1) This claim describes internal implementation behavior of the pulumi-service backend (check-run rendering vs. PR comment rendering caps) tied to a specific internal PR (pulumi/pulumi-service#48886). Public web…; source: WebSearch ran query "Pulumi policy violations pull request comments 40-item cap check run"; top results didn't address the claim
source: WebSearch ran query "Pulumi policy violations pull request comments 40-item cap check run"; top results didn't address the claim
pass3
No claims match the current filter.
Findings
| ID | Bucket | File:lines | Status | Disposition |
|---|---|---|---|---|
| F1 | ⚠️ Reviewer check | content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md:2 | disputed-held | refuted — Scope is settled by the author's citation of pulumi-service#48886 — both update_pull_request_comment.tmpl and update_check_run_details.tmpl add the section, GetUpdateLogs streams EngineEventPolicy for previews as well as updates, and the four VCS providers match the shipped changelog fragment. One detail does not settle: the finding asked whether the heading renders literally as "Policy violations", and the author's own quote of the shipping templates says "## Policy Violations" (title case), while the entry writes "**Policy violations**". Reviewer call: quote the product string verbatim as "Policy Violations", or keep sentence case per the site heading convention since this reads as prose rather than a quoted UI label. |
| F2 | ❓ Author answer | content/releases/changelog/2026-09-14-policy-violations-in-pull-request-comments-and-checks.md | conceded | — |
Editorial stances
The extractor found no positioning or comparison language in this PR's added lines.
Investigation log
- cross-sibling-reads
- not run (not in a templated section)
- external-claim-verification
- 2 of 5 claims verified (2 unverifiable, 0 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 2 Pass 1, 0 Pass 2, 3 Pass 3 (verified 0, contradicted 0, unverifiable 3).
- 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
- 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/)
History
- 2026-09-14T14:48:59Z
02bee8f
initial review (pending publication)
- 2026-09-14T15:51:01Z
02bee8f0f7
Author cited pulumi-service#48886: F2 conceded; F1 scope confirmed but heading casing differs, held.