Enhance test, and remove noise from README

Author: kabir

boms/README.md

@@ -140,16 +140,8 @@ Add to your project's `pom.xml`:
 
 ## Internal Project Usage
 
-**Important:** The A2A Java SDK project itself does **NOT** import these BOMs in the parent `pom.xml`.
-
-### Why Not Use BOMs Internally?
-
-Following the WildFly pattern, we keep BOMs separate from internal dependency management for several reasons:
-
-1. **Build Order Complexity**: BOMs must be built before other modules, adding reactor ordering constraints
-2. **Flexibility**: Parent pom may need different scopes/configurations than external users
-3. **Simplicity**: Avoids potential circular dependencies and build complexity
-4. **Single Source of Truth**: Parent `pom.xml` remains authoritative for internal builds
+**Important:** The A2A Java SDK project itself does **NOT** import these BOMs in the parent `pom.xml`. The BOMs are 
+for the convenience of external users. 
 
 ### Maintenance Strategy
 
@@ -235,44 +227,4 @@ The BOMs use `${project.version}` for all A2A SDK modules, ensuring:
 - Version updates only need to change parent pom
 - No version drift between BOMs and SDK modules
 
-## Build Order
-
-BOMs have explicit dependencies to ensure correct reactor build order:
-- **SDK BOM** builds first (no BOM dependencies)
-- **Extras BOM** builds second (depends on SDK BOM)
-- **Reference BOM** builds third (depends on SDK BOM)
-
-Maven's reactor automatically orders them correctly based on their `<dependencies>` declarations, regardless of their position in the parent pom's `<modules>` section.
-
-## Examples
-
-See the `examples/` directory for sample projects using these BOMs:
-- `examples/helloworld/` - Basic agent using SDK BOM
-- `examples/cloud-deployment/` - Quarkus-based agent using Reference BOM
-
-## Release Process
-
-When releasing the A2A Java SDK:
-
-1. All three BOMs are released as separate Maven artifacts
-2. External users can depend on them via Maven Central
-3. BOMs follow the same version scheme as the SDK (e.g., `0.4.0.Alpha1`, `0.4.0`)
-
-## Questions?
-
-- **Which BOM should I use?**
-  - Quarkus project → Reference BOM
-  - Production server with database/distributed features → Extras BOM
-  - Other framework/basic agent → SDK BOM
-
-- **Can I use Extras BOM with Spring Boot?**
-  - Yes! Extras BOM imports SDK BOM and adds server enhancements that work with any framework.
-
-- **Can I use Reference BOM with Spring Boot?**
-  - Yes, but you'll get unnecessary Quarkus dependencies. Use SDK BOM or Extras BOM instead.
-
-- **Do I need multiple BOMs?**
-  - No, choose one. Extras BOM imports SDK BOM. Reference BOM imports SDK BOM.
-
-- **Why are test dependencies in SDK BOM?**
-  - Test scope dependencies don't pollute runtime, but allow users to easily import test utilities.
+Maven's reactor automatically orders them correctly based on their `<dependencies>` declarations, regardless of their position in the parent pom's `<modules>` section.

boms/test-utils/src/main/java/io/a2a/bom/test/DynamicBomVerifier.java

@@ -43,15 +43,11 @@ public void verify() throws Exception {
         Set<String> requiredClasses = discoverRequiredClasses(projectRoot);
         Set<String> forbiddenClasses = discoverForbiddenClasses(projectRoot);
 
-        // Do some sanity checks for some classes from both top-level and nested modules to make sure the
-        // discovery mechanism worked properly
-        sanityCheckDisovery("io.a2a.spec.AgentCard", requiredClasses);
-        sanityCheckDisovery("io.a2a.server.events.EventConsumer", requiredClasses);
-        sanityCheckDisovery("io.a2a.client.transport.spi.ClientTransport", requiredClasses);
-
         System.out.println("Discovered " + requiredClasses.size() + " required classes to verify");
         System.out.println("Discovered " + forbiddenClasses.size() + " forbidden classes to verify");
 
+        sanityCheckDiscovery(requiredClasses, forbiddenClasses);
+
         List<String> failures = new ArrayList<>();
         int successful = 0;
 
@@ -98,8 +94,28 @@ public void verify() throws Exception {
         System.out.println("\n✅ BOM is COMPLETE - all required classes loaded, all forbidden classes not loadable!");
     }
 
-    private void sanityCheckDisovery(String className, Set<String> discovered) {
-        if (!discovered.contains(className)) {
+    private void sanityCheckDiscovery(Set<String> requiredClasses, Set<String> forbiddenClasses) {
+        // Do some sanity checks for some classes from both top-level and nested modules to make sure the
+        // discovery mechanism worked properly
+        sanityCheckDisovery("io.a2a.spec.AgentCard", requiredClasses, forbiddenClasses);
+        sanityCheckDisovery("io.a2a.server.events.EventConsumer", requiredClasses, forbiddenClasses);
+        sanityCheckDisovery("io.a2a.client.transport.spi.ClientTransport", requiredClasses, forbiddenClasses);
+
+        sanityCheckDisovery("io.a2a.server.common.quarkus.DefaultProducers", requiredClasses, forbiddenClasses);
+        sanityCheckDisovery("io.a2a.extras.common.events.TaskFinalizedEvent", requiredClasses, forbiddenClasses);
+        sanityCheckDisovery("io.a2a.extras.queuemanager.replicated.core.ReplicatedEventQueueItem", requiredClasses, forbiddenClasses);
+
+        // Make sure that the required and forbidden sets don't contain the same classes
+        Set<String> intersection = new HashSet<>(requiredClasses);
+        intersection.retainAll(forbiddenClasses);
+        if (!intersection.isEmpty()) {
+            System.err.println("The following classes appear in both the required and forbidden sets: " + intersection);
+            System.exit(1);
+        }
+    }
+
+    private void sanityCheckDisovery(String className, Set<String> requiredClasses, Set<String> forbiddenClasses) {
+        if (!requiredClasses.contains(className) && !forbiddenClasses.contains(className)) {
             System.err.println("Class expected to be on the classpath was not discovered: " + className);
             System.exit(1);
         }