online-song-omni-routing

name

online-song-omni-routing

description

Standardize Folia online-song data access around the Omni facade, including search, playback, lyrics, catalogs, libraries, recommendations, account actions, mutations, provider identity, and explicit cross-provider flows. Use when adding, refactoring, reviewing, or testing online music features, when deciding whether a caller may use a provider adapter directly, or when implementing provider aggregation, fallback, comparison, or migration.

Online Song Omni Routing

Use this skill for every feature that exchanges data with an online music provider. For fast navigation, read skills/codebase-navigation/SKILL.md, then the relevant sections of README.md, src/README.md, and src/services/onlineMusic/README.md; treat src/services/onlineMusic/omni.ts and src/types/onlineMusic.ts as the public contract.

Non-negotiable rule

Unless the feature is explicitly cross-provider, route all online-song data interaction through omni.

This rule applies to search, song detail, audio URLs, availability/replacement, lyrics, chorus ranges, playlists, albums, artists, recommendations, account status, likes, subscriptions, playlist mutations, and page URLs. Components, hooks, stores, and ordinary app services must not import a concrete provider, provider registry, or provider transport to perform these operations.

omni is a facade, not a raw-response escape hatch. Callers consume UnifiedSong, OmniCollection, OmniPage, OmniLyricsResult, OmniAudioSource, OmniUser, and OmniError; never make caller code depend on provider-specific field names or envelopes.

Current provider implementation map: providerRegistry.ts selects capabilities, and retain account/session state, and normalize provider data, and owns KuGou transport details. is a separate Subsonic service, not an Omni provider.