fix: restore Aura emulator discovery and control

[daniele21]

Outcome

Restore truthful Aura↔Harnex emulator control for the independently signed two-APK lane.

Two independent fixture defects were exposed by Aura W10:

• the emulator-only shell bridge handled Room-backed control-plane commands synchronously from BroadcastReceiver.onReceive(), causing Cannot access database on the main thread;
• the phone-test manifest did not declare Aura release/debug packages in <queries>, so Android package visibility hid Aura from Harnex startup discovery and the Aura schema/category assignments were never seeded.

Repair

• run the shell-only DUMP bridge command after goAsync() on a short-lived background thread and fail closed on handler exceptions;
• declare com.staituned.aura and com.staituned.aura.debug as package-visibility queries alongside RedactGuard;
• add a unit regression proving observed Aura package aliases seed both Aura use-case specs as PENDING with package-bound signer identities.

Boundary / invariants

• Production Binder/runtime/control-plane semantics are unchanged.
• The shell bridge remains emulator-only, android.permission.DUMP protected and absent from production variants.
• Aura remains independently signed and starts PENDING; explicit authorization is still required before live Binder trust.
• Package and signer matching remain exact; the manifest query only makes the installed package observable to Harnex.
• No cloud fallback or content logging is introduced.

Validation

Candidate: fae66fc0c495f184944c3ffc905eeb0dbc595f2c, base dev@d60c0ff9560d6eed225e4fd6e02e746f18625935.

Repository health is green. Selector-owned remote preflight /preflight auto is running at integration/strong because the Android manifest/package boundary changed. The discriminating acceptance gate remains Aura API 36 two-APK execution against this exact Harnex candidate with Aura's hardened AndroidJUnitRunner parsing.

[daniele21]

/preflight auto

[daniele21]

/preflight auto

[daniele21]

Superseded by #567, which reapplies the same 3-file regression repair on the current dev release-candidate baseline. Keeping this stale-base PR out of the release path.