doc: regenerate manpages for v1.2.0

They still described v1.0.3-4caf2fc68, so none of the options added
since -- -autoshield and its four companions, -mnemonic,
-mnemonicsaplinggap -- appeared anywhere in them.

Generated from a binary built at a clean tree on an annotated v1.2.0
tag, which is what makes util/genbuild.sh emit BUILD_DESC "v1.2.0"
rather than a version with a commit suffix. Note that genbuild.sh uses
`git describe --abbrev=0`, which ignores lightweight tags; v1.0.0
through v1.0.3 were lightweight, which is why those releases all
reported themselves as v1.0.x-<sha>. Tag releases annotated.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FU87LdsJZiZkfq1eXubpeo

doc/man/dragonx-tx.1

@@ -1,9 +1,9 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.49.1.
-.TH DRAGONX-TX "1" "July 2026" "dragonx-tx v1.0.3-4caf2fc68" "User Commands"
+.TH DRAGONX-TX "1" "August 2026" "dragonx-tx v1.2.0" "User Commands"
 .SH NAME
-dragonx-tx \- DragonX transaction utility
+dragonx-tx \- manual page for dragonx-tx v1.2.0
 .SH DESCRIPTION
-hush\-tx utility version v1.0.3\-4caf2fc68
+hush\-tx utility version v1.2.0
 .SS "Usage:"
 .TP
 hush\-tx [options] <hex\-tx> [commands]
@@ -84,3 +84,22 @@ Load JSON file FILENAME into register NAME
 set=NAME:JSON\-STRING
 .IP
 Set register NAME to given JSON\-STRING
+.SH COPYRIGHT
+
+In order to ensure you are adequately protecting your privacy when using
+DragonX, please see <https://dragonx.is/security/>.
+
+Copyright (C) 2024-2026 The DragonX Developers
+
+Copyright (C) 2016-2024 Duke Leto and The Hush Developers
+
+Copyright (C) 2016-2020 jl777 and SuperNET developers
+
+Copyright (C) 2016-2018 The Zcash developers
+
+Copyright (C) 2009-2014 The Bitcoin Core developers
+
+This is experimental Free Software! Fuck Yeah!!!!!
+
+Distributed under the GPLv3 software license, see the accompanying file COPYING
+or <https://www.gnu.org/licenses/gpl-3.0.en.html>.