Skip to content

docs: listing form selects provider → plan → model (v1.9) - #31

Merged
argszero merged 1 commit into
mainfrom
docs/listing-plan-flow
Aug 17, 2026
Merged

argszero merged 1 commit into
mainfrom
docs/listing-plan-flow

Conversation

@argszero

Copy link
Copy Markdown
Owner

Summary

Docs half of the "厂商 → Plan → 模型" listing-flow change (UI half landed in PR #30).

  • docs/user-stories.md bumped to v1.9: US-8 rewritten to the three-level "选厂商 → 选 Plan → 选模型" flow (with "API(按量)" = pay-as-you-go key, built-in domestic plan catalog); US-9 AC updated to show "厂商 · Plan / 模型" in the listing table; 核心机制表「上架 Listing」term updated.
  • config/config.example.toml: supplemented the missing pay-as-you-go (paygo) plans — zhipu / aliyun-bailian / bytedance-ark / moonshot / minimax — so every provider in the catalog has an "API(按量)" entry (deepseek already had one). Verified: 12 plans total, all 6 providers have a paygo type.

Rant reference

Host instruction (rant 2026-08-17T10:51:24, 上架表单改为"厂商 → Plan → 模型"):

所以上架时选择的是厂商 Plan,而不是厂商/模型——流程应为:选厂商 → 选 Plan(列表里 "API" 代表按量计价的 key)→ 选该 Plan 支持的模型;把国内已知 Plan 都内置进去。

Verification

  • config/config.example.toml parses with tomllib — 12 plans, every provider has ≥1 paygo plan
  • cargo test passes (1 passed)
  • cargo fmt --check passes

Update the product user stories to the new listing flow: sharers select
provider → plan → model (most share their plan subscriptions such as
Aliyun Token Plan / Kimi Code, and different plans of the same provider
may have different base URLs). In the plan dropdown, "API(按量)"
means a pay-as-you-go key. Bump docs to v1.9 (US-8 / US-9 / Listing
term updated). Also supplement config/config.example.toml with the
missing pay-as-you-go plans (zhipu / aliyun-bailian / bytedance-ark /
moonshot / minimax) so every provider has an "API(按量)" entry per
the built-in plan catalog.

Refs: rant 2026-08-17T10:51:24 (上架表单改为"厂商 → Plan → 模型")
@argszero
argszero merged commit 5927f46 into main Aug 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant