AskaEth
bc0047b449
design/11 §7.1（主人 2026-10-03 拍板）。此前 hub.broadcast 是全连接广播，而任意角色
（含 viewer）都能连 /ws/chat ⇒ viewer 能收到角色回复正文（message.*）、推理内容
（thinking.*）、消息增量、graph_update、mood 等。这与 design/19 §1/§3「flow 可视化仅
owner/admin 可见」冲突，也与 GET /sessions/{id}/messages 的 owner/admin 档位不一致。
收口：唯一分类点 internal/services/gateway/ws_frame_scope.go 的 frameReachesAll(typ)
（fail-closed switch，默认 false）；hub.broadcast 投递前查表，白名单外对非 owner/admin
连接直接跳过。**不给 broadcast 加 bool 参数、不让调用点自己判断** —— 那正是"漏一处就是
泄漏"的形状。全包只有一个 fan-out 循环，14 个 .broadcast( 调用点全部落进该入口。
- 白名单只有 7 个状态机信号帧（不含任何内容）：session_busy / pending_ack / pending_drain /
session_idle / session_interrupted / pending_full / session_read
- 其余全部（流式 message/thinking/tool_call、message_persisted/edited/deleted、graph_update、
subagent_event/result、task_output/task_done、automation_result、tool_used、capacity_awaken、
mode_switch、mood、device_update、reminder）仅 owner+admin
- 语义澄清：本门管「谁被主动推送」，数据可见性仍由 REST 决定（viewer 的 12 条只读监控端点
不变，含 GET /personas 的 mood）；/ws/chat 连接鉴权与 voice_output 定向帧不动
契约：Docs/api-client.md → v0.48（对 viewer 是收紧；owner/admin 零变化；无端点/字段形状变更）
验证：go build/vet 绿；go test ./... = 58 包 ok / 0 FAIL；-race ./internal/services/gateway/... ok；
linux/amd64 + darwin/arm64 交叉编译绿。真 httptest WS + 真 JWT 按角色逐帧实测 37 帧：
viewer 只收到 7 个状态信号，owner/admin 37/37。
变异验证：① graph_update 加回白名单 → 真 WS 抓到 viewer 收到 graph_update，3 个测试 FAIL；
② session_idle 移出白名单 → 3 个测试 FAIL（viewer 等不到哨兵帧而超时）。均已还原。
遗留（已登记，待主人裁决）：① 握手 history 回放对任意角色照发（viewer 连上即得主会话最近
50 条正文）；② /ws/chat 上行未按角色授权（viewer 可发 chat = 真驱动模型并落库；
subagent_ask / task_output_query 的定向应答绕过本门）。
32 lines
1.7 KiB
Go
32 lines
1.7 KiB
Go
package gateway
|
|
|
|
// wsMessageEdited / wsMessageDeleted are the downstream event types of the D3
|
|
// history writes: a message's content was edited, or a message was removed. Both
|
|
// reuse the wsEvent envelope and the same fan-out as `message_persisted` — and,
|
|
// like it and every other content frame, they are owner/admin only under the
|
|
// design/11 §7.1 frame gate. The hub has no per-session subscription, so the frame
|
|
// carries SessionID and a client filters it by its active session, exactly as it
|
|
// does for message_persisted.
|
|
const (
|
|
wsMessageEdited = "message_edited"
|
|
wsMessageDeleted = "message_deleted"
|
|
)
|
|
|
|
// broadcastMessageEdited fans a content edit out to the owner/admin connections as
|
|
// a `message_edited` frame whose data is the updated message DTO. The frame is a
|
|
// render-only sync: the edited content's single source of truth stays the history
|
|
// store, so a client that missed the frame converges again on its next read. The
|
|
// caller strips Thinking to match the message_persisted/replay contract.
|
|
func (h *hub) broadcastMessageEdited(msg historyMessage) {
|
|
h.broadcast(wsEvent{Type: wsMessageEdited, SessionID: msg.SessionID, Data: msg})
|
|
}
|
|
|
|
// broadcastMessageDeleted fans a removal out to the owner/admin connections as a
|
|
// `message_deleted` frame carrying the removed id (plus the owning sessionId for
|
|
// client-side session filtering), so every browser of the account drops the row
|
|
// without a refresh. sessionID may be empty when the store could not report it;
|
|
// clients then fall back to the globally unique id.
|
|
func (h *hub) broadcastMessageDeleted(sessionID, id string) {
|
|
h.broadcast(wsEvent{Type: wsMessageDeleted, SessionID: sessionID, Data: map[string]any{"id": id}})
|
|
}
|