Alejandro Gutiérrez 8697c1c032 fix(api+cli): topic post messageId is the durable historyId (v1.9.2) ...

Previously POST /v1/messages returned the message_queue row id as
`messageId`. Topic posts ARE durable (in topic_message); the queue
entry drains on delivery. Pasting that id into `--reply-to` failed
because the broker validates parents against topic_message, not the
queue. Now `messageId` aliases `historyId` for topic posts; both
`historyId` and `queueId` remain available as explicit fields.

Roadmap and CLI README updated with v0.3.1 reply-to + v0.3.2
multi-session entries.

2026-05-02 22:10:13 +01:00

1.8 KiB

Raw Blame History

View Raw