chore(repo): remove the unused .codex settings file and the provider-service stubs

docs/discord/README.md

@@ -7,7 +7,6 @@ This directory contains all documentation related to Discord integration with Co
 ## Overview
 
 **Status**: ⚠️ Legacy in-platform provider. Discord will move to an external service.
-External service stub lives at `external/commonly-provider-services/discord-service/`.
 
 | Document | Description |
 |----------|-------------|

docs/groupme/README.md

@@ -44,8 +44,6 @@ sender-authentication mechanism.
 - ✅ Webhook route `POST /api/webhooks/groupme/:integrationId`
 - UI: Sidebar Apps quick-add uses a redirect flow (no inline config fields); the integration stores Bot ID for outbound replies and Group ID for callback routing (the callback does not supply Bot ID).
 
-External service stub lives at `external/commonly-provider-services/groupme-service/`.
-
 ## Notes
 - Inbound delivery is callback-based, while command and summary responses use
   the GroupMe bot API; this avoids mirroring every message and limits loops.

docs/integrations/README.md

@@ -23,9 +23,7 @@ consent/code-exchange flow is not live.
 ## External provider services (preferred path)
 
 Provider services should live outside the Commonly repo and forward events into the platform.
-For local dev, a mirror lives at `external/commonly-provider-services/` with service stubs for
-Discord/Slack/Telegram/GroupMe. The in-platform providers under `backend/integrations/providers`
-are considered legacy and will be removed once external services are live.
+The in-platform providers under `backend/integrations/providers` are considered legacy and will be removed once external services are live.
 
 ## Two-Way Integration Testing
 

docs/telegram/README.md

@@ -41,7 +41,6 @@
 
 ## Status
 - ⚠️ Legacy in-platform provider (will move to external service).
-- External service stub lives at `external/commonly-provider-services/telegram-service/`.
 
 ## Next Steps
 - Parse common attachment types (photo/document/audio) for richer summaries.