Name a maintenance owner for the Volcengine Ark presets #825

volcengine, volcengine-coding-plan, and volcengine-agent-plan landed in #611 with the credential-destination evidence gate otherwise satisfied (ledger: #611 (comment)). One MAINTAINERS.md item is still open: a named maintenance owner.

This is not paperwork. All three presets are liveModels: false, so their model catalogs are static by design — live discovery cannot repair a stale entry, and a wrong id surfaces to the user as an upstream model error at request time. We already hit this once: the branch shipped glm-5.1, which is absent from Volcengine's current published Plan list, and it had to be corrected to glm-5.2 during review.

@yrooogerg — you authored these presets and have the working knowledge of the three billing routes. Would you take ownership? Concretely that means:

• being the tag target when Ark endpoints, plan model lists, or terms change
• refreshing VOLCENGINE_ARK_MODELS, VOLCENGINE_CODING_PLAN_MODELS, and VOLCENGINE_AGENT_PLAN_MODELS in src/providers/registry.ts when Volcengine's catalog moves
• re-checking the Plan usage restriction disclosed in the two Plan note strings if Volcengine's terms change

Reply on this issue to accept and I will record you in the evidence ledger. If you would rather not, say so plainly and it falls to the maintainers — in that case we should also decide whether to keep the static catalogs canonical or demote them.

Related: #611. Verification date on the current evidence: 2026-08-01.