Fixed AI agents missing previously downloaded cache.

[AlexSkrypnyk]

Summary by CodeRabbit

• Documentation
  • Updated development guidelines with new task initialization guidance and critical command usage rules.

[coderabbitai]

Walkthrough

Documentation update to AGENTS.md adding guidance for checking cached documentation, project conventions, and fetching external docs before task investigation. Additionally extends critical rules with specific Drupal command preferences for config exports and script execution.

Changes

Cohort / File(s)	Summary
Documentation & Guidance AGENTS.md	Added "Before Starting Any Task" guidance block with cached docs lookup, project docs reference, and external docs fetching instructions. Extended critical rules with preferences for ahoy drush php:script over php:eval and config export requirements via ahoy drush cex.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Added support for all AI agents + docs. #2272: Modifies AGENTS.md with AI-docs caching guidance and .data/ai-artifacts behavior.
• Updated AI instructions. Part 2. #1980: Updates AI instruction documentation with cached docs lookup directives.

Poem

🐰 A rabbit hops through guidance new,
Cached docs and rules, both tried and true,
Before each task, a checklist bright,
Config exports done just right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title mentions 'missing cache' but the summary shows the changes add a guidance block to check cached docs and cache from docs source—improving the cache checking process, not fixing something that was previously missing.	Revise the title to accurately reflect the actual changes, such as 'Add AI agent guidance for checking and caching documentation' or similar phrasing that describes what was added.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/improve-agentic-instructions

---

_{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 the current code and only fix it if needed.

Inline comments:
In `@AGENTS.md`:
- Line 65: Update the rule that currently reads "Never modify `scripts/vortex/`
- use `scripts/custom/` for your scripts" to clarify scope: state that
downstream projects should never modify `scripts/vortex/` and must use
`scripts/custom/`, but for the template repository (e.g., drevops/vortex)
modifications to `scripts/vortex/` are expected and allowed for maintenance;
reference the `scripts/vortex/` and `scripts/custom/` paths and explicitly call
out "template repo (drevops/vortex)" so reviewers understand the exception.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Clarify the scripts/vortex/ rule for the template repo.

In the template repository, modifying scripts/vortex/ is expected for maintenance. The current blanket prohibition is misleading here. Consider scoping it to downstream projects instead.

✏️ Suggested wording

-- **Never modify** `scripts/vortex/` - use `scripts/custom/` for your scripts
+- **Downstream projects:** do not modify `scripts/vortex/`; use `scripts/custom/` instead.  
+- **Template repo (this repo):** updates to `scripts/vortex/` are allowed for template maintenance.

Based on learnings: “The drevops/vortex repository is the template source itself. When reviewing PRs in drevops/vortex, modifications to scripts/vortex/ are expected and correct…”

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 65, Update the rule that currently reads "Never modify
`scripts/vortex/` - use `scripts/custom/` for your scripts" to clarify scope:
state that downstream projects should never modify `scripts/vortex/` and must
use `scripts/custom/`, but for the template repository (e.g., drevops/vortex)
modifications to `scripts/vortex/` are expected and allowed for maintenance;
reference the `scripts/vortex/` and `scripts/custom/` paths and explicitly call
out "template repo (drevops/vortex)" so reviewers understand the exception.

[AlexSkrypnyk]

Code Coverage Report:
  2026-02-20 01:48:22

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

[github-actions]

Code Coverage Report:
  2026-02-20 01:48:24

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

[AlexSkrypnyk]

Code Coverage Report:
  2026-02-20 01:51:46

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)

[AlexSkrypnyk]

Code Coverage Report:
  2026-02-20 01:52:08

 Summary:
  Classes:  0.00% (0/1)
  Methods:  0.00% (0/2)
  Lines:   94.65% (177/187)