signals from both proactive sources (scheduled security scans, UI regression runs, mutation testing, health checks) and reactive sources (user reviews, support tickets, app store ratings, meeting notes, production metrics) flow through automated triage into typed task creation. Both sources contribute; neither is manually gated. The proactive-source path depends on an agent-invokable scheduling primitive — scored here rather than as its own criterion, but load-bearing for `PL2-test-quality`, `PL2-ui-test-coverage`, `PL2-load-stress-testing`, `PL4-release-strategy`, `PL5-pipeline-reliability`, `PL5-outcome-input-loop` as well