You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(transport): make DM-listing/follow-up fetches transport-aware (Codex review)
Addresses the Codex P2 on PR #177: the range-order child-order follow-up
fetched after a `release` (send_msg.rs) used `create_filter(DirectMessagesUser,
…)`, whose DirectMessages branch hard-coded `Kind::GiftWrap`. On a v2 node the
child `NewOrder` is a kind-14 event authored by Mostro, so it was never fetched
and `print_commands_results` never ran.
Fix: make `create_filter` transport-aware for the `DirectMessages*` kinds —
`transport.event_kind()` plus an `author = mostro_pubkey` pin on v2 (new
`mostro_pubkey` param threaded through its call sites + the integration test).
This also makes the `get-dm` historical listing v2-aware, so the whole
interactive path is fully v2 (spec note updated; the item is no longer deferred
to Phase 3).
cargo build/test/clippy --all-targets --all-features -D warnings/fmt all clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0 commit comments