Compliance controls should auto-update on scan completion instead of 12-hour intervals

Problem

Compliance controls currently update on a 12-hour interval schedule. This creates a delay between when security scans complete and when compliance status is reflected in the compliance framework, leading to:

• Stale compliance data that doesn't reflect current project state
• Confusion when scans complete successfully but compliance status shows as failing
• Need for manual workarounds (unassigning/reassigning frameworks) to trigger updates

Proposal

Update compliance controls automatically when security scans complete, rather than waiting for the scheduled 12-hour interval. This would provide:

• Real-time compliance status updates
• Immediate feedback when security scans complete
• Reduced confusion about compliance state
• Elimination of manual workaround needs

Current Workaround

Users can manually trigger a compliance scan by unassigning and reassigning the compliance framework (takes ~5 minutes to run).

Related Issues

• #579849 (closed) - Compliance controls should show success/failed based on scan completion regardless of pipeline status

Benefits

• More accurate, real-time compliance reporting
• Better user experience with immediate feedback
• Reduced support burden from compliance status confusion
• Alignment with user expectations for modern CI/CD systems