① 一句话需求

运营按 BRAND_A／BRAND_B × 客户端 H5／代理后台 H5 建立最多 10 个导航项目，再从项目库任意组合成 3 项或 5 项策略；同一范围可有多套策略，但最多启用一套。

② 核心模型

③ 本期与不做

④ 全局红线表

1.4 配置流程

1.4.1 新增与复制共用同一编辑、校验及保存流程；复制只负责预填来源范围、组合与顺序。

flowchart TD
    scope([选择用户渠道与使用端]) --> library[维护导航项目库]
    library --> editor[新增或复制策略]
    editor --> choose[勾选同范围项目]
    choose --> count{恰为 3 项或 5 项}
    count -->|否| blocked[阻断保存]
    count -->|是| order[调整显示顺序]
    order --> preview[预览中间突起位置]
    preview --> save[保存为禁用]
    save --> activate{启用}
    activate -->|同范围已有启用| blockedEnable[提示先禁用原策略]
    activate -->|没有冲突| h5[H5 下次读取新版本]

2.1 字段

2.1.1 项目库列表提供用户渠道、使用端、状态与后台名称搜索；前三项都保留 All。项目库共用一个页面，不按客户端／代理后台拆成两套菜单。

2.1.2 新增导航项目时，在新增页以基础 radio button 选择用户渠道与使用端；编辑既有项目时，两组 radio button 维持可见但禁用，只可修改后台名称、跳转页面、一般图标与中间图标。系统编号由保存后自动产生，新增与编辑表单都不显示，只在项目库列表等建立后情境显示。

2.1.3 原型每个范围提供 6 笔范例资料，用来实际验证可继续新增至第 10 笔；范例数量与内容不代表上线预置值。

2.2 约束与影响

2.2.1 页面白名单不提供 URL；不收外链、单一游戏、特定活动或带业务对象的深层页面。目标页面既有的登录限制、权限检查与登录后返回逻辑维持不变，本需求只配置入口。图标没有选中态。

2.2.2 新增第 11 个项目时阻断。被任一未删除策略引用的项目不得禁用或删除，须先移出所有策略；无引用项目点击「禁用」时须二次确认，确认后列表状态改为红字「禁用」。

2.2.3 编辑项目备注必填。若新目标会让任一引用策略出现重复页面，整次保存阻断；本页不显示引用策略明细。

3.1 列表与字段

3.1.1 列表筛选的用户渠道、使用端与状态都保留 All；策略名称支持关键字查询。新增／编辑时必须指定单一范围。

3.1.2 状态只使用后台既有文字形制：启用 为一般文字，禁用 为红字，不使用徽章或胶囊。

3.1.3 策略编辑器的用户渠道、使用端与导航数量选项都少且固定，使用 radio button 平铺；列表搜索区因含 All，继续使用下拉选单。

3.1.4 策略编号由保存后自动产生；新增、复制与编辑表单都不显示策略编号，只在策略列表等建立后情境显示。

3.2 选择、排序与预览

3.2.1 编辑器左侧列出同范围最多 10 个启用项目供勾选；右侧依选择顺序列出已选项目，可移除及上／下调整。实时显示 已选 n／3 或 已选 n／5，超过目标数时不得继续勾选。

3.2.2 选择 3 项时第 2 项使用中间图；选择 5 项时第 3 项使用中间图。运营不另选中间项目，顺序变化后预览自动重算。

3.2.3 保存时校验：项目数、范围、项目状态、项目 ID 不重复、目标页面不重复及配置版本。任一失败则整单不写入。

3.2.4 新增时若已选项目后切换用户渠道或使用端，须先确认；确认后清空选择。编辑既有策略时范围不可修改。

3.3 复制策略

3.3.1 列表的「复制」会开启新增策略编辑器，复制来源策略的范围、3／5 项模式、项目组合与顺序；策略编号重新生成，名称预填「{原策略名称}－副本」，状态固定为禁用。

3.3.2 复制不会直接保存，也不会复制启用状态、备注、建立人或更新时间。若来源项目已不可用，须标红并替换后才能保存；保存仍执行 §3.2.3 全部校验。

3.4 启用、禁用与删除

3.4.1 启用前显示名称与范围并要求备注。若同范围已有启用策略，本次阻断，必须由运营先禁用原策略，系统不得自动切换。

3.4.2 禁用前提示该范围可能隐藏底部导航并要求备注；确认后状态改为禁用。只有禁用策略可软删除。

3.5 并发

3.5.1 两人从同一版本编辑时，先提交者成功；后提交者整单拒绝并要求刷新，不得覆盖。

6.1 后台提示语

6.2 开放项

① Requirement in One Sentence

Operations maintains up to ten navigation items for each BRAND_A/BRAND_B × Client H5/Agent Backoffice H5 scope, combines any three or five into strategies, and may activate at most one strategy in each scope.

② Core Model

③ In Scope and Out of Scope

④ Global Invariants

1.4 Configuration Flow

flowchart TD
    scope([Select Platform and Surface]) --> library[Maintain item library]
    library --> editor[Create or copy strategy]
    editor --> choose[Select same-scope items]
    choose --> count{Exactly 3 or 5 items}
    count -->|No| blocked[Block save]
    count -->|Yes| order[Arrange display order]
    order --> preview[Preview raised center]
    preview --> save[Save as disabled]
    save --> activate{Enable}
    activate -->|Another is active| blockedEnable[Disable original first]
    activate -->|No conflict| h5[H5 reads next version]

2.1 Fields

2.1.1 The item-library list supports Platform, Surface, Status, and Backoffice Name search. The first three retain All. One shared page covers every scope; Client H5 and Agent Backoffice H5 do not use separate menu entries.

2.1.2 On navigation-item creation, select Platform and Surface on the create page with basic radio buttons. When editing an existing item, keep both radio groups visible but disabled; only Backoffice Name, Target Page, General Image, and Center Image are editable. The system generates the ID after save, so create and edit forms omit it; post-creation contexts such as the item-library list may display it.

2.1.3 The prototype provides six sample items per scope so creating additional items up to the tenth can be exercised. Sample count and content are not production seed data.

2.2 Constraints and Impact

2.2.1 The target selector exposes no URL. External links, individual games, specific campaigns, and object-specific deep links are unavailable. Existing login restrictions, permission checks, and post-login return behavior remain owned by the target page; this requirement only configures the entry point. There is no selected-state asset.

2.2.2 Creating the eleventh item is blocked. An item referenced by any non-deleted strategy cannot be disabled or deleted until removed from every strategy. Disabling an unreferenced item requires confirmation and then changes the list status to red Disabled text.

2.2.3 Item-edit remarks are required. If the new target would duplicate a target in any referencing strategy, reject the entire save. Do not display referencing-strategy details on this page.

3.1 List and Fields

Platform, Surface, and Status filters all retain All; Strategy Name supports keyword search. Create and edit always use one exact scope.

Use the existing text-only backoffice status style: Enabled is ordinary text and Disabled is red text. Do not use badges or pills.

The Strategy Editor has only a few fixed Platform, Surface, and Navigation Count values, so display them as radio buttons. List filters retain dropdowns because they also include All.

The system generates the Strategy ID after save. Create, copy, and edit forms omit it; post-creation contexts such as the strategy list may display it.

3.2 Selection, Order, and Preview

3.2.1 The left panel lists up to ten enabled items from the exact scope. The right panel contains selected items in display order with Remove, Up, and Down controls. Show Selected n/3 or Selected n/5 live and prevent further selection at the limit.

3.2.2 For three items, position two uses the center image. For five items, position three uses it. Operations never designates the center item; order changes recalculate the preview.

3.2.3 Save validates count, scope, item status, unique item IDs, unique target pages, and configuration version. Any failure writes nothing.

3.2.4 When creating a strategy, changing Platform or Surface after selecting items requires confirmation and clears the selection. Existing strategies cannot change scope.

3.3 Copy Strategy

3.3.1 Copy opens the create editor with the source scope, three/five-item mode, item combination, and order. Generate a new strategy ID, prefill {Original Strategy Name} - Copy, and force the status to Disabled.

3.3.2 Copy does not save automatically and does not copy active status, remarks, creator, or update time. Unavailable source items are highlighted and must be replaced. The full §3.2.3 validation still applies.

3.4 Enable, Disable, and Delete

3.4.1 Enabling shows the name and scope and requires remarks. If another strategy is active in the scope, block the action and require Operations to disable the original first. The system never switches automatically.

3.4.2 Disabling warns that the scope may lose its bottom navigation and requires remarks. Confirmation changes status to Disabled. Only disabled strategies may be soft-deleted.

3.5 Concurrency

When two operators edit the same base version, the first submission succeeds. Reject the later submission in full and require a refresh.

6.1 Backoffice Copy

6.2 Open Points