Add risk level rubric to AGENTS.md

[xrajesh]

Adds a Risk Levels section to AGENTS.md defining risk 1/2/3 classification with repo-specific examples and Jira description format.

Summary by CodeRabbit

• Documentation
  • Added a "Risk Levels" section describing risk classification for Jira create/edit actions, how classifications are applied, and where to find the assessment rubric and classification examples in the reference documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 76edd3ad-872c-48a7-8228-d8a0f9fe191d

📥 Commits

Reviewing files that changed from the base of the PR and between 642a104 and 6d7b174.

📒 Files selected for processing (1)

• AGENTS.md

---

📝 Walkthrough

Walkthrough

Adds a new "Risk Levels" section to AGENTS.md stating that risk classification is enforced via a PreToolUse hook before Jira create/edit operations and linking to the external lightspeed-team-harness risk-rubric.md for the rubric and examples.

Changes

Risk Levels Documentation

Layer / File(s)	Summary
Risk Levels section AGENTS.md	Inserted a "Risk Levels" section noting PreToolUse enforcement for Jira create/edit operations and referencing lightspeed-team-harness's risk-rubric.md for the rubric and classification examples.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding risk level documentation to AGENTS.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@AGENTS.md`:
- Line 168: The fenced code block that contains "## Risk Level" is missing a
language tag (triggers markdownlint MD040); update the opening fence from ``` to
```md so the block is explicitly marked as markdown (e.g., change the fence
around the "## Risk Level" snippet to use ```md) to satisfy the linter.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 34ce0d2c-2f6f-4913-92a6-4a6db108be19

📥 Commits

Reviewing files that changed from the base of the PR and between 072dc67 and 642a104.

📒 Files selected for processing (1)

• AGENTS.md

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@xrajesh: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.