Add py-review-orchestrator agent configuration

[SatoryKono]

Added the py-review-orchestrator.md agent configuration file for hierarchical code review within BioETL. Ensure it references version v5.22 to maintain sync with the latest rules version. Regenerated architecture dependency map docs to satisfy the test_architecture_dependency_docs_drift.py drift test after testing.

---

PR created automatically by Jules for task 1743739128730836516 started by @SatoryKono

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6306a09e4b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Align orchestrator prompt with active RULES.md version

This change hard-codes v5.22 in the orchestrator metadata, but the repository’s canonical rules document is v5.23 (docs/00-project/RULES.md:3), so reviewers using this prompt will be instructed to audit against an outdated policy set and may miss or misclassify issues introduced in 5.23. The same stale version appears in multiple sections of this file, so the prompt is now internally consistent but externally out of sync with the actual project rules.

Useful? React with 👍 / 👎.

[SatoryKono]

Closing: stale docs/reports/audit branch, content outdated.