Type of Change

• New Feature
• Bug Fix
• Documentation
• Performance Improvement
• Test/CI
• Refactor
• Other:

Related Issues

Summary of Changes

Problem

The audit system currently transitions to AuditSystemState::Starting immediately upon entering the start() method, before validating that any targets exist. This causes a brief state inconsistency when the configuration contains no enabled targets.

Solution

This PR modifies the state machine logic to:

1. Create targets from configuration first
2. Check if the target list is empty
3. Only transition to Starting state if targets exist
4. Return early with Ok(()) and keep Stopped state when no targets are found

Changes

• File: crates/audit/src/system.rs
• Move state transition (*state = AuditSystemState::Starting) after target creation
• Add early return when targets.is_empty()
• Add informative log message for zero-target scenario

Testing

• System remains in Stopped state when no targets configured
• Normal startup proceeds when valid targets exist
• State consistency maintained across edge cases

Impact

• Prevents misleading state transitions
• Improves observability and debugging
• No breaking changes to public API

Checklist

• I have read and followed the CONTRIBUTING.md guidelines
• Passed make pre-commit
• Added/updated necessary tests
• Documentation updated (if needed)
• CI/CD passed (if applicable)

Impact

• Breaking change (compatibility)
• Requires doc/config/deployment update
• Other impact:

Additional Notes

Thank you for your contribution! Please ensure your PR follows the community standards (CODE_OF_CONDUCT.md) and sign the CLA if this is your first contribution.