oma-search

# Search Router ## Scheduling ### Goal Route an information request to the appropriate channel and return relevant sources with trust labels. ### Intent signature - Search, find, look up, reference docs, inspect official APIs, or search remote code. - Another skill requests docs, web, code, or local search with a query and constraints. ### When to use - Library documentation, web research, GitHub/GitLab implementation patterns, or unclear search channels. ### When NOT to use - Pure local code exploration -> use configured code intelligence under the shared contract. - Git history/blame -> `oma-scm`; architecture analysis -> `oma-architecture`. ### Expected inputs Query, optional route hint (`docs`, `web`, `code`, `local`), source/recency constraints, and flags. Explicit `--docs`, `--code`, or `--web` selects the route; `--strict` filters trust, `--wide` retains labeled results, and `--gitlab` selects the remote code host. ### Expected outputs Ranked sources with URL or file reference, route, relevance, trust level/score, and material fallback limits. Do not invent sources when no reliable result is found. ### Dependencies Context7 for docs, runtime web search, `oma search`/`gh`/`glab` for remote code, and configured code intelligence or native local search. ## Structural Flow ### Routes | Route | Primary | Fallback | Use for | |---|---|---|---| | `docs` | Context7 `resolve-library-id` → `query-docs` | Web search | Official API/framework documentation | | `web` | Run...