build: Adding a PR Risk Comment

[scotttjob]

Motivations

1. Looking to explore making our PRs more efficient.
2. As a base first step, I wanted to explore the idea of a Risk rating for a PR to help reviewers and contributors better understand the risk associated to change. Modifications to docs or stories should be less risky than build system or component changes.
3. The idea is this check will be used in a future step when a component grades above a certain threshold, we may invoke secondary AI-based processes to see about de-risking the PR, or if the PR will be risky no matter what generate QA steps for manual reviewers.

Changes

1. Adding a Danger Rule for how "Risky" a PR is. Details of what "Risk" means are within a human-readable specification. Changes in the future will be made to the spec first, then to the implementation of the spec.

Added

• Danger Rule, Workflow to run that danger rule, human-readable spec for the rule.

Security

• The danger rule should only run once, on this PR only.

Testing

• Branch off this PR, make a risky change, push the branch and open a PR. You should see a risk report.

Changes can be
tested via Pre-release

---

In Atlantis we use Github's built in pull request reviews.

[github-actions]

	Warnings
⚠️	High-risk PR: discuss this change with a developer before merge.

PR Risk

Risk: 85/100 (Very High)

Why: This change touches infrastructure, release flow, dependencies, or public API surface.

Signals

• Change size warning: strong line-count warning.
• Touches CI, build, release, or root tooling.
• Style-oriented files changed without visual regression or Storybook updates.

Guidance

• Developer review is recommended before merge.

Rubric: docs/pr-risk-rubric.md

Generated by 🚫 dangerJS against 4d3b3ef

[cloudflare-workers-and-pages]

Deploying atlantis with    Cloudflare Pages

Latest commit:	4d3b3ef
Status:	✅  Deploy successful!
Preview URL:	https://dfcb3293.atlantis.pages.dev
Branch Preview URL:	https://scott-t-pr-task.atlantis.pages.dev

View logs