feat: add node branch for single-shot sms/email compose

[mikejgray]

Summary

This PR lets a Node send a text or email by voice, in one turn — no back-and-forth. It adds a Node branch to handle_send_sms and handle_send_email, checked before the existing mobile draft-and-confirm flow. The branch reads the recipient, subject, and body already extracted by CMS_match_message_phrase, then calls the shared helper in NeonGeckoCom/neon-utils#568 to check support, dispatch, and speak the result. A Node request never enters the mobile draft state.

Spoken text for these actions lives in this skill's dialog files: the same four native_action_* dialogs as skill-launcher#54, plus launch_sms_app.dialog and launch_email_app.dialog holding the spoken name of each action. The shared helper has no built-in fallback text; a missing file gets the standard OVOS behavior of speaking the key.

This PR also adds test/test_skill.py, the first unit tests for this skill. The requirements/test.txt and test extra it originally introduced landed upstream in #29 and are no longer part of this diff.

Test plan

• 11 unit tests pass, including a check that the existing mobile SMS path still works and never touches the new Node branch.
• Resource tests (3) and intent tests (4) from Add intent and resource tests #29 pass locally on this branch via minerva. The six new dialog files are registered in test/test_resources.yaml.
• End-to-end test against a live Hub: not yet passing. See below.

End-to-end status: blocked

Live testing found two problems upstream of this PR's code, in how the utterance reaches this skill at all.

Text messages. The phrase "send a text to X that says Y" should match skill-communication's SendMessageIntent — it has both a trigger word (send) and a content word (text). In testing it did not match anything, and fell through to the fallback LLM skill instead. This needs investigation in skill-communication, a different repo.

Email. The phrase "draft an email to X about Y" matched DraftEmailIntent, a skill-messaging intent, instead of going through CMS_match_message_phrase as expected. DraftEmailIntent only checks for the words "draft" and "email" — it does not read a recipient or subject from the utterance, because it was built to start the mobile draft flow, not to fill in Node fields directly. So it wins the match and hands the new Node branch an empty result. The branch handles that correctly — it speaks an error instead of failing silently — but the wrong intent is answering the request.

Neither of these is a bug in this PR's code: the dispatch and error-handling logic behaves correctly given what it receives. The Node branch cannot be called end-to-end validated until these two matching problems are fixed.

CI note

requirements.txt floors neon-utils at 1.14.2a5 (the alpha published from NeonGeckoCom/neon-utils#568) and neon-data-models at 0.0.3a2 (the first prerelease with NodeNativeAction). Neither spec resolved a prerelease before. skill.json carries the same specs so the update-skill-json workflow has nothing to push.

This PR turns on the skill_unit_tests job in the test workflow, per review, so test/test_skill.py runs in CI alongside the intent and resource jobs enabled in #29.

Rebased onto dev after #29 (2026-09-16); the only conflict was the test workflow, resolved with all three test jobs enabled.

Depends on NeonGeckoCom/neon-utils#568.

[NeonDaniel]

CI shows all green, but this repo's test workflow has skill_unit_tests, skill_intent_tests, and skill_resource_tests commented out — already true on dev, not something this PR changed. So the new test/test_skill.py never runs in CI. Green here means no tests ran, not that tests passed.

This PR is defining unit tests where none existed previously. Please, un-comment the skill_unit_tests automation since there are valid tests to run now