1. What is the nature and description of the request?

When Event-Driven Ansible (EDA) imports a project, rulebooks that fail validation are silently ignored. If a rulebook contains a validation error (for example, a missing required condition in a rule), the project sync completes successfully, but the rulebook:

  * Is not available for selection during rulebook activation creation;
  * Produces no explicit validation error or warning in the UI

From a user perspective, the project appears to contain no rulebooks, even though rulebook files are present and correctly synchronized from Git. There is currently no indication that rulebook parsing or validation failed, nor any information about what is wrong with the rulebook.

This enhancement requests that EDA explicitly surface rulebook validation failures and provide actionable feedback to users.

2. Why does the customer need this? (List the business requirements here)

• Avoid Silent Failures as they obscure the true cause of missing rulebooks and lead to unnecessary investigation;
• 
  Reduce Time to Resolution - customers spend time troubleshooting project layout, Git sync, or EDA configuration instead of addressing rulebook content errors;
• 
  Improve Usability and Developer Experience as clear validation feedback is critical for efficient rulebook development;

3. How would you like to achieve this? (List the functional requirements here)

• Detect and Track Rulebook Validation Failures - rulebooks discovered during project import that fail validation must be explicitly tracked as invalid, rather than silently ignored;
• Expose Validation Status in the UI - the project sync or project details view should indicate when:
  •  Rulebooks were found;
  • One or more rulebooks failed validation;
• Provide Actionable Error Details - validation feedback should include:
  • Rulebook file name
  • Rule name
  • Clear validation errors (e.g., “Missing required field: condition”)
• Improve Rulebook Activation Workflow - during rulebook activation creation or editing:
  • Projects with invalid rulebooks should not appear empty
  • Users should be informed that rulebooks exist but are unavailable due to validation errors