TalkBack, 4 of 10: Improve routing rule accessibility

[eliotcougar]

Summary

Part 4 of the TalkBack series makes routing rules one accessible toggle per row. The row exposes its name and routing destination, its observable enabled state, and named custom actions. Visible Edit/Delete buttons remain usable by touch and keyboard but do not create separate TalkBack action targets; the visual switch is controlled by the row.

Interaction

• Preserve native toggle semantics and checked-state events. The row's activation label changes between Enable rule and Disable rule.
• Expose Edit [name] first, Delete [name] second, followed by the currently valid Move to top / Move up / Move down / Move to bottom actions.
• Use the shared polite live-region feedback for successful move actions. Toggle feedback comes from native checked-state changes, without an unconditional announcement after each tap.
• Describe built-in block and direct routes using localized text. Other tags retain their actual case-sensitive identity; Direct, for example, is not the built-in direct tag.
• Omit the raw matching conditions from row speech and include a localized locked marker where applicable.
• Both the row custom Delete action and the visible Delete button open the same named confirmation. The editor's confirmation is named as well.

State and scope

• Use rule IDs for pending deletion, row actions and reorder identity. Keep the pending delete ID with rememberSaveable so recreation preserves the target. Do not show a nameless confirmation when its target no longer exists.
• Resolve an editor position immediately before navigation to fit current upstream's position-based editor contract. This PR does not reintroduce the separate routing-storage/API migration.
• Resolve list deletion against freshly loaded persisted rules by ID, perform its storage work on Dispatchers.IO, and remove that ID from the observable list after completion. Failures are logged and use the existing error feedback.
• Remove the obsolete deletion result wrapper and its wrapper-only tests. Keep the routing row private and require real reorder callbacks instead of test-only defaults.
• Remove the old isolated Android test harness. No new Android test source set or test folder is introduced.
• Keep shared feedback/reorder code and catalog entries aligned with the companion accessibility PRs, including the existing selected/select translations and Bakhtiari corrections. Do not split XML catalogs.

The branch includes the shared live-region renderer needed for move feedback, not the complete toast/service-notification layer from Part 1. It does not include the subscription, asset, per-app, settings, navigation or server-list feature changes from the other parts.

Localization

Routing summaries, enabled/disabled states, action labels, named confirmations and move feedback are covered in English, Arabic, Bengali, Bakhtiari, Persian, Russian, Vietnamese, Simplified Chinese and Traditional Chinese. Russian uses the pinned/preserved sense, «Закреплено», for the lock marker to distinguish it from blocked traffic. Actual outbound tags are configuration identities and are not translated.

TalkBack controls the precise ordering and wording of native role/state output; this PR does not suppress those semantics or force accessibility focus.

Validation

• Play Store debug JVM suite: 78 tests, no failures or errors.
• Kotlin compilation and Play Store debug x86_64 APK assembly pass.
• All nine locale catalogs contain the 17 routing/reorder keys with matching placeholders.
• Non-checkout merge checks against each of the other nine focused branches pass in both orders and produce equal result trees.
• Android 17 / Pixel 9 Pro emulator: native checked state and Enable/Disable labels update on the same focused row; custom Edit opens the named rule; Move down retains row focus and persists after reopening; custom Delete shows the correct name after reordering and rotation. Exact Direct remains a custom destination while built-in direct and block retain their localized summaries.
• The device checks use the real application screen and an external temporary native-node probe, not setContent replacement screens. The probe is not part of the PR.

Not run

• Recorded TalkBack audio and every locale's speech-engine pronunciation. Native node state, actions and focus were inspected with TalkBack bound; that is not an audio transcript.
• Exhaustive keyboard/D-pad action traversal, storage-failure injection and concurrent storage-writer stress scenarios. No dedicated JVM persistence test seam was added solely for this cleanup.

Validation above was performed on the reviewed code ending at 67cbe2ac4 on 2026-09-05. The emulator's original APK and settings were restored, the temporary rule and external probe were removed, and the existing lab subscription was preserved.