#3695 Docs: issue redaction keeps git ids and non-address colon runs, and asks before posting (swamp-club#3686)

What changed

swamp-club#3686 changes swamp issue redaction (bug, feature, security, edit, ripple):

• A 40 or 64 character hex run right after a git word (commit, sha, rev, git checkout/show/revert/cherry-pick/reset, or a /commit/, /commits/, /tree/, /blob/ URL segment) is kept as a git object id, unless a secret label (token, key, password, secret, auth, credential, signature, hmac) appears in the 40 characters before it.
• IPv6 detection judges each colon-joined token: a run is an address with eight or more groups, a double colon, an embedded IPv4 tail, or six consecutive two-hex groups (a MAC). Runs that cannot hold an address (fast-check replay paths, timestamps, code paths such as Foo::bar and AWS[IP-1]::VPC, all-zero runs such as passwd fields) are kept. A one-colon label (remote_addr:) stays outside the placeholder.
• On an interactive terminal in log mode, when anything was redacted, the command asks: y submits the redacted text, w submits it as written (logged like --no-redact), anything else cancels and nothing is sent. json mode and non-terminal stdin are unchanged.

Pages to update

• content/manual/reference/issue-commands.md, Redaction section: the Secret row says long hex strings are redacted; add the git-id exception and the IPv6 rules above, and describe the confirmation prompt.
• content/manual/how-to/file-issues-from-the-cli.md, "Check what was redacted": the command now asks before sending in an interactive terminal; mention the y/w/N choice next to --no-redact.