[Integration] paperfoot/search-cli - optional You.com search provider

[mouse-value-add]

Target Repository URL\n\nhttps://github.com/paperfoot/search-cli\n\n### You.com API(s)\n\nsearch\n\n### Why this repo was selected\n\nsearch-cli is an active Rust CLI with 37 stars, a clean provider registry, and explicit support for multiple search backends. Adding You.com as one more optional provider fits the existing architecture without changing defaults, and it keeps the PR small and reviewable.\n\n### Candidate evaluation\n\n- paperfoot/search-cli: best fit today, 37 stars, recent activity, explicit provider abstraction, straightforward optional integration path, strong testability\n- yokingma/one-search-mcp: already contains a You.com provider in the cloned source, so it is not a clean new integration target\n- damionrashford/RivalSearchMCP: active and well-structured, but broader search surfaces made the change a bit less focused than search-cli\n\n### Proposed integration type\n\nOptional search provider adapter backed by the You.com Search API.\n\n### Planned env vars and setup\n\n- to select the new provider\n- for authentication\n- Existing defaults remain unchanged when the provider is not selected\n\n### Expected usage example\n\n\n\n### Validation plan\n\n- Add unit coverage for provider selection and response mapping\n- Run the repo's relevant checks: and if available in the environment\n- Confirm default behavior is unchanged when is not set to \n\n### Fallback/error behavior\n\n- Missing keeps the provider unavailable\n- HTTP failures surface a clear provider error with status/body\n- Existing providers and default routing remain unchanged\n\n### Links\n\nImplementation branch: pending\nOSS PR: pending\n\n### Status\n\nPlanned.

[mouse-value-add]

Update: implementation is complete locally on commit in a fork-based branch workspace, but I hit a GitHub auth/scope blocker before I could publish the branch or open the upstream PR.\n\nCurrent status\n- Selected repo: https://github.com/paperfoot/search-cli\n- Integration type: optional You.com Search provider\n- Local branch name: \n- Local commit: ()\n\nWhat changed locally\n- Added using with \n- Registered the provider in \n- Added support and display/config wiring in \n- Updated README setup/docs for the optional provider\n\nSetup / env vars\n- \n- provider key name: \n\nExpected usage example\n- \n- \n\nFallback / error behavior\n- Missing returns the existing auth-missing provider error\n- HTTP failures flow through the repo's shared provider error handling\n- Default behavior remains unchanged unless users explicitly choose \n\nValidation\n- Could not run or in this environment because Rust/Cargo is not installed\n- Could not publish the fork branch because both the GitHub CLI token and PAT available here lack scope, and GitHub rejects pushes to this fork due to the upstream repo history including \n\nBlocker\n- Need a token with scope, or another push path that can update the fork branch, before opening the OSS PR.\n\nI stopped here rather than scout another repo.

[mouse-value-add]

Follow-up triage update

I checked the existing implementation path instead of scouting a new repo.

Current status

• Tracking issue: [Integration] paperfoot/search-cli - optional You.com search provider #91
• Selected repo: https://github.com/paperfoot/search-cli
• Branch: https://github.com/mouse-value-add/search-cli/tree/feat/add-you-search-provider
• OSS PR: feat: add you.com search provider paperfoot/search-cli#7
• Current branch state: published and clean locally
• Current commit: ce4df37f91ba5fc6dc1754c7cc4f0326218834db

Triage result

• No maintainer comments, review requests, requested changes, or failing checks are present on PR Integration request: nickscamara/open-deep-research #7 right now.
• There is no unaddressed review feedback to act on in this run.
• A second older PR (Integration request: nickclyde/duckduckgo-mcp-server #3) also exists for the same repo, but PR Integration request: nickscamara/open-deep-research #7 is the newer implementation thread and the one linked from this tracking issue.

Validation status

• No new code changes were made in this run.
• I verified the local branch is clean and matches the published fork branch.
• I verified PR Integration request: nickscamara/open-deep-research #7 and the tracking issue for unresolved feedback.
• Rust validation is still not available in this environment, so there was no new cargo test/clippy run in this pass.

Follow-up needed

• Wait for maintainer review on feat: add you.com search provider paperfoot/search-cli#7
• If the maintainers prefer, close PR Integration request: nickclyde/duckduckgo-mcp-server #3 to reduce duplicate noise and keep PR Integration request: nickscamara/open-deep-research #7 as the single active thread.