Pod linked a transaction to its journal entry through the transaction's journal_ref_id. For a trade that settles at once that field holds the id of the trade's own market_transaction journal row, but for a sell-order fill ESI fills it with an id two past that row, on an id the wallet never receives. The join found nothing, the assignment was dropped, and the chip stayed amber. The same skew explains the transaction row disagreeing with its journal twin: assigning from the journal row keys on the row's real id, while the transaction row read through the bad ref. Both paths now resolve the id the same way, off the journal row's own context_id back-link, which is sound for every trade; journal_ref_id remains the fallback for a trade whose twin has not synced yet. The owner axis is unchanged, since read and write already agreed there. A write the ownership guard drops now logs instead of vanishing, which is what let this hide for a release. Closes #68 Closes #65