fix(corsair): register youcom plugin in provider constants

[Ronitjaiswal30]

The youcom package is a fully implemented You.com Web Search plugin (client, endpoints, error handlers, schema, tests), but it was never added to the central provider registry, so the core system had no way to know it exists.

Register it in all three places in core/constants.ts:

• BaseProviders, alphabetically between xquik and youtube
• ProviderDisplayNames, with the display name You.com
• the AllProviders union type

Closes #622

Description

Checklist

Before submitting your PR, please verify the following:

• I have run pnpm lint and all checks pass
• I have run pnpm typecheck and there are no TypeScript errors
• I have run pnpm build and all packages build successfully
• I have run pnpm test and all tests pass
• I have added or updated tests where applicable
• I have added or updated necessary documentation

Screenshots / Demos (if applicable)

Additional Notes

Summary by CodeRabbit

• New Features
  • Added You.com as a supported provider.
  • You.com now appears with its display name wherever provider options are shown.

[vercel]

@Ronitjaiswal30 is attempting to deploy a commit to the corsair Team on Vercel.

A member of the Team first needs to authorize it.

[Ronitjaiswal30]

.

[Ronitjaiswal30]

hacknite

[greptile-apps]

Greptile Summary

This PR registers the existing You.com plugin in Corsair’s shared provider vocabulary so core consumers recognize it.

• Adds youcom to BaseProviders.
• Maps youcom to the display name You.com.
• Adds youcom to the AllProviders union.

Confidence Score: 5/5

The PR appears safe to merge, with the provider identifier and display name registered consistently.

The new identifier exactly matches the existing You.com plugin ID, is correctly ordered, and updates every shared provider vocabulary surface without introducing a conflicting registry entry.

Important Files Changed

Filename	Overview
packages/corsair/core/constants.ts	Adds the existing plugin’s exact youcom identifier consistently across all three provider registry surfaces.

_{Reviews (1): Last reviewed commit: "fix(corsair): register youcom plugin in ..." | Re-trigger Greptile}

[coderabbitai]

📝 Walkthrough

Walkthrough

The core provider registry now includes You.com in its base provider list, display-name map, and AllProviders type union.

Changes

Provider registration

Layer / File(s)	Summary
Register You.com provider packages/corsair/core/constants.ts	Adds youcom to BaseProviders and AllProviders, and maps it to the display name You.com.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• corsairdev/corsair#623: Duplicates the same provider declaration changes.
• corsairdev/corsair#647: Makes identical updates to register youcom.
• corsairdev/corsair#648: Adds a provider to the same three declarations.

Suggested reviewers: yuvrxj-afk

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes satisfy issue #622 by adding youcom to BaseProviders, ProviderDisplayNames, and AllProviders.
Out of Scope Changes check	✅ Passed	All changes are limited to the provider registration points required by issue #622.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes registering the You.com plugin in the provider constants.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[Dhirenderchoudhary]

Thanks for the contribution @Ronitjaiswal30 Closing PR as PR #623 already exist.