接入 MaDao 统一接码并收敛 provider 换号链路#288
Open
netcookies wants to merge 7 commits into
Open
Conversation
新增 MaDao 接码 provider,并将 acquire/poll/release 接入手机号验证链路。 侧边栏新增 MaDao 互斥配置模型,支持路由方案与直连参数两种模式, 同时保留 HeroSMS、5sim、NexSMS 的原有分散式直连能力。 同步适配 MaDao 最新国家 canonical 规则: - madaoCountry 改为保留 ISO alpha-2 与 any/local sentinel - 运行态国家展示按 canonical 值还原可读国家名 - 更新持久化、测试夹具与文档说明
为 MaDao provider 增加 createProvider 导出,和统一 provider registry 契约保持一致。 补充真实模块回归测试,避免假桩掩盖 registry 与模块导出不一致的问题。
收敛 MaDao 模式下的接码设置显隐规则,隐藏未对接或无效的共享接码项。 补充 direct 与 routing_plan 模式文案及回归测试,避免不同服务商下的价格区文案混淆。
在 MaDao 模式下隐藏冗余的路由方案说明行,避免与已收敛后的参数显隐重复表达。 同步更新侧边栏回归测试断言。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
背景
本次改动把 FlowPilot 的手机接码能力进一步收敛到 MaDao 统一后端,同时保留原有分散式 provider 能力,避免一次性切断现有链路。
除了接入 MaDao direct / routing_plan 两种模式,这次也把 provider registry 的契约补齐,并修正了第 9 步在 MaDao routing replace 场景下的换号状态处理问题。
主要改动
acquire / poll / releasedirect与routing_plan两种模式routing_plan模式下,换号改为优先走/api/routing/replacePhoneSmsProviderRegistry.createProvider('madao')NexSMS独立 provider 模块并接入background.js、sidepanel加载入口background/phone-verification-flow.js中对 provider adapter 的 fallback,统一通过 registry 构造routing_plan与direct参数按模式互斥显示MaDao时显示仓库入口按钮routing_plan下,某些分支先拿到nextActivation后,又把新号码继续当旧号码做清理/封禁的问题验证
已执行:
node --test tests/phone-verification-flow.test.js tests/phone-sms-provider-registry.test.jsnode --check background/phone-verification-flow.jsnode --check phone-sms/providers/nexsms.jsgit diff --check影响说明
.workflow/目录内容