[Question] ELITEA-1796–1802: contradictory metadata (automation_test_id set, status: draft)

[bermudas]

Context: intake run over EliteaAI/onetest-ai-tm-Elitea → tests/automated-full-regression-ui/support-assistant/ (2026-07-10).

7 cases in this run have contradictory metadata: execution_type: automated and a non-empty automation_test_id, but status: draft (not ready). Per the intake mission's rule, a case like this is not guessed either way — not filed as a new card, not skipped as already-automated. Flagging for a human decision.

ID	Title	automation_test_id
ELITEA-1796	Launcher is visible and Support Assistant widget opens and closes	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantLauncher.test_launcher_is_visible_and_opens_widget
ELITEA-1797	Widget conversation state persists after close and reopen	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantLauncher.test_widget_state_persists_after_close_and_reopen
ELITEA-1798	Send message and receive AI response via Send button	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantMessaging.test_send_message_and_receive_response
ELITEA-1799	New Chat button creates fresh session and moves previous to history	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantNewSession.test_new_chat_creates_fresh_session
ELITEA-1800	History restore — open previous session and continue messaging	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantHistory.test_history_restore_and_continue_messaging
ELITEA-1801	Expand widget to full-view mode and collapse back	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantViewModes.test_expand_and_collapse_to_full_view
ELITEA-1802	Attach button is present and opens file picker in Support Assistant	tests.ui.support_assistant.test_support_assistant_smoke.TestSupportAssistantAttachments.test_attach_button_is_present_and_opens_file_picker

Possible readings:

1. Automation exists (automation_test_id populated, plausible test names in a real module path) but the TMS record's status field was never flipped to ready after the automation landed — a bookkeeping gap in the source repo, not a real automation gap. → status should be corrected to ready upstream.
2. The automation_test_id was pre-filled speculatively (e.g. planned test names before the code was written) and the automation doesn't actually exist yet. → these are still open automation work, and cards should be filed once confirmed.

Ask: can someone confirm whether tests/ui/support_assistant/test_support_assistant_smoke.py (or equivalent) exists and passes for these 7 cases? If yes, please flip status: ready in the source .md files. If no, tell intake to file these as regular automation cards next run.

Filed by intake automation (Tal), 2026-07-10. All 7 cases skipped this run pending the answer — no cards filed, no automated-coverage assumed.