feat: split screen intelligence from accessibility and add dedicated settings

[senamakel]

Summary

• Introduced screen_intelligence as a first-class feature area while preserving existing openhuman.accessibility_* RPC compatibility.
• Split Rust core module ownership so screen intelligence now lives under openhuman/screen_intelligence, with openhuman/accessibility as a compatibility re-export.
• Added screen-intelligence settings update flow (openhuman.update_screen_intelligence_settings) and config fields for policy mode and allowlist/denylist behavior.
• Kept accessibility and screen intelligence separate in settings UI by restoring Accessibility naming and adding a dedicated Screen Intelligence panel/route.
• Wired screen captures to active-window policy filtering and memory persistence under screen_intelligence category.

Problem

• The initial implementation mixed accessibility automation and screen intelligence into a single surfaced feature, creating product confusion and coupling.
• Screen intelligence needed to become a configurable core feature with independent policy controls for capture targeting.
• We needed this without breaking existing accessibility command paths already used by frontend and Tauri command bridges.

Solution

• Created a dedicated openhuman::screen_intelligence module and moved implementation ownership there.
• Kept backward compatibility by re-exporting from openhuman::accessibility and leaving openhuman.accessibility_* RPC methods in place.
• Added and connected openhuman.update_screen_intelligence_settings to persist and apply runtime config updates.
• Implemented policy controls (all_except_blacklist / whitelist_only) with allowlist + denylist matching.
• Added a standalone Screen Intelligence settings panel and route, while restoring Accessibility panel/menu labeling and behavior.

Testing

• yarn -s compile
• cargo check --manifest-path src-tauri/Cargo.toml
• Other checks run (list commands)
• Commands: npx prettier --check ., npx eslint ., npx tsc --noEmit, cargo fmt --manifest-path src-tauri/Cargo.toml, cargo check --manifest-path src-tauri/Cargo.toml
• Manual validation completed (list scenarios)

Impact

• Runtime impact: desktop-focused screen intelligence controls and capture behavior now have their own feature boundary.
• Compatibility: existing accessibility RPC command names remain functional; no immediate client migration required.
• Architecture: clearer separation between accessibility permissions/session controls and screen intelligence policy/config ownership.
• Data impact: screen-intelligence summaries are persisted under screen_intelligence memory category.

Breaking Changes

• None
• Yes (describe clearly, including migration steps)

Related

• Issue(s): n/a
• Follow-up PR(s)/TODOs: migrate remaining accessibility-labeled RPC names to explicit screen-intelligence names once clients are updated.