release: 2.10.0: inbound-upstream-result - the upstream's answer in the Inbound log

Cut at the owner's word (2026-10-16): "потом режь" after the check, which
he allowed ("Отправляй").

Inbound › Log says what became of accepted mail - queued, held, sent,
deferred, bounced - with the upstream's last reply, the host and when
(5348330, 295d72e, 46b90d2 design and plan; d515493 code, the reviews'
findings fixed in it). Migration 0012, schema 12.

On the test server as 2.9.1-post.d515493 (the same code), 2026-10-16:
healthy, every program RUNNING, keys unchanged, schema 12. One message
sent from the server to its own port 25 for selfpost@dev.mixdep.ru: its
row sent, "250 2.0.0 Ok: queued as 04F0D1023EF" from mc-ent.mixfed.ru. (The
owner's own message had gone to mc-ent directly: SelfPost is
dev.mixdep.ru's second MX.)

CHANGELOG [2.10.0]; pins in deploy/docker-compose.yml, README and the guide
(pin, build, the sample restore message); development's "from pin" and row
32; roadmap row and recommended order; plan closed. No tag.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/plans/inbound-upstream-result.md

@@ -1,6 +1,6 @@
 # inbound-upstream-result
 
-**Status:** agreed 2026-10-16; one stage, `2.10.0`.
+**Status:** shipped `2.10.0` (2026-10-16).
 
 ## Problem
 
@@ -94,4 +94,7 @@ finding became:
 - [x] e2e: a relayed message's row shows `sent` with the sink's `250`; an
   upstream that refuses connections shows `deferred` with the reason.
 - [x] Docs. *Done (2026-10-16), with the reviews' findings above.*
-- [ ] Roll out, read the server's journal; cut `2.10.0`.
+- [x] Roll out, read the server's journal; cut `2.10.0`. *Done (2026-10-16): on the
+  test server as 2.9.1-post.d515493, a message to selfpost@dev.mixdep.ru through
+  port 25 - its row sent, mc-ent.mixfed.ru's "250 2.0.0 Ok: queued as
+  04F0D1023EF" on it.*