CAMEL-21975: Add route-diagram command to display Camel route diagrams in terminal

.github/workflows/pr-doc-validation.yml

@@ -22,6 +22,7 @@ on:
       - main
     paths:
       - '**.adoc'
+      - 'docs/**/*'
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}

.github/workflows/pr-manual-component-test.yml

@@ -40,7 +40,7 @@ jobs:
           persist-credentials: false
           submodules: recursive
       - name: Check Permission
-        uses: actions-cool/check-user-permission@7b90a27f92f3961b368376107661682c441f6103
+        uses: actions-cool/check-user-permission@c21884f3dda18dafc2f8b402fe807ccc9ec1aa5e
       - name: Retrieve sha
         id: pr
         env:

.mvn/extensions.xml

@@ -8,7 +8,7 @@
     <extension>
         <groupId>eu.maveniverse.maven.nisse</groupId>
         <artifactId>extension</artifactId>
-        <version>0.7.0</version>
+        <version>0.8.1</version>
     </extension>
     <extension>
         <groupId>com.gradle</groupId>

AGENTS.md

@@ -7,7 +7,7 @@ Guidelines for AI agents working on this codebase.
 Apache Camel is an integration framework supporting routing rules in Java, XML and YAML DSLs.
 
 - Version: 4.19.0-SNAPSHOT
-- Java: 21+
+- Java: 17+
 - Build: Maven 3.9.12+
 
 ## AI Agent Rules of Engagement
@@ -56,11 +56,12 @@ When creating a PR, **always identify and request reviews** from the most releva
 - Run `git log --format='%an' --since='1 year' -- <affected-files> | sort | uniq -c | sort -rn | head -10`
   to find who has been most active on the affected files.
 - Use `git blame` on key modified files to identify who wrote the code being changed.
-- Cross-reference with the [committer list](https://camel.apache.org/community/team/#committers)
+- Cross-reference with the [committer list](https://home.apache.org/committers-by-project.html#camel)
   to ensure you request reviews from active committers (not just contributors).
 - For component-specific changes, prefer reviewers who have recently worked on that component.
 - For cross-cutting changes (core, API), include committers with broader project knowledge.
 - Request review from **at least 2 relevant committers** using `gh pr edit --add-reviewer`.
+- When all comments on the Pull Request are addressed (by providing a fix or providing more explanation) and the PR checks are green, re-request review on existing reviewers so that they are aware that the new changeset is ready to be reviewed.
 
 ### Merge Requirements
 
@@ -75,6 +76,29 @@ When creating a PR, **always identify and request reviews** from the most releva
 - All code must pass formatting checks (`mvn formatter:format impsort:sort`) before pushing.
 - All generated files must be regenerated and committed (CI checks for uncommitted changes).
 
+### Asynchronous Testing: Use Awaitility Instead of Thread.sleep
+
+Do **NOT** use `Thread.sleep()` in test code. It leads to flaky, slow, and non-deterministic tests.
+Use the [Awaitility](https://github.com/awaitility/awaitility) library instead, which is already
+available as a test dependency in the project.
+
+**Example — waiting for a route to be registered:**
+
+```java
+import static org.awaitility.Awaitility.await;
+
+await().atMost(20, TimeUnit.SECONDS)
+       .untilAsserted(() -> assertEquals(1, context.getRoutes().size()));
+```
+
+**Rules:**
+
+- New test code MUST NOT introduce `Thread.sleep()` calls.
+- When modifying existing test code that contains `Thread.sleep()`, migrate it to Awaitility.
+- Always set an explicit `atMost` timeout to avoid hanging builds.
+- Use `untilAsserted` or `until` with a clear predicate — do not replace a sleep with a
+  busy-wait loop.
+
 ### Issue Investigation (Before Implementation)
 
 Before implementing a fix for a JIRA issue, **thoroughly investigate** the issue's validity and context.