fix: treat only home-action skills as launcher abilities

[tonycoder-hub]

Problem

get_app_abilities() decides isLauncherAbility with:

if len(skills) > 0 or "action.system.home" in skills[0]["actions"]:

Two bugs:

• or marks every ability with a non-empty skills list as a launcher.
• Empty skills evaluates skills[0] → IndexError → the ability is silently skipped.

That list feeds get_app_main_ability() / start_app() when page_name is omitted, so the wrong ability can be chosen.

Fix

if len(skills) > 0 and "action.system.home" in (skills[0].get("actions") or []):

Only the home action is treated as a launcher. Empty or missing actions is safe.

Tests

Device-free unit tests in tests/test_app_abilities.py use a fixture bm dump JSON covering:

• empty skills — ability is kept, isLauncherAbility is false
• skills without action.system.home — not a launcher
• skills with action.system.home — launcher, and get_app_main_ability() prefers it

pytest tests/test_app_abilities.py

No Harmony device required.