Poe API returns '402 You've used up your points! Visit https://poe.com/api/keys to get more.' which was not matched by RAW_402_MARKER_RE (requires 'payment required'). Add Poe-specific pattern to RAW_402_MARKER_RE so fallback triggers.

Ref: https://poe.com/api/keys
Made-with: Cursor

Summary

Describe the problem and fix in 2–5 bullets:

• Problem: Poe API returns 402 You've used up your points! Visit https://poe.com/api/keys to get more. when credits are exhausted. RAW_402_MARKER_RE only matches 402 payment required and similar patterns, so this error is not recognized as billing.
• Why it matters: Without recognition, classifyFailoverReason returns null, fallback is not triggered, and the user sees a generic failure instead of automatic failover to another model.
• What changed: Added |^\s*402\s+.*used up your points\b to RAW_402_MARKER_RE so Poe's 402 message is treated as billing and triggers fallback.
• What did NOT change (scope boundary): Other 402 formats, classifyFailoverReasonFromHttpStatus, and non-Poe providers are unchanged. Only Poe's specific "used up your points" text is matched.

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes [Bug]: 402 "You've used up your points!" from Poe API not recognized as billing — model fallback does not trigger #42236
• Related #

User-visible / Behavior Changes

List user-visible changes (including defaults/config).
If none, write None.

• When Poe returns 402 You've used up your points!, model fallback now triggers instead of failing with an unclassified error.

Security Impact (required)

• New permissions/capabilities? (No)
• Secrets/tokens handling changed? (No)
• New/changed network calls? (No)
• Command/tool execution surface changed? (No)
• Data access scope changed? (No)
• If any Yes, explain risk + mitigation: N/A

Repro + Verification

Environment

• OS: macOS / Linux
• Runtime/container: Node ≥22
• Model/provider: Poe (poe.com)
• Integration/channel (if any): Any channel using Poe as LLM provider
• Relevant config (redacted): agents.defaults.models with Poe + fallback model (e.g. OpenRouter)

Steps

1. Configure Poe as primary model and another provider (e.g. OpenRouter) as fallback.
2. Exhaust Poe API points (or simulate 402 response).
3. Send a message that triggers an LLM call.

Expected

• Error is classified as billing; fallback to secondary model is triggered.

Actual

• Before fix: classifyFailoverReason returns null, no fallback, generic error shown.
• After fix: Error classified as billing, fallback triggers.

Evidence

Attach at least one:

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Added pi-embedded-helpers.isbillingerrormessage.test.ts case for Poe 402 message; regex logic verified via standalone Node script.

Human Verification (required)

What you personally verified (not just CI), and how:

• Verified scenarios: Regex matches 402 You've used up your points! Visit https://poe.com/api/keys to get more.; existing 402 patterns (e.g. 402 Payment Required) still match.
• Edge cases checked: Pattern is narrow (used up your points); does not match arbitrary 402 xxx text.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

If a bot review conversation is addressed by this PR, resolve that conversation yourself. Do not leave bot review conversation cleanup for maintainers.

Compatibility / Migration

• Backward compatible? (Yes)
• Config/env changes? (No)
• Migration needed? (No)
• If yes, exact upgrade steps: N/A

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert the commit.
• Files/config to restore: src/agents/pi-embedded-helpers/errors.ts, src/agents/pi-embedded-helpers.isbillingerrormessage.test.ts
• Known bad symptoms reviewers should watch for: Poe 402 no longer triggering fallback; false positives on other 402 messages containing "used up your points".

Risks and Mitigations

List only real risks for this PR. Add/remove entries as needed. If none, write None.

• Risk: Another provider returns a 402 message containing "used up your points" with different semantics.
  • Mitigation: Pattern is specific to Poe's known wording; classify402Message still distinguishes billing vs rate_limit via existing hints.