{"repo":"NousResearch/hermes-agent","public_id":"75939","display_label":"Feishu thread and topic message/media send routing issues","summary":"These items concern sending messages or media into Feishu threads or topics, with two titles describing routing such sends through the reply API rather than using thread_id as receive_id. One title reports a field validation error ([99992402]) for file/media sends into a thread.","subsystem":"gateway","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":75939,"title":"[Bug] Feishu file/media sends into a thread fail with [99992402] field validation failed","url":null,"state":"open"},{"kind":"pr","number":75940,"title":"fix: route feishu thread sends via reply API instead of invalid thread_id receive_id","url":null,"state":"open","close_reason":{"refs":[{"kind":"pr","value":"#135933","number":135933}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":141924,"title":"fix(feishu): route topic media through the reply API","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}