Issue 概要

issue：#1770
版本 / 控制器：issue 未提供版本、控制器、截图和 MaaEnd-logs-*.zip，本次无法建立日志时间线，也无法确认是否为 Win32 / ADB、是否为最新版本。
任务 / 相关选项：
- 🎁基建任务（DijiangRewards），相关开关是 不使用总控中枢生产助力
- ⚔️协议空间（ProtocolSpace），相关选项是 选择队伍
- issue 文本里的“自动战斗”更像 ⚔️协议空间 的自动刷取前置流程，而不像 🎱基质刷取（AutoEssence）：因为仓库里只有 ⚔️协议空间 暴露了“选择队伍”选项；🎱基质刷取 只有“挑战方式=走路/自动战斗”，没有选队节点
用户现象：
- 基建任务遇到助力红点时，会反复被带到助力相关界面，但没有真正完成助力
- 战斗前会反复“选择队伍”，却不继续开始战斗
- 由于没有日志包，以下结论是基于 issue 文本 + 当前 HEAD 代码 + 历史同类 issue 旁证的高相关推断，不是本次复现的日志复盘

关键证据

点击此处展开

issue 本身
- #1770 没有提供 MaaEnd-logs-*.zip、版本截图、控制器信息或现场图，因此证据不足，无法像常规日志分析那样锁定具体 task_id、节点超时点和实际停留画面。

🎁基建任务（DijiangRewards）

ControlNexus 会优先跳转 RecoveryEmotionMain；只要总控中枢的助力红点还在，父流程就会持续优先尝试这条分支：

MaaEnd/assets/resource/pipeline/DijiangRewards/MainFlow.json

