I should add a comment for this, but in most cases uri is on the same page (just with a different anchor), so browsers navigate to the anchor but don't reload the page. This puts the browser window in the right place, but the user sees the old content.

Explicitly reloading afterward effects "forcefully reload the page, even if it's the current page". This feels a bit iffy and I'd rather just do it on the server side, but we can't always tell what the right detail page is based on a transaction right now (in most cases it's the object monogram page, but in some cases the transaction history is on some separate page), and I don't want to just pass "?redirect=T123#asdf" because semi-open redirects can, e.g., interact with OAuth in dangerous/scary ways and we don't really need to perform one here.

We probably should have some method on Transaction like getTheURIToGoBackToAfterMakingAnEdit(), but then what if there's more than one URI, and probably no one will ever remember to implement that, so despite being a little rough this felt like the most reasonable thing for now to me. I'll make a note about it, though, at least.