fix(web): resolve skill vs type-chip routing conflicts

[leno23]

Fixes #2972

Summary

Home hero could keep both an active scenario type chip (plugin) and an @skill selection at once, then submit with conflicting pluginId + skillId routing. Picking one source now clears the other, and submit omits skillId whenever a scenario plugin is active.

Surface area

• apps/web/src/components/HomeView.tsx — mutual exclusion in usePlugin / useSkill; guard skillId on submit.
• apps/web/tests/components/HomeView.context-picker.test.tsx — regression tests for chip→skill and skill→chip flows.

Validation

• cd apps/web && pnpm test tests/components/HomeView.context-picker.test.tsx — 5 passed.

Made with Cursor

[lefarcen]

Hey @leno23, thanks for jumping on the #2972 routing conflict so quickly — the Summary and Validation make the fix direction easy to follow.

One small PR-description housekeeping ask before pool review: could you update the ## Surface area section to use the repo's checklist and tick the affected surface (this looks like UI/default routing behavior), rather than only listing files? That helps reviewers and release verification see the user-facing surface at a glance.

[github-actions]

Visual regression review

Head: b0c4a03 · Base: 1d72914

0 changed · 17 unchanged · 0 missing baseline · 0 failed

Unchanged cases

Case	Main	PR	Diff
visual-avatar-menu
visual-design-systems
visual-home
visual-home-catalog
visual-home-context-picker
visual-home-plugin-filter
visual-integrations
visual-integrations-use-everywhere
visual-new-project-modal
visual-plugin-details
visual-plugins
visual-projects
visual-projects-kanban
visual-settings-byok
visual-settings-execution
visual-tasks
visual-topbar-execution-switcher

Visual diff is advisory only and does not block merging.

[Siri-Ray]

@leno23 I reviewed the HomeView routing changes and the added context-picker regression coverage. The updated selection handlers now clear the opposing route source, submit derives skillId from the active scenario state, and the new tests cover both chip-to-skill and skill-to-chip flows. CI is green for the relevant web/workspace checks; I could not rerun the focused Vitest locally because this Looper worktree has no node_modules, but the live Web workspace tests passed. Thanks for tightening this routing path and adding focused regression coverage.

_{🔁 Powered by Looper · runner=reviewer · agent=codex · An autonomous AI dev team for your GitHub repos.}

[lefarcen]

Reviewer approval and CI are green — flagged for the maintainer team to make the merge call. Thanks @leno23 for the fix and @Siri-Ray for the review!