[MAJOR] Skills list search does not filter the visible list — it's a navigate-away typeahead instead

[bermudas]

[MAJOR] Skills list search does not filter the visible list — it's a navigate-away typeahead instead

Found while working #127 (ELITEA-1739 "Search Skills by Name" test-case analysis)

Environment: https://next.elitea.ai/app/skills/all (and ?view=table), Chromium, account alita@elitea.ai

Preconditions: 3 skills exist: formatter, code-reviewer, content-writer (see note on naming below)

Steps:

1. Navigate to Skills (/app/skills/all), either Card view or Table view.
2. Type a partial/exact skill name into the "search" textbox (placeholder "Let's find something amazing!") in the right-hand Tags/search panel.
3. Observe the main Skills list/grid (or table) while typing.
4. Optionally click one of the autocomplete suggestions that appears in the floating tooltip under the search box.

Expected (per ELITEA-1739): The Skills list itself re-renders to show only the skills matching the search term — partial match, exact match, and an in-list empty state for non-matching terms, restoring the full list when the search is cleared.

Actual:

• The search box is a typeahead/omnisearch — it opens a floating tooltip listing matching skill names (and a "Tags" section), but the main Skills list/table is never filtered. It stays at "1 - 3 of 3" (table view) / all 3 cards (card view) regardless of the query.
• Clicking a suggestion in the tooltip navigates away to that single skill's own detail page (/app/skills/all/<id>?viewMode=owner&name=<name>) rather than filtering the list in place to show just the matches.
• For a non-existent name, the tooltip shows "No Skills Match" — but again this is inside the floating tooltip, not an in-list empty state; the underlying list/table is still showing all 3 skills.
• Additionally, typing fewer than 3 characters (e.g. the case's own partial-search example "Co") triggers a toast: "The search key word should be at least 3 letters long" and produces no suggestions at all — so even the typeahead can't reproduce the case's literal 2-character example.

Evidence:

• test-results/screenshots/ELITEA-1739-step2-search-ter-list-unfiltered.png — query "ter" (3 chars) shows a tooltip with only content-writer and formatter suggested, while the table below still reads "1 - 3 of 3" and lists all 3 rows including code-reviewer.
• test-results/screenshots/ELITEA-1739-step2-min3char-toast.png — query "co" (2 chars) triggers the "at least 3 letters long" toast instead of any filtering/suggestion.
• No console errors observed during any of the above (checked via browser_console_messages).

Frequency: Always — reproduced consistently in both Card view and Table view.

Workaround: None for "filter the list in place." The typeahead can be used to jump directly to a single known skill, but that's a different feature than "search/filter the list."

Note on test data: The case's example skill names ("Formatter", "Code Reviewer", "Content Writer") contain spaces/mixed case, which the live product's Skill "Name" field rejects — Name is enforced as lowercase letters/digits/hyphens only (validation message: "Name must be lowercase letters, digits and hyphens only (no spaces), and cannot start or end with a hyphen"). This is flagged separately as a clarification against the case text (see ELITEA-1739 AFS), not filed as a second defect — it's a naming-convention drift, not a functional bug.

[bermudas]

Confirmed resolved: re-verification found the missing interaction step was pressing Enter after typing into the search box — once done, the main Skills list correctly filters (partial/exact/non-existent/clear all confirmed live, with network + DOM evidence). This was an analysis gap in the original AFS pass (Enter was never pressed), not a real product defect. Closing as invalid/analysis-gap. Automated in #130 (merged).