fix: drop stale hardcoded sidechat UUID, use job-sidechats.json mapping
- bin/dm.py: remove 646 tasks -> 1e75a740 from SIDCHAT_ALIASES. That UUID is stale (not a valid thread on 646 account; SPA redirects elsewhere, causing misdelivery). Alias now falls through to job-sidechats.json/autoprovision. Do NOT re-add hardcoded UUIDs. - job-sidechats.json: live autoprovisioned mappings for 646-pip and 646 tasks (2026-10-04). - bin/box-chat-cdp.py: CDP robustness -- drain events until command response, retry switcher lookup while SPA settles, fresh reconnect per retry (transient NO_SWITCHER on pip/opm 2026-10-04). Session: sidechat/uuid-stale-fix
This commit is contained in:
@@ -206,9 +206,14 @@ LOG_FILE = "/home/super/Projects/NetVM/dm-log.jsonl"
|
||||
# Resolved 2026-10-04. Add new entries as sidechats are created.
|
||||
SIDCHAT_ALIASES = {
|
||||
"646-opm-work": "d410b9ad-f667-465f-a103-43fabc0f69fe",
|
||||
"646 tasks": "1e75a740-d08f-443d-a0f9-793db196e24f",
|
||||
"heartbeat": "0077e918-9ac8-40ba-b0ad-65f9f78037c4", # dedicated heartbeat sidechat (was colliding with 646 tasks)
|
||||
}
|
||||
# NOTE 2026-10-04: "646 tasks" alias REMOVED -- the hardcoded UUID
|
||||
# 1e75a740-d08f-443d-a0f9-793db196e24f is stale (not a valid thread on 646's
|
||||
# account; the SPA redirects to another thread, causing misdelivery).
|
||||
# "646 tasks" now falls through to passthrough -> fuzzy name search ->
|
||||
# autoprovision, which registers the live UUID in job-sidechats.json.
|
||||
# Do NOT re-add a hardcoded UUID here; use job-sidechats.json instead.
|
||||
|
||||
def resolve_sidechat_target(target):
|
||||
"""Resolve target alias or name to UUID dynamically from job-sidechats.json."""
|
||||
|
||||
Reference in New Issue
Block a user