docs(honcho): prune wizard and peers-map comments
The picker-cap comment repeated the constant's name; the sessionAiPeerPrefix field comment restated the field name and its symmetry with sessionPeerPrefix before reaching the collision it prevents. Both now state only the why.
This commit is contained in:
@@ -1146,8 +1146,7 @@ def _preview_peer_resolution(
|
||||
return sanitize(user_id)
|
||||
|
||||
|
||||
# Picker cap: workspaces holding thousands of peers (public bots) must not
|
||||
# stall the CLI on an exhaustive listing.
|
||||
# Workspaces holding thousands of peers (public bots) must not stall the CLI.
|
||||
_PEERS_MAP_FETCH_CAP = 200
|
||||
|
||||
|
||||
|
||||
@@ -395,8 +395,8 @@ class HonchoClientConfig:
|
||||
session_peer_prefix: bool = False
|
||||
# Bot-authored DMs write into their own session per sender bot.
|
||||
a2a_sessions: bool = True
|
||||
# Symmetric to session_peer_prefix: several AI peers sharing one workspace, peerName and gateway
|
||||
# chat key would otherwise resolve to the same session name.
|
||||
# Prefixes every resolved session name with ``{ai_peer}-``. The gateway_session_key branch is
|
||||
# AI-peer-agnostic, so several AI peers sharing one workspace + peerName + chat key would collide.
|
||||
session_ai_peer_prefix: bool = False
|
||||
sessions: dict[str, str] = field(default_factory=dict)
|
||||
raw: dict[str, Any] = field(default_factory=dict)
|
||||
|
||||
Reference in New Issue
Block a user