tui: two palette rows titled "Skills"; the default match inserts a slash command instead of opening the browser with Publish to workspace

[anandgupta42]

Summary

The command palette has two rows titled Skills:

• prompt.skills (category Prompt, packages/tui/src/component/prompt/index.tsx:593): opens a picker that inserts /skill-name into the composer.
• altimate.skill.list (category Altimate, packages/opencode/src/plugin/tui/altimate/skill-ops.tsx:843): the skill browser with Show / Edit / Test / Remove / Publish to workspace (feat(workspace): skill publish <name> and a "Publish to workspace" action #1313).

ctrl+p, typing skill, Enter lands on the first one. The user ends up with /team-greeting in the composer and no dialog, and does not learn that the "Publish to workspace" action exists. That action was added in #1313 precisely because a UAT participant could not tell whether publishing was possible; the row that answers the question is the second "Skills" entry, one arrow key below a row with the same title. Observed on 0.12.1 while testing #1313 end to end (it derailed the first attempt at the flow).

Reproduction

1. ALTIMATE_WORKSPACE=1 altimate-code --yolo in a linked project with one authored skill.
2. ctrl+p, type skill, Enter.
3. A skill picker opens; choosing a skill inserts /name into the prompt. No Publish action anywhere.
4. ctrl+p, type skill, arrow down once, Enter: the Altimate skill browser opens; Enter on a skill shows the action menu with Publish to workspace.

Suggested fix

Give the two rows distinct titles and descriptions (e.g. "Insert skill into prompt" under Prompt, "Skills: browse, publish, test" under Altimate), or fold the insert action into the browser's action menu so there is one Skills row. Also consider listing the Altimate row first when the query is skill.

[anandgupta42]

@sahrizvi assigning to you with the other workspace-pilot findings. Found while running the v0.12.0/v0.12.1 skill-publish flow end to end on 0.12.1; the repro in the body is exactly what was run, and the source line is named. Everything else in #1280/#1313 passed: create then update, attach to the workspace, pull into a second checkout with the skill used on a plain question, and every refusal (built-in, workspace-sent, non-UTF-8 file with the path named, symlinked root, unlinked project).