After the cooldown elapses and forceDisable() runs (VPN off + tamper-lock disarmed), Android's a11y service can't deactivate itself — surface a friendly Alert routing the user to Settings → Accessibility so they can finish removing protection. Wired into both the fetchState cooldown active→inactive transition and the AppState 'active' check; idempotent via ref. (Native side — disable() also disarms the tamper-lock, RebreakAccessibilityService goes fully passive when neither tamper-locked nor enabled, syncBlocklist no longer re-starts the VpnService when disabled — lives in the gitignored module/android dir, not committed here.) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Description
Self-hosted mirror of rebreak monorepo
Languages
TypeScript
68%
Vue
7.9%
Swift
7.7%
Shell
4.2%
JavaScript
3.1%
Other
8.9%