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 development guide introducing Risk Levels and how they are applied to Jira create/edit operations, with detailed risk rubrics and classification examples in an external reference.
  • Clarified change-classification expectations, review guidance, standardized Jira ticket format, and related documentation requirements.

[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: 1433a3a8-f9d6-4078-be15-cb9903bb3905

📥 Commits

Reviewing files that changed from the base of the PR and between eb6b658 and 67c12b6.

📒 Files selected for processing (1)

• AGENTS.md

---

📝 Walkthrough

Walkthrough

Adds a new AGENTS.md development guide with a Risk Levels section that notes risk levels are enforced via a PreToolUse hook before Jira create/edit calls and points to lightspeed-team-harness/hooks/risk-rubric.md for detailed rubrics and examples.

Changes

Development Guidelines and Risk Rubric

Layer / File(s)	Summary
Risk levels and enforcement note AGENTS.md	Adds AGENTS.md with the guide title, a Risk Levels section, and explanation that risk levels are enforced via a PreToolUse hook; references lightspeed-team-harness/hooks/risk-rubric.md for rubrics and examples.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 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 pull request title directly summarizes the main change: adding a risk level rubric to AGENTS.md, which aligns with the file changes and PR objectives.
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`:
- Around line 27-32: In the fenced code block under the "Risk Level" example,
add a language identifier to the opening triple-backticks (e.g., ```markdown or
```text) so the snippet is properly highlighted and passes markdown linting;
update the opening fence in that Risk Level block (the example containing "Risk
{1|2|3} — {one-line impact summary}" and "Rationale: {why this classification,
referencing the rubric}") to include the chosen language identifier.

🪄 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: 2afa4830-113d-487a-8d44-8fa16ab7326c

📥 Commits

Reviewing files that changed from the base of the PR and between 8ac45f7 and eb6b658.

📒 Files selected for processing (1)

• AGENTS.md

[xrajesh]

/approve

[xrajesh]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: xrajesh

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [xrajesh]

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

[joshuawilson]

/lgtm