#13717: feat(providers): add Poe API provider plugin

## Summary Add [Poe](https://poe.com) (`api.poe.com`) as a provider plugin with OpenAI-compatible API. **This has been a frequently requested integration from our users** who want access to multiple models through a single API key. - Create `extensions/poe` with full plugin implementation - Add API key validation via `/v1/models` endpoint - Include 14 popular models: Claude (Opus/Sonnet/Haiku/Code), GPT-5.x Codex family, o3 Pro, Gemini 3, Grok 4, DeepSeek R1/V3 - Add unit tests (6 tests, all passing) - Add documentation at `docs/providers/poe.md` - Update provider index and docs navigation This is a clean rebase of #1855 (by @garethpaul) onto the latest `main`, squashed into a single commit and polished to match project conventions: - `package.json` updated to follow workspace conventions (`private: true`, `devDependencies`, current version) - Docs frontmatter aligned with existing providers (`title` field, `openclaw` CLI references) - Navigation entries placed consistently alongside similar multi-model providers ## Test plan - [x] `vitest run extensions/poe/index.test.ts` — 6/6 tests pass - [ ] Verify docs render correctly - [x] CI passes 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Adds a new `poe` provider plugin under `extensions/poe` that registers Poe’s OpenAI-compatible API (`https://api.poe.com/v1`) as a model provider with an API-key auth flow (validated via `/v1/models`). The PR also wires provider docs into the docs navigation and adds a new provider page describing setup and available model IDs. The plugin follows the same provider registration + `configPatch` patterns used by other provider extensions (registering `models.providers.poe` and adding entries to `agents.defaults.models`), and includes basic unit tests for registration + API-key validation behavior. <h3>Confidence Score: 4/5</h3> - This PR is largely safe to merge, with one docs/config mismatch to fix. - Core provider/plugin implementation matches existing extension patterns and the tests cover basic registration + API-key validation. The main issue found is a documentation snippet that doesn’t align with the canonical agent default model selection fields, which could lead users to misconfigure their default model. - docs/providers/poe.md <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->