[feature]: Support model ID mapping for proxy providers (LiteLLM, etc.)

[sacrtap]

Problem

When using a proxy provider like LiteLLM, the modelID returned by the session API reflects the proxy's model name (e.g., litellm-local/qwen3.6-plus) rather than the original provider prefix (e.g., alibaba-cn/qwen3.6-plus).

The isAlibabaModelId() function only matches models starting with alibaba/ or alibaba-cn/, so local request counting never triggers for proxied models.

Root Cause

plugin.js:1389 — isAlibabaModelId(model) checks:

normalized.startsWith("alibaba/") || normalized.startsWith("alibaba-cn/")

But when routed through LiteLLM, sessionMeta.modelID = litellm-local/qwen3.6-plus, which doesn't match.

Impact

• recordAlibabaCodingPlanCompletion() is never called
• alibaba-coding-plan-local-quota.json recent array stays empty
• Users with proxy setups cannot track local request counts

Suggested Solutions

Option A: Configurable model ID mapping

Add a config option to map custom model prefixes to provider quota tracking:

{
  "modelIdMapping": {
    "litellm-local/qwen3.6-plus": "alibaba-coding-plan"
  }
}

Option B: Provider-based matching fallback

When modelID doesn't match any known prefix, fall back to providerID from sessionMeta to determine which quota tracker to use.

Option C: Wildcard/pattern matching in isAlibabaModelId

Allow configurable regex or wildcard patterns for model ID matching.

Environment

• opencode-quota: v3.8.7
• opencode: v1.15.4
• Provider: LiteLLM proxy routing to Alibaba Coding Plan

[github-actions]

Thanks for opening this issue.

This issue was automatically closed because it does not match the expected issue template format.

Missing required template sections:

• Pre-flight checks

• OpenCode version reviewed

• Problem statement

• Proposed change

• Acceptance criteria

Please re-open using the Feature request issue template.

You can open a new issue here: https://github.com/slkiser/opencode-quota/issues/new/choose