[History] Add filtering, diagnostics, retry, and retention controls

[emi-ran]

Feature

Upgrade execution history into useful diagnostics.

Scope

• Filter by trigger, status, rule, and failures-only.
• Rule detail exposes its own history.
• Support retrying one eligible failed action with explicit capability check and confirmation; never replay unsafe actions blindly (calls, SMS, webhooks, clipboard) without product-approved safeguards.
• Add a "Why did this rule not run?" diagnostic that evaluates trigger receipt, enabled state, conditions, cooldown, conflicts, capability, and listener registration using safe summaries.
• User-configurable retention: 100, 500, or unlimited records. Unlimited requires bounded storage monitoring/clear-history control and documented impact.

Security and privacy

History and diagnostics must retain existing redaction: no phone numbers, webhook URL/headers/body, credential, notification/SMS content, clipboard text, or raw sensitive exception text.

Acceptance criteria

• Filters are composable, fast, persisted only if desired, and have empty states.
• Diagnostic says "unknown/not observed" instead of inventing cause.
• Retry eligibility is explicit and unsafe actions are excluded by default.

Verification

• Repository retention/pruning tests; filter/query tests; redaction regression tests; UI tests for no-result and explanations.
• Device smoke test with successful, failed, cooldown-suppressed, and permission-denied runs.