OCPBUGS-74178: Direct AI agents to AGENTS.md documentation hub

[sg00dwin]

Update CLAUDE.md and .cursor/context.md and .coderabbit.yaml to direct AI agents to our primary entry point AGENTS.md and its linked documentation files for code generation.

Summary by CodeRabbit

• Chores
  • Restructured internal AI context and configuration documentation. Consolidated AI guidance references and updated documentation file organization. No changes to application functionality or user-facing features.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes reorganize the AI context structure by removing the .ai/ directory's documentation (README.md and context.md) and redirecting AI assistant configurations to a new primary entry point at AGENTS.md. The .cursor/context.md and CLAUDE.md files are updated to reference AGENTS.md instead of .ai/context.md, adding mandatory startup instructions and cross-references to additional documentation files (ARCHITECTURE.md, CONVENTIONS.md, TESTING.md, README.md, CONTRIBUTING.md, STYLEGUIDE.md, INTERNATIONALIZATION.md). No functional code or runtime logic is affected; these are purely documentation and configuration changes for AI assistants.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title accurately summarizes the main change: redirecting AI agents from scattered .ai/ and .cursor/ documentation to a centralized AGENTS.md hub.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

---

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

[openshift-ci-robot]

@sg00dwin: This pull request references Jira Issue OCPBUGS-74178, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @yapei

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Update CLAUDE.md and .cursor/context.md to direct AI to our primary entry point AGENTS.md and its linked documentation files for code generation.

Summary by CodeRabbit

• Chores
• Restructured internal AI context and configuration documentation. Consolidated AI guidance references and updated documentation file organization. No changes to application functionality or user-facing features.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

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 openshift-eng/jira-lifecycle-plugin repository.

[jhadvig]

/lgtm
/approve

[jhadvig]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhadvig, sg00dwin

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 [jhadvig]

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

[logonoff]

could we symlink context.md and CLAUDE.md to AGENTS.md to reduce duplicate documentation?

[sg00dwin]

/test e2e-gcp-console

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2998cf8 and 2 for PR HEAD bab5a40 in total

[sg00dwin]

/test e2e-gcp-console

[openshift-ci]

@sg00dwin: 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.