Lines 2 to 25 in 17467b9

    
           "ControlNexus": { 
        
               "desc": "[主流程·控制中枢] 识别处于帝江号总控中枢界面，按 next 分发至会客室/制造舱/培养舱/好友助力/滑动等子任务或意外处理", 
        
               "max_hit": 1, 
        
               "recognition": { 
        
                   "type": "TemplateMatch", 
        
                   "param": { 
        
                       "roi": [ 
        
                           15, 
        
                           437, 
        
                           225, 
        
                           153 
        
                       ], 
        
                       "template": [ 
        
                           "ClaimDijiangRewards/InControlNexus.png" 
        
                       ] 
        
                   } 
        
               }, 
        
               "next": [ 
        
                   "[JumpBack]RecoveryEmotionMain", 
        
                   "[JumpBack]ReceptionRoomMain", 
        
                   "[JumpBack]MFGCabinMain", 
        
                   "[JumpBack]GrowthChamberMain", 
        
                   "FinishDijiangRewards" 
        
               ],

RecoveryEmotionAssistWindowOpen -> RecoveryEmotionAssistUseAssist -> RecoveryEmotionView2In 这条链只覆盖“识别到生产助力窗口”“识别到使用助力按钮”“成功进入选择待恢复心情的干员”这条理想路径，没有显式覆盖“仍停留在第一页弹窗 / 点击后页面没推进 / OCR 没命中”的回退：

MaaEnd/assets/resource/pipeline/DijiangRewards/RecoveryEmotion.json

Lines 94 to 138 in 17467b9

    
           "RecoveryEmotionAssistWindowOpen": { 
        
               "desc": "[恢复心情·助力] 打开助力界面", 
        
               "recognition": "And", 
        
               "all_of": [ 
        
                   "RecoveryEmotionAssistWindowTitle" 
        
               ], 
        
               "pre_wait_freezes": { 
        
                   "time": 100, 
        
                   "target": "RecoveryEmotionAssistWindowTitle", 
        
                   "target_offset": [ 
        
                       0, 
        
                       0, 
        
                       200, 
        
                       250 
        
                   ] 
        
               }, 
        
               "pre_delay": 0, 
        
               "post_delay": 0, 
        
               "rate_limit": 0, 
        
               "next": [ 
        
                   "RecoveryEmotionAssistUseAssist" 
        
               ] 
        
           }, 
        
           "RecoveryEmotionAssistUseAssist": { 
        
               "desc": "[恢复心情·需要助力] 点击使用助力", 
        
               "recognition": { 
        
                   "type": "And", 
        
                   "param": { 
        
                       "all_of": [ 
        
                           "YellowConfirmButtonType1", 
        
                           "UseAssistText" 
        
                       ], 
        
                       "box_index": 1 
        
                   } 
        
               }, 
        
               "pre_delay": 0, 
        
               "action": { 
        
                   "type": "Click" 
        
               }, 
        
               "post_delay": 0, 
        
               "rate_limit": 0, 
        
               "next": [ 
        
                   "RecoveryEmotionView2In" 
        
               ] 
        
           },

MaaEnd/assets/resource/pipeline/DijiangRewards/RecoveryEmotion.json

Lines 174 to 195 in 17467b9

    
           "RecoveryEmotionView2In": { 
        
               "desc": "[恢复心情·状态] 已打开「选择待恢复心情的干员」界面，开始选择待恢复心情的干员", 
        
               "recognition": "And", 
        
               "all_of": [ 
        
                   "RecoveryEmotionAssistView2Label" 
        
               ], 
        
               "pre_wait_freezes": { 
        
                   "time": 200, 
        
                   "target_offset": [ 
        
                       -300, 
        
                       0, 
        
                       0, 
        
                       150 
        
                   ] 
        
               }, 
        
               "pre_delay": 0, 
        
               "post_delay": 0, 
        
               "rate_limit": 0, 
        
               "next": [ 
        
                   "RecoveryEmotionSelectLowEmotion" 
        
               ] 
        
           },

UseAssistText 只在 YellowConfirmButtonType1 周围较窄 OCR 区域内识别“使用助力 / Use Assist”，对界面偏移、文案遮挡、按钮状态变化都比较敏感：

MaaEnd/assets/resource/pipeline/DijiangRewards/Template/TextTemplate.json

Lines 22 to 39 in 17467b9

    
           "UseAssistText": { 
        
               "desc": "[需要助力] 识别使用助力按钮", 
        
               "recognition": { 
        
                   "type": "OCR", 
        
                   "param": { 
        
                       "roi": "YellowConfirmButtonType1", 
        
                       "roi_offset": [ 
        
                           -125, 
        
                           -31, 
        
                           130, 
        
                           67 
        
                       ], 
        
                       "expected": [ 
        
                           "使用助力", 
        
                           "Use Assist" 
        
                       ] 
        
                   } 
        
               }

不使用总控中枢生产助力 这个开关会直接禁用 RecoveryEmotionMain，说明这条分支本身就是总控中枢助力入口：

MaaEnd/assets/tasks/DijiangRewards.json

Lines 44 to 66 in 17467b9

    
           "ProductionAssistanceWithoutTheControlNexus": { 
        
               "type": "switch", 
        
               "label": "$option.ProductionAssistanceWithoutTheControlNexus.label", 
        
               "description": "$option.ProductionAssistanceWithoutTheControlNexus.description", 
        
               "default_case": "No", 
        
               "cases": [ 
        
                   { 
        
                       "name": "Yes", 
        
                       "pipeline_override": { 
        
                           "RecoveryEmotionMain": { 
        
                               "enabled": false 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "No", 
        
                       "pipeline_override": { 
        
                           "RecoveryEmotionMain": { 
        
                               "enabled": true 
        
                           } 
        
                       } 
        
                   } 
        
               ]

历史 issue #1473 已明确复现过“🎁基建任务 停留在使用助力界面”，当时的分析也指向 RecoveryEmotion 分支状态覆盖不全；而当前 HEAD 仍保留同样的节点结构：基建任务、信用购物失败 #1473

⚔️协议空间（ProtocolSpace）

选择队伍 是显式任务选项；默认 case 会禁用 ProtocolSpaceTeamChoose，只有用户改成 01~05 时才会启用队伍识别：

MaaEnd/assets/tasks/ProtocolSpace.json

Lines 24 to 94 in 17467b9

    
           "ProtocolSpaceTeamChoose": { 
        
               "type": "select", 
        
               "label": "$option.ProtocolSpaceTeamChoose.label", 
        
               "default_case": "ProtocolSpaceTeamChooseDefault", 
        
               "cases": [ 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChooseDefault", 
        
                       "label": "$option.ProtocolSpaceTeamChoose.case.ProtocolSpaceTeamChooseDefault.label", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChoose": { 
        
                               "enabled": false 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChoose01", 
        
                       "label": "01", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChooseTextRecognition": { 
        
                               "expected": [ 
        
                                   "01" 
        
                               ] 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChoose02", 
        
                       "label": "02", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChooseTextRecognition": { 
        
                               "expected": [ 
        
                                   "02" 
        
                               ] 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChoose03", 
        
                       "label": "03", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChooseTextRecognition": { 
        
                               "expected": [ 
        
                                   "03" 
        
                               ] 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChoose04", 
        
                       "label": "04", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChooseTextRecognition": { 
        
                               "expected": [ 
        
                                   "04" 
        
                               ] 
        
                           } 
        
                       } 
        
                   }, 
        
                   { 
        
                       "name": "ProtocolSpaceTeamChoose05", 
        
                       "label": "05", 
        
                       "pipeline_override": { 
        
                           "ProtocolSpaceTeamChooseTextRecognition": { 
        
                               "expected": [ 
        
                                   "05" 
        
                               ] 
        
                           } 
        
                       } 
        
                   } 
        
               ] 
        
           },

ProtocolSpaceEnterSpace 的 next 顺序是 ProtocolSpaceTeamChoose -> ProtocolSpacePopupSanityLow -> ProtocolSpaceEnterSpaceConfirm。也就是说，只要队伍节点还能命中，后面的“确认进入”就轮不到：

MaaEnd/assets/resource/pipeline/ProtocolSpace/InSpace.json

Lines 2 to 28 in 17467b9

    
           "ProtocolSpaceEnterSpace": { 
        
               "desc": "进入协议空间", 
        
               "recognition": "Or", 
        
               "any_of": [ 
        
                   "WhiteConfirmButtonType1", 
        
                   { 
        
                       "recognition": "OCR", 
        
                       "roi": [ 
        
                           -250, 
        
                           -150, 
        
                           250, 
        
                           150 
        
                       ], 
        
                       "expected": [ 
        
                           "进入", 
        
                           "進入", 
        
                           "Enter" 
        
                       ] 
        
                   } 
        
               ], 
        
               "action": "Click", 
        
               "post_wait_freezes": 500, 
        
               "next": [ 
        
                   "[JumpBack]ProtocolSpaceTeamChoose", 
        
                   "ProtocolSpacePopupSanityLow", 
        
                   "ProtocolSpaceEnterSpaceConfirm" 
        
               ],

ProtocolSpaceTeamChoose 只要 OCR 到目标编号且左侧颜色满足条件就会点击；点击后没有“已经选好队伍，应该改点进入”的状态推进判断：

MaaEnd/assets/resource/pipeline/ProtocolSpace/InSpace.json

Lines 33 to 80 in 17467b9

    
           "ProtocolSpaceTeamChooseTextRecognition": { 
        
               "desc": "识别协议空间队伍", 
        
               "recognition": "OCR", 
        
               "roi": [ 
        
                   0, 
        
                   -60, 
        
                   500, 
        
                   35 
        
               ], 
        
               "expected": [ 
        
                   "01" 
        
               ] 
        
           }, 
        
           "ProtocolSpaceTeamChoose": { 
        
               "desc": "选择协议空间队伍", 
        
               "recognition": "And", 
        
               "all_of": [ 
        
                   "ProtocolSpaceTeamChooseTextRecognition", 
        
                   { 
        
                       "recognition": "ColorMatch", 
        
                       "roi": "ProtocolSpaceTeamChooseTextRecognition", 
        
                       "roi_offset": [ 
        
                           -30, 
        
                           0, 
        
                           10, 
        
                           0 
        
                       ], 
        
                       "lower": [ 
        
                           30, 
        
                           30, 
        
                           30 
        
                       ], 
        
                       "upper": [ 
        
                           45, 
        
                           45, 
        
                           45 
        
                       ], 
        
                       "connected": true 
        
                   } 
        
               ], 
        
               "pre_delay": 0, 
        
               "action": "Click", 
        
               "post_wait_freezes": 200, 
        
               "post_delay": 0, 
        
               "focus": { 
        
                   "Node.Action.Succeeded": "选择队伍" 
        
               } 
        
           },

ProtocolSpaceEnterSpaceConfirm 点击后只接受“加载退出”或“进入成功”这两种理想后继状态，没有覆盖“还停在确认页 / 还停在队伍页”时的重试路径：

MaaEnd/assets/resource/pipeline/ProtocolSpace/InSpace.json

Lines 102 to 127 in 17467b9

    
           "ProtocolSpaceEnterSpaceConfirm": { 
        
               "desc": "确认进入协议空间", 
        
               "recognition": "Or", 
        
               "any_of": [ 
        
                   "YellowConfirmButtonType2", 
        
                   { 
        
                       "recognition": "OCR", 
        
                       "roi": [ 
        
                           -250, 
        
                           -150, 
        
                           250, 
        
                           150 
        
                       ], 
        
                       "expected": [ 
        
                           "进入", 
        
                           "進入", 
        
                           "Enter" 
        
                       ] 
        
                   } 
        
               ], 
        
               "pre_wait_freezes": 400, 
        
               "action": "Click", 
        
               "next": [ 
        
                   "[JumpBack]SceneWaitLoadingExit", 
        
                   "ProtocolSpaceEnterSpaceSuccess" 
        
               ],

历史 issue #1690 已经确认过协议空间入场链路在慢加载时属于“点击成功，但 next 只覆盖成功态，不覆盖原页重试”的脆弱模式。这和“反复选择队伍，不开始”的描述高度同类：游戏界面加载慢，点击过快且缺少重试例如：协议空间+日常奖励领取 #1690

排除项

🎱基质刷取（AutoEssence） 虽然有“挑战方式=自动战斗”，但它没有“选择队伍”任务选项，因此与 issue 文本里的“会一直选择队伍”不吻合：

MaaEnd/assets/tasks/AutoEssence.json

Lines 24 to 55 in 17467b9

    
           "option": { 
        
               "AutoEssenceChallengeMode": { 
        
                   "type": "select", 
        
                   "label": "$option.AutoEssenceChallengeMode.label", 
        
                   "description": "$option.AutoEssenceChallengeMode.description", 
        
                   "default_case": "Walk", 
        
                   "cases": [ 
        
                       { 
        
                           "name": "Walk", 
        
                           "label": "$option.AutoEssenceChallengeMode.cases.Walk.label", 
        
                           "pipeline_override": { 
        
                               "AutoEssenceClickEssenceChallengeUsingWalk": { 
        
                                   "enabled": true 
        
                               }, 
        
                               "AutoEssenceClickEssenceChallengeUsingAutoFight": { 
        
                                   "enabled": false 
        
                               } 
        
                           } 
        
                       }, 
        
                       { 
        
                           "name": "AutoFight", 
        
                           "label": "$option.AutoEssenceChallengeMode.cases.AutoFight.label", 
        
                           "pipeline_override": { 
        
                               "AutoEssenceClickEssenceChallengeUsingWalk": { 
        
                                   "enabled": false 
        
                               }, 
        
                               "AutoEssenceClickEssenceChallengeUsingAutoFight": { 
        
                                   "enabled": true 
        
                               } 
        
                           } 
        
                       } 
        
                   ]

根因判断

直接结论：
- 本 issue 大概率不是一个单一的 MXU / Agent / 控制器启动故障，而是两个独立但同类的 Pipeline 状态覆盖缺陷。
- 现象 1 高概率落在 🎁基建任务 的 RecoveryEmotion 分支：红点未清掉时，父流程会持续把任务吸回总控中枢助力分支，但子流程对“第一页弹窗 / 使用助力按钮 / 点击后仍未推进”的状态覆盖不够完整，所以表现为“反复带去红点，但没有真正助力”。
- 现象 2 高概率落在 ⚔️协议空间 的入场分支：ProtocolSpaceTeamChoose 被放在 ProtocolSpaceEnterSpaceConfirm 之前，而且没有“已选好队伍 / 该改点进入”的推进判断；在配置了 选择队伍 且界面响应慢或首帧不稳定时，容易反复点击队伍而不继续开始战斗。
证据链：
- #1473 已经复现过与本 issue 第一条现象高度同构的“停留在使用助力界面”，且当前 HEAD 的 RecoveryEmotion 结构没有看到本质不同的分支补强。
- #1690 已经确认过 ProtocolSpaceEnterSpaceConfirm 属于“单次点击 + 只等成功态”的脆弱模式；再叠加当前 ProtocolSpaceEnterSpace 把 TeamChoose 放在 Confirm 之前，就很容易演化成“反复选择队伍”的用户感知。
- issue 文本里的“自动战斗”如果真是别的任务，目前仓库里也找不到另一个更贴近“反复选择队伍”的公开入口；所以把第二个现象映射到 ⚔️协议空间 的置信度高于映射到通用 AutoFight。

给用户的建议

用户现在可以直接尝试的动作：
- 🎁基建任务 临时开启 不使用总控中枢生产助力，先绕过 RecoveryEmotion 分支。
- ⚔️协议空间 先把 选择队伍 改回 默认，让游戏沿用当前或上次的编队，避免触发 ProtocolSpaceTeamChoose。
- 如果 issue 里说的“自动战斗”其实不是 ⚔️协议空间，请下次补一份 MaaEnd-logs-*.zip，或者至少补版本截图、任务截图、是否开启了“选择队伍”。
是否建议升级 / 重下完整包 / 同步资源 / 重置配置：
- 没有证据表明这是安装包损坏、资源缺失或配置损坏，重装不是首选建议。
- 若当前不是最新正式版，升级可以一试；但从当前 HEAD 看，这两处脆弱结构仍然存在，所以升级不保证彻底解决。
是否需要等待开发者修复：
- 需要。 这更像 Pipeline 分支覆盖不足，而不是用户配置错误。
是否有临时绕过方案：
- 有，最实用的是：
  - 基建任务开启 不使用总控中枢生产助力
  - 协议空间将 选择队伍 改回 默认

修复方案

代码 / Pipeline / 配置层修复
- 🎁基建任务 / RecoveryEmotion
  - 在 RecoveryEmotionAssistWindowOpen 和 RecoveryEmotionAssistUseAssist 之后补显式状态分支，至少覆盖：
    - 今日助力好友
    - 选择待恢复心情的干员
    - 无法使用助力 / 干员心情已满
    - 没有更多心情激励点数
    - 点击后仍停留在第一页弹窗
  - UseAssistText 不要只依赖窄 ROI OCR；应增加标题/标签锚点，或放宽识别区域。
  - 当 RecoveryEmotionMain 多次命中但子流程没有推进时，应返回控制中枢并临时跳过，而不是一直被红点吸回。
- ⚔️协议空间 / 入场确认
  - 调整 ProtocolSpaceEnterSpace 的分支策略，不要让 ProtocolSpaceTeamChoose 永远抢在 ProtocolSpaceEnterSpaceConfirm 前面。
  - ProtocolSpaceTeamChoose 点击后应立即校验：如果目标队伍已选中且确认按钮存在，就转入 ProtocolSpaceEnterSpaceConfirm，而不是重复点队伍。
  - ProtocolSpaceEnterSpaceConfirm 需要补“仍停留在原确认页 / 原队伍页”的重试分支或中间稳定态，覆盖慢加载。
需要补充的测试或日志
- 对 RecoveryEmotion 增加 on_error 现场图与更明确的 focus 文案，区分“停在第一页弹窗”“Use Assist 未识别”“进入第二页失败”。
- 对 ProtocolSpaceEnterSpace -> TeamChoose -> Confirm 增加回归样本，至少覆盖：
  - 首次进入、资源未热加载
  - 自定义队伍 01~05
  - 点击后仍停留在确认页的慢加载场景
- 如果用户再次复现，优先要求提供：
  - MaaEnd-logs-*.zip
  - 版本截图
  - 控制器类型
  - ⚔️协议空间 是否启用了 选择队伍
如问题本身属于不支持场景，给出应如何限制入口或改进提示
- 目前证据不支持“这是不支持场景”的判断。
- 相反，两个现象都更像已支持任务中的状态分支不完整，因此更适合修 Pipeline，而不是限制入口。

给修复 AI 的建议（可复制）

点击此处展开

现象：
1. 🎁基建任务遇到总控中枢助力红点时，反复进入助力界面，但没有真正完成助力；
2. ⚔️协议空间在启用了“选择队伍”后，反复点击队伍，不继续进入战斗。

关键证据：
- ControlNexus.next 先跳 RecoveryEmotionMain，红点不消失时会被持续吸回；
- RecoveryEmotionAssistWindowOpen / RecoveryEmotionAssistUseAssist 只覆盖理想成功态，没有覆盖“仍停留在今日助力好友/生产助力第一页”；
- UseAssistText 仅依赖 YellowConfirmButtonType1 附近窄 ROI OCR；
- ProtocolSpaceEnterSpace.next 顺序为 TeamChoose -> PopupSanityLow -> EnterSpaceConfirm；
- ProtocolSpaceTeamChoose 点击后没有状态推进校验；
- ProtocolSpaceEnterSpaceConfirm 只覆盖成功进入，不覆盖原页重试。

可能相关线索（待验证）：
- UseAssistText OCR ROI 过窄或按钮状态变化导致未命中；
- ProtocolSpace 慢加载或首帧未稳定时，TeamChoose 会抢在 EnterSpaceConfirm 前反复命中；
- 两处都需要补“当前页面未推进”的重试/跳过分支，而不是只等待成功态。

置信度

中
高置信度部分：
- 当前代码里确实存在上述两个高风险脆弱点；
- #1473 与 #1690 已分别给出与这两个现象高度同类的历史旁证。
还缺什么证据：
- #1770 本次复现的 MaaEnd-logs-*.zip
- 版本 / 控制器信息
- “自动战斗”到底指的是 ⚔️协议空间 还是别的任务
- 是否启用了 选择队伍

English translation

Click here to expand

Issue Summary

Issue: #1770
Version / controller: not provided. The issue has no version info, controller info, screenshot, or MaaEnd-logs-*.zip, so I cannot build a runtime timeline for this reproduction.
Tasks / related options:
- 🎁Base Rewards (DijiangRewards), with the related option Production Assistance without Master Control Nexus
- ⚔️Protocol Space (ProtocolSpace), with the related option Select Team
- The user's “auto battle” description is more likely referring to the pre-battle flow of ⚔️Protocol Space than 🎱Auto Essence, because only ⚔️Protocol Space exposes a visible Select Team option.
User-visible symptoms:
- During the base task, when an assist red dot appears, the task keeps being pulled back to that UI but does not actually perform the assist.
- Before battle, it keeps selecting the team and never proceeds to actually start.
- Since there is no log package, the conclusion below is a code-based high-probability inference, not a direct log replay.

Root Cause

Direct conclusion:
- This issue is most likely not a single MXU / agent / controller startup failure. It looks like two separate but structurally similar Pipeline state-coverage defects.
- Symptom 1 most likely belongs to 🎁Base Rewards: the RecoveryEmotion branch does not fully cover the intermediate states around the “Use Assist” flow, so when the red dot remains visible, the parent flow keeps re-entering that branch without actually clearing it.
- Symptom 2 most likely belongs to ⚔️Protocol Space: ProtocolSpaceTeamChoose is evaluated before ProtocolSpaceEnterSpaceConfirm, and it lacks a state transition check such as “team already selected, now press Enter”. When Select Team is enabled and the UI is slow or unstable, it can keep clicking the team instead of advancing into battle.
Evidence chain:
- #1473 previously reproduced a highly similar “stuck on the Use Assist screen” problem in 🎁Base Rewards, and the current HEAD still keeps the same RecoveryEmotion structure.
- #1690 previously confirmed that the ProtocolSpace entry flow is fragile in slow-loading scenarios because its next branches only cover the success path and do not cover retry-on-same-screen behavior.
- There is no other public task in the current repo that matches the user's “keeps selecting team” description better than ⚔️Protocol Space.

Suggestions for the user

Immediate workarounds:
- In 🎁Base Rewards, enable Production Assistance without Master Control Nexus to bypass the RecoveryEmotion branch.
- In ⚔️Protocol Space, set Select Team back to Default so the flow does not enter ProtocolSpaceTeamChoose.
Reinstall / reset config / re-download:
- There is no evidence that this is caused by a broken package or broken config, so reinstalling is not the first recommendation.
- Updating to the latest release may be worth trying, but the fragile structures still exist in current HEAD, so an update is not guaranteed to solve it.
Do developers need to fix it?
- Yes. This looks like a real Pipeline design defect rather than a user-side misconfiguration.

Fix Plan

🎁Base Rewards / RecoveryEmotion
- Add explicit branches after RecoveryEmotionAssistWindowOpen and RecoveryEmotionAssistUseAssist to cover:
  - Assists Today
  - Select operator awaiting mood recovery
  - Cannot assist / max mood
  - No remaining mood booster points
  - the case where the UI still remains on the first assist popup
- Do not rely only on the narrow UseAssistText OCR region. Add stronger anchors or widen the ROI.
- If RecoveryEmotionMain keeps hitting without progress, return to Control Nexus and skip temporarily instead of being permanently attracted by the red dot.
⚔️Protocol Space / entry flow
- Adjust ProtocolSpaceEnterSpace so ProtocolSpaceTeamChoose cannot starve ProtocolSpaceEnterSpaceConfirm.
- After ProtocolSpaceTeamChoose clicks the target team, immediately check whether the team is already selected and whether the confirm button is present; if so, proceed to confirm instead of clicking the team again.
- Add a retry path for ProtocolSpaceEnterSpaceConfirm when the UI remains on the original team/confirm screen under slow loading.

Confidence

Medium
High-confidence part:
- The current code does contain both fragile structures described above.
- #1473 and #1690 provide strong prior evidence for the same two paths.
Missing evidence:
- A real MaaEnd-logs-*.zip from #1770
- Version and controller info
- Confirmation of whether the “auto battle” in this report is really ⚔️Protocol Space
- Confirmation of whether Select Team was enabled

点击此处展开分析过程

● skill(maaend-issue-log-analysis)

先把 issue 正文、评论、仓库协作规范和当前版本一起拉下来，接着我会下载日志包并建立时间线。

● Read AGENTS.md
└ 71 lines read

● Get issue details
└ [{"id":4159813160,"body":"🤖 MaaEndBot 正在分析该 Issue... \n\n感谢您的反馈！AI 正在自动...

● Get issue details
└ {"number":1770,"title":"基建收菜，和自动战斗","body":"###
问题描述\n\n收菜的时候如果有助力，会有红点，他就会一直...

● Get current HEAD commit (shell)
│ git rev-parse HEAD
└ 2 lines...

这个 issue 没带日志包，我会按“证据不足 + 代码复核”的路径继续，把两个现象分别映射到现有任务和 Pipeline，再给出能落地的结论。

● Explore(claude-haiku-4.5) 探索相关任务
└ Agent started in background with agent_id: issue1770-mapping. You can use rea...

● Todo added 4 items
│ 确认 issue 上下文
│ 映射相关任务
│ 复核相关 Pipeline
└ 撰写最终结论

● Create session plan file (shell)
│ cat > /home/runner/.copilot/session-state/c2c4b05f-4014-424f-91d8-5a8db6ce0e8f/plan.md <<'EOF'
│ # Issue 1770 分析计划
│
│ 1. 确认 issue 文本、评论、是否存在日志附件。
│ 2. 映射“基建收菜”和“自动战斗”到实际任务、中文文案、入口与控制器支持。…
└ 4 lines...

我先在仓库里把中文文案、任务定义和疑似相关节点对齐起来，这样后面的结论能直接落到具体文件和节点。

● Read interface.json
│ assets/interface.json
└ L1:260 (169 lines read)

● Search (glob)
│ "assets/tasks/*.json"
└ 31 files found

● Search (grep)
│ "收菜|自动战斗|助力|队伍|开始战斗|基建" in **/*.json (assets/locales)
└ 53 lines found

● Search (grep)
│ "助力|红点|队伍|开始战斗|自动战斗|收菜" in **/*.{json,md} (assets)
└ 102 lines found

● Read DijiangRewards.json
│ assets/tasks/DijiangRewards.json
└ 1 line read

● Read AutoEssence.json
│ assets/tasks/AutoEssence.json
└ 1 line read

● Search (grep)
│ "ProtocolSpaceTeamChoose|AutoFight|开始战斗|队伍界面|快速编辑队伍|队伍" in **/*.json
│ (assets/resource/pipeline)
└ 87 lines found

● Read ProtocolSpace.json
│ assets/tasks/ProtocolSpace.json
└ 459 lines read

我已经把范围缩到两条主线了：一条是 🎁基建任务 里的助力/红点分支，另一条是带“选择队伍”的战斗任务。接下来我会读对应节点，确认是不是存在“点了但没验证状态变化”的循环。

● Read InSpace.json
│ assets/resource/pipeline/ProtocolSpace/InSpace.json
└ L1:340 (340 lines read)

● Read Manufacturing.json
│ assets/resource/pipeline/DijiangRewards/Manufacturing.json
└ L150:380 (231 lines read)

● Read RecoveryEmotion.json
│ assets/resource/pipeline/DijiangRewards/RecoveryEmotion.json
└ L1:260 (260 lines read)

● Search (grep)
│ "ProductionAssistType|ProductionAssistanceWithoutTheControlNexus|AutoStartExchange|controller|en
│ try" (assets/tasks/DijiangRewards.json)
└ 9 lines found

● Search (grep)
│ "entry|controller|AutoEssenceChallengeMode|controller|group" (assets/tasks/AutoEssence.json)
└ 9 lines found

● Read RecoveryEmotion.json
│ assets/resource/pipeline/DijiangRewards/RecoveryEmotion.json
└ L260:470 (143 lines read)

● Read MainFlow.json
│ assets/resource/pipeline/DijiangRewards/MainFlow.json
└ L1:280 (229 lines read)

● Read DijiangRewards.json
│ assets/tasks/DijiangRewards.json
└ L1:220 (220 lines read)

● Read AutoEssence.json
│ assets/tasks/AutoEssence.json
└ L1:120 (120 lines read)

● Read AutoEssence.json
│ assets/resource/pipeline/AutoEssence/AutoEssence.json
└ L220:340 (121 lines read)

● Search (grep)
│ "MFGCabinMain|GrowthChamberMain|NeedAssistColor|UseAssistText|AssistText|InDijiangControlNexus"
│ in **/*.json (assets/resource/pipeline/DijiangRewards)
└ 18 lines found

基建这条线里，ControlNexus 的分发顺序很关键：它优先跳到 RecoveryEmotionMain，再去会客室/制造舱/培养舱。我现在要确认它是不是把“制造舱/培养舱助力红点”误当成“恢复心情红点”了。

● Read Status.json
│ assets/resource/pipeline/DijiangRewards/Template/Status.json
└ L1:140 (140 lines read)

● Read Location.json
│ assets/resource/pipeline/DijiangRewards/Template/Location.json
└ L150:260 (95 lines read)

● Read Manufacturing.json
│ assets/resource/pipeline/DijiangRewards/Manufacturing.json
└ L1:160 (160 lines read)

● Read GrowthChamber.json
│ assets/resource/pipeline/DijiangRewards/GrowthChamber.json
└ L1:140 (140 lines read)

战斗这条线里，协议空间 的 选择队伍 节点现在非常可疑：它被放在“确认进入”之前，而且只要识别到目标队伍就会反复点，没有“已经选好/应继续点击进入”的状态校验。我再把所有带队伍选择的任务扫一遍，确认是不是它最贴近用户现象。

● Search (grep)
│ "选择队伍|队伍界面|快速编辑队伍|TeamChoose|QuickEdit|开始挑战|开始战斗|进入协议空间|EnterSpaceCo
│ nfirm" in **/*.json (assets/resource/pipeline)
└ 21 lines found

● Search (grep)
│ "TeamChoose|选择队伍|队伍" in *.json (assets/tasks)
└ 17 lines found

● Search (grep)
│ "task.ProtocolSpace|task.AutoEcoFarm|task.AutoEssence|task.DailyRewards|task.DijiangRewards
│ " (assets/locales/interface/zh_cn.json)
└ 40 lines found

● Read AutoEcoFarmPrepare.json
│ assets/resource/pipeline/AutoEcoFarm/AutoEcoFarmPrepare.json
└ L1:220 (65 lines read)

● Read (Explore agent — 探索相关任务)
└ Running

我已经确认了 协议空间 确实有“选择队伍”前置循环风险，但为了避免误判，我再把 🎱基质刷取 的“自动战斗”启动链也对一下，看它有没有类似的“卡在开始前”问题。

● Search (grep)
│ "visitfriends.|ProductionAssist|助力" (assets/locales/go-service/zh_cn.json)
└ 12 lines found

● Search (grep)
│ "AutoEssenceMain|AutoEssenceChallengeEnter|AutoEssenceClickEssenceChallengeUsingAutoFight|AutoFi
│ ght" in *.json (assets/resource/pipeline/AutoEssence)
└ 9 lines found

● Search (grep)
│ "production assist|visitfriends|ProtocolSpaceTeamChoose|RecoveryEmotionMain|MFGCabinAssist|Growt
│ hChamberGrow|UseAssist|No recovery required" in **/*.{go,md,json} (agent/go-service)
└ 34 lines found

● Read AutoEssence.json
│ assets/resource/pipeline/AutoEssence/AutoEssence.json
└ L140:240 (101 lines read)

我刚意识到一个更贴近“有助力红点”的候选：👋拜访好友。它本来就负责“生产助力与情报交流”，而且背后还用了 Go 自定义逻辑。我把这条线也补查一下，避免把“基建收菜”误判成单纯的 🎁基建任务。

● Read VisitFriends.json
│ assets/tasks/VisitFriends.json
└ L1:240 (56 lines read)

● Read visitfriends.go
│ agent/go-service/visitfriends/visitfriends.go
└ L1:260 (260 lines read)

● Read visitfriends.go
│ agent/go-service/visitfriends/visitfriends.go
└ L260:580 (319 lines read)

● Search (grep)
│ "红点|助力|VisitFriends|friend|Assist|Clue|红" in **/*.json
│ (assets/resource/pipeline/VisitFriends)
└ 128 lines found

探索子代理已经跑完了，我先把它的结论并进来，再和刚才手工核对到的节点交叉验证，避免漏掉更贴近 issue 的那条路径。

● Read (Explore agent — 探索相关任务)
└ Completed

● Read Exectue.json
│ assets/resource/pipeline/VisitFriends/Exectue.json
└ L240:450 (211 lines read)

● Read MenuScan.json
│ assets/resource/pipeline/VisitFriends/MenuScan.json
└ L1:180 (122 lines read)

● Read Exectue.json
│ assets/resource/pipeline/VisitFriends/Exectue.json
└ L1:160 (160 lines read)

● Read Main.json
│ assets/resource/pipeline/VisitFriends/Main.json
└ L1:160 (128 lines read)

● Search issues 1770 similar ProtocolSpaceTeamChoose RecoveryEmotion is:issue
└ {"total_count":1,"incomplete_results":false,"items":[{"id":4175692348,"number...

● Search issues "选择队伍" "不开始" is:issue
└ {"total_count":6,"incomplete_results":false,"items":[{"id":4175692348,"number...

👋拜访好友 这条线我也核了：它更像“扫描好友列表再进船协助”，和“看到红点就反复带过去”不太一致。现在我更倾向把第一个现象落在 🎁基建任务 的恢复心情/助力分支，第二个现象落在 ⚔️协议空间 的队伍选择分支。再补一轮相似 issue 搜索后我就写结论。

● Search issues 助力红点基建 is:issue
└ {"total_count":4,"incomplete_results":false,"items":[{"id":4175692348,"number...

● Search issues "好友" 助力 is:issue
└ Output too large to read at once (30.6 KB). Saved to: /tmp/1774931891989-copi...

● Search issues RecoveryEmotion is:issue
└ Output too large to read at once (33.2 KB). Saved to: /tmp/1774931892030-copi...

● Search issues ProtocolSpaceTeamChoose is:issue
└ {"total_count":5,"incomplete_results":false,"items":[{"id":4175692348,"number...

我找到两个很有价值的旁证：#1473 明确提到“基建任务停留在使用助力界面”，#1690 明确提到“协议空间进入时加载慢、四人配队加载慢导致点击过快”。我把这两条的评论和结论拉一下，看看是否能补强 Issue 1770 的证据链。

● Get issue details
└ [{"id":4149409182,"body":"## Issue 概要\n\n- issue：#1690\n- 版本 /
控制器：日志显示实际运行...

● Get issue details
└ {"number":1690,"title":"游戏界面加载慢，点击过快且缺少重试
例如：协议空间+日常奖励领取","body":"### 问题描述及复现...

● Get issue details
└ {"number":1473,"title":"基建任务、信用购物失败","body":"###
问题描述及复现步骤\n\n先做全套日常，基建任务和信用购...

● Get issue details
└ [{"id":4096587225,"body":"👋 你好！我们检测到你的 issue 中包含上传相关的信息。\n\n⚠️
检测到上传失败\n...

我再补一个维度：看看相关文件在最近提交里有没有被修过。要是自 #1473 / #1690 之后这些关键节点基本没变，那“同类问题仍在当前分支存在”的置信度会更高。

● Todo started

● Show recent RecoveryEmotion history (shell)
│ git --no-pager log --oneline -- assets/resource/pipeline/DijiangRewards/RecoveryEmotion.json |
│ head -20
└ 2 lines...

● Show recent ProtocolSpace history (shell)
│ git --no-pager log --oneline -- assets/resource/pipeline/ProtocolSpace/InSpace.json | head -20
└ 2 lines...

● Show recent ProtocolSpace task history (shell)
│ git --no-pager log --oneline -- assets/tasks/ProtocolSpace.json | head -20
└ 2 lines...

最后一步我把英文文案键也对一下，这样 copilot_answer.md 里的英文区块能尽量沿用仓库现有翻译，不会自造术语。

● Search (grep)
│ "task.DijiangRewards.label|task.DijiangRewards.description|option.ProductionAssistanceWitho
│ utTheControlNexus.label|task.ProtocolSpace.label|task.ProtocolSpace.description|option.Pro
│ tocolSpaceTeamChoose.label" (assets/locales/interface/en_us.json)
└ 6 lines found

● Search (grep)
│ "task.DijiangRewards.label|option.ProductionAssistanceWithoutTheControlNexus.label|task.Pro
│ tocolSpace.label|option.ProtocolSpaceTeamChoose.label" (assets/locales/interface/zh_cn.json)
└ 4 lines found

● Read ProtocolSpace.json
│ assets/tasks/ProtocolSpace.json
└ L24:94 (71 lines read)

● Read AutoEssence.json
│ assets/tasks/AutoEssence.json
└ L24:55 (32 lines read)

我补一眼 UseAssistText 的 OCR 模板定义，确认是不是按钮文案本身就只有一层很窄的识别条件；如果是，这能更准确解释为什么会停在“使用助力”界面。

● Read TextTemplate.json
│ assets/resource/pipeline/DijiangRewards/Template/TextTemplate.json
└ L1:60 (60 lines read)

● Read InSpace.json
│ assets/resource/pipeline/ProtocolSpace/InSpace.json
└ L1:130 (130 lines read)

● Read en_us.json
│ assets/locales/interface/en_us.json
└ L130:235 (106 lines read)

● Edit
└ Create copilot_answer.md

结论已经落盘到 copilot_answer.md 了。我再快速自检一下格式和关键链接，确认没有把“无日志”的前提丢掉。

✔ Todo completed issue-1770-answer

● Read copilot_answer.md
└ L1:260 (216 lines read)

● Check answer file status (shell)
│ git --no-pager status --short copilot_answer.md
└ 2 lines...

已完成，最终分析已写入 copilot_answer.md。

结论里我明确注明了 #1770 没有日志包，证据不足，因此本次是基于当前 HEAD 代码和历史同类 issue #1473、#1690 的高相关推断：一条指向 🎁基建任务 的 RecoveryEmotion 助力分支状态覆盖不足，另一条指向 ⚔️协议空间 的 ProtocolSpaceTeamChoose / ProtocolSpaceEnterSpaceConfirm 入场链路容易反复选队而不推进。

Total usage est: 1 Premium request
API time spent: 8m 9s
Total session time: 6m 54s
Total code changes: +217 -0
Breakdown by AI model:
gpt-5.4 1.9m in, 26.2k out, 1.7m cached (Est. 1 Premium request)
claude-haiku-4.5 1.4m in, 13.6k out, 1.3m cached (Est. 0 Premium requests)

🔗 GitHub Action 运行记录

	"ControlNexus": {
	"desc": "[主流程·控制中枢] 识别处于帝江号总控中枢界面，按 next 分发至会客室/制造舱/培养舱/好友助力/滑动等子任务或意外处理",
	"max_hit": 1,
	"recognition": {
	"type": "TemplateMatch",
	"param": {
	"roi": [
	15,
	437,
	225,
	153
	],
	"template": [
	"ClaimDijiangRewards/InControlNexus.png"
	]
	}
	},
	"next": [
	"[JumpBack]RecoveryEmotionMain",
	"[JumpBack]ReceptionRoomMain",
	"[JumpBack]MFGCabinMain",
	"[JumpBack]GrowthChamberMain",
	"FinishDijiangRewards"
	],

	"RecoveryEmotionAssistWindowOpen": {
	"desc": "[恢复心情·助力] 打开助力界面",
	"recognition": "And",
	"all_of": [
	"RecoveryEmotionAssistWindowTitle"
	],
	"pre_wait_freezes": {
	"time": 100,
	"target": "RecoveryEmotionAssistWindowTitle",
	"target_offset": [
	0,
	0,
	200,
	250
	]
	},
	"pre_delay": 0,
	"post_delay": 0,
	"rate_limit": 0,
	"next": [
	"RecoveryEmotionAssistUseAssist"
	]
	},
	"RecoveryEmotionAssistUseAssist": {
	"desc": "[恢复心情·需要助力] 点击使用助力",
	"recognition": {
	"type": "And",
	"param": {
	"all_of": [
	"YellowConfirmButtonType1",
	"UseAssistText"
	],
	"box_index": 1
	}
	},
	"pre_delay": 0,
	"action": {
	"type": "Click"
	},
	"post_delay": 0,
	"rate_limit": 0,
	"next": [
	"RecoveryEmotionView2In"
	]
	},

	"RecoveryEmotionView2In": {
	"desc": "[恢复心情·状态] 已打开「选择待恢复心情的干员」界面，开始选择待恢复心情的干员",
	"recognition": "And",
	"all_of": [
	"RecoveryEmotionAssistView2Label"
	],
	"pre_wait_freezes": {
	"time": 200,
	"target_offset": [
	-300,
	0,
	0,
	150
	]
	},
	"pre_delay": 0,
	"post_delay": 0,
	"rate_limit": 0,
	"next": [
	"RecoveryEmotionSelectLowEmotion"
	]
	},

	"UseAssistText": {
	"desc": "[需要助力] 识别使用助力按钮",
	"recognition": {
	"type": "OCR",
	"param": {
	"roi": "YellowConfirmButtonType1",
	"roi_offset": [
	-125,
	-31,
	130,
	67
	],
	"expected": [
	"使用助力",
	"Use Assist"
	]
	}
	}

	"ProductionAssistanceWithoutTheControlNexus": {
	"type": "switch",
	"label": "$option.ProductionAssistanceWithoutTheControlNexus.label",
	"description": "$option.ProductionAssistanceWithoutTheControlNexus.description",
	"default_case": "No",
	"cases": [
	{
	"name": "Yes",
	"pipeline_override": {
	"RecoveryEmotionMain": {
	"enabled": false
	}
	}
	},
	{
	"name": "No",
	"pipeline_override": {
	"RecoveryEmotionMain": {
	"enabled": true
	}
	}
	}
	]

	"ProtocolSpaceTeamChoose": {
	"type": "select",
	"label": "$option.ProtocolSpaceTeamChoose.label",
	"default_case": "ProtocolSpaceTeamChooseDefault",
	"cases": [
	{
	"name": "ProtocolSpaceTeamChooseDefault",
	"label": "$option.ProtocolSpaceTeamChoose.case.ProtocolSpaceTeamChooseDefault.label",
	"pipeline_override": {
	"ProtocolSpaceTeamChoose": {
	"enabled": false
	}
	}
	},
	{
	"name": "ProtocolSpaceTeamChoose01",
	"label": "01",
	"pipeline_override": {
	"ProtocolSpaceTeamChooseTextRecognition": {
	"expected": [
	"01"
	]
	}
	}
	},
	{
	"name": "ProtocolSpaceTeamChoose02",
	"label": "02",
	"pipeline_override": {
	"ProtocolSpaceTeamChooseTextRecognition": {
	"expected": [
	"02"
	]
	}
	}
	},
	{
	"name": "ProtocolSpaceTeamChoose03",
	"label": "03",
	"pipeline_override": {
	"ProtocolSpaceTeamChooseTextRecognition": {
	"expected": [
	"03"
	]
	}
	}
	},
	{
	"name": "ProtocolSpaceTeamChoose04",
	"label": "04",
	"pipeline_override": {
	"ProtocolSpaceTeamChooseTextRecognition": {
	"expected": [
	"04"
	]
	}
	}
	},
	{
	"name": "ProtocolSpaceTeamChoose05",
	"label": "05",
	"pipeline_override": {
	"ProtocolSpaceTeamChooseTextRecognition": {
	"expected": [
	"05"
	]
	}
	}
	}
	]
	},

	"ProtocolSpaceEnterSpace": {
	"desc": "进入协议空间",
	"recognition": "Or",
	"any_of": [
	"WhiteConfirmButtonType1",
	{
	"recognition": "OCR",
	"roi": [
	-250,
	-150,
	250,
	150
	],
	"expected": [
	"进入",
	"進入",
	"Enter"
	]
	}
	],
	"action": "Click",
	"post_wait_freezes": 500,
	"next": [
	"[JumpBack]ProtocolSpaceTeamChoose",
	"ProtocolSpacePopupSanityLow",
	"ProtocolSpaceEnterSpaceConfirm"
	],

	"ProtocolSpaceTeamChooseTextRecognition": {
	"desc": "识别协议空间队伍",
	"recognition": "OCR",
	"roi": [
	0,
	-60,
	500,
	35
	],
	"expected": [
	"01"
	]
	},
	"ProtocolSpaceTeamChoose": {
	"desc": "选择协议空间队伍",
	"recognition": "And",
	"all_of": [
	"ProtocolSpaceTeamChooseTextRecognition",
	{
	"recognition": "ColorMatch",
	"roi": "ProtocolSpaceTeamChooseTextRecognition",
	"roi_offset": [
	-30,
	0,
	10,
	0
	],
	"lower": [
	30,
	30,
	30
	],
	"upper": [
	45,
	45,
	45
	],
	"connected": true
	}
	],
	"pre_delay": 0,
	"action": "Click",
	"post_wait_freezes": 200,
	"post_delay": 0,
	"focus": {
	"Node.Action.Succeeded": "选择队伍"
	}
	},

	"ProtocolSpaceEnterSpaceConfirm": {
	"desc": "确认进入协议空间",
	"recognition": "Or",
	"any_of": [
	"YellowConfirmButtonType2",
	{
	"recognition": "OCR",
	"roi": [
	-250,
	-150,
	250,
	150
	],
	"expected": [
	"进入",
	"進入",
	"Enter"
	]
	}
	],
	"pre_wait_freezes": 400,
	"action": "Click",
	"next": [
	"[JumpBack]SceneWaitLoadingExit",
	"ProtocolSpaceEnterSpaceSuccess"
	],

	"option": {
	"AutoEssenceChallengeMode": {
	"type": "select",
	"label": "$option.AutoEssenceChallengeMode.label",
	"description": "$option.AutoEssenceChallengeMode.description",
	"default_case": "Walk",
	"cases": [
	{
	"name": "Walk",
	"label": "$option.AutoEssenceChallengeMode.cases.Walk.label",
	"pipeline_override": {
	"AutoEssenceClickEssenceChallengeUsingWalk": {
	"enabled": true
	},
	"AutoEssenceClickEssenceChallengeUsingAutoFight": {
	"enabled": false
	}
	}
	},
	{
	"name": "AutoFight",
	"label": "$option.AutoEssenceChallengeMode.cases.AutoFight.label",
	"pipeline_override": {
	"AutoEssenceClickEssenceChallengeUsingWalk": {
	"enabled": false
	},
	"AutoEssenceClickEssenceChallengeUsingAutoFight": {
	"enabled": true
	}
	}
	}
	]

基建收菜，和自动战斗 #1770

Description

问题描述

MaaEnd 版本

其他信息

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions