docs(patrol): add install command + Slack branding config (2026-05-30)

[aaronwong1989]

文档巡逻 2026-05-30

自 a8499cd 以来 12 个提交，经分析 2 篇文档需要维护。

修复内容

docs/reference/cli.md
  + 命令树添加 install 节点
  + 新增 hotplex install 命令参考段落（--path / --force 标志）

docs/reference/configuration.md
  + §3.11.5 Slack 专有配置：添加 display_name / icon_emoji 字段
  + §3.11.8 SlackBotConfig：添加 display_name / icon_emoji bot 级覆盖字段

变更来源

• c09422c feat: install command (feat: install command + webchat cron fix + gateway TurnCount persist #555)
• 0ba0550 feat(messaging/slack): Assistant branding + DataTableBlock (feat(slack): adopt Block Kit 2026 new blocks (Alert/DataTable/Card/Carousel) #565)

未修改（经阅读确认无影响）

• tutorials/slack-integration.md — branding 为配置级行为，教程不涉及
• explanation/* — 无架构变更
• Bug fix 提交（fix: batch — 5 high-ROI fixes for #501 #527 #526 #510 #544 #564, fix(batch): error-handling & reliability fixes for #532, #522, #535, #533 #557, fix(ux): dev mode lockout warning + webchat 401 guidance + font preload trim #561, fix(gateway): populate metadata in synthetic events (#559) #563）— 内部修复，不影响文档
• ACP Worker spec (feat(worker/acp): ACP Worker integration spec with cross-review #570) — specs/ 不在巡逻范围

[hotplex-ai]

Code Review — hotplex-ai

Verdict: APPROVE | P0:0 P1:0 P2:0 P3:2

• [P3] Flag table column schema inconsistency between install and update sections (docs/reference/cli.md:318) — The hotplex update flag table (line 318) uses 5 columns: 标志 | 短标志 | 类型 | 默认值 | 说明. The new hotplex install flag table (added in this PR) uses only 4 columns: 标志 | 类型 | 默认值 | 说明, omitting the 短标志 column. While the install command has no short flags (confirmed in cmd/hotplex/install.go), omitting the column breaks visual consistency with the update table directly above it. Best practice for doc consistency: include the 短标志 column with empty cells to maintain a uniform table schema across the same document.
  

  hotplex/docs/reference/cli.md

  Lines 317 to 319 in 698b5ee

  	|------|------|--------|------|
  	| `--path` | `string` | `~/.local/bin` | 目标安装目录 |
  	| `--force` | `bool` | `false` | 即使已安装也重新安装 |

• [P3] SlackBotConfig doc table omits pre-existing per-bot access control fields (work_dir, dm_policy, group_policy, require_mention, allow_from, allow_dm_from, allow_group_from) (docs/reference/configuration.md:449) — The SlackBotConfig table at line 449 lists only name, bot_token, app_token, worker_type, stt_, tts_. However, the actual struct in internal/config/config.go (lines 279-299) also has work_dir, dm_policy, group_policy, require_mention, allow_from, allow_dm_from, allow_group_from fields. This is a pre-existing gap (not introduced by this PR), but this PR adds display_name and icon_emoji to the same table while the access control fields remain undocumented. The PR should ideally either document all missing fields or note them as intentionally omitted, to avoid giving a false impression of completeness after the branding additions.
  

  hotplex/docs/reference/configuration.md

  Lines 448 to 450 in 698b5ee

  	|------|------|------|
  	| `name` | string | Bot 名称（同一平台内唯一，必填） |
  	| `bot_token` | string | Slack Bot Token（`xoxb-...`） |

[hotplex-ai]

Code Review — hotplex-ai

Verdict: APPROVE | P0:0 P1:0 P2:0 P3:2

• [P3] Flag table column schema inconsistency between install and update sections (docs/reference/cli.md:318) — The hotplex update flag table (line 318) uses 5 columns: 标志 | 短标志 | 类型 | 默认值 | 说明. The new hotplex install flag table (added in this PR) uses only 4 columns: 标志 | 类型 | 默认值 | 说明, omitting the 短标志 column. While the install command has no short flags (confirmed in cmd/hotplex/install.go), omitting the column breaks visual consistency with the update table directly above it. Best practice for doc consistency: include the 短标志 column with empty cells to maintain a uniform table schema across the same document.
  

  hotplex/docs/reference/cli.md

  Lines 317 to 319 in 698b5ee

  	|------|------|--------|------|
  	| `--path` | `string` | `~/.local/bin` | 目标安装目录 |
  	| `--force` | `bool` | `false` | 即使已安装也重新安装 |

• [P3] SlackBotConfig doc table omits pre-existing per-bot access control fields (work_dir, dm_policy, group_policy, require_mention, allow_from, allow_dm_from, allow_group_from) (docs/reference/configuration.md:449) — The SlackBotConfig table at line 449 lists only name, bot_token, app_token, worker_type, stt_, tts_. However, the actual struct in internal/config/config.go (lines 279-299) also has work_dir, dm_policy, group_policy, require_mention, allow_from, allow_dm_from, allow_group_from fields. This is a pre-existing gap (not introduced by this PR), but this PR adds display_name and icon_emoji to the same table while the access control fields remain undocumented. The PR should ideally either document all missing fields or note them as intentionally omitted, to avoid giving a false impression of completeness after the branding additions.
  

  hotplex/docs/reference/configuration.md

  Lines 448 to 450 in 698b5ee

  	|------|------|------|
  	| `name` | string | Bot 名称（同一平台内唯一，必填） |
  	| `bot_token` | string | Slack Bot Token（`xoxb-...`） |