#3686 swamp issue redacts git commit SHAs as secrets and fast-check replay paths as IP addresses

What happens

Filing swamp-club#3685 with swamp issue bug --body, the pre-post redaction replaced a full 40-character git commit id with the marker REDACTED-SECRET-1 and replaced a fast-check replay path (six integers separated by colons, the path fast-check prints next to the seed) with the marker IP-1. Both values were the reproduction data the report existed to carry, and the command posted the redacted body without asking.

Expected

A hexadecimal string that is exactly a git object id (40 or 64 hex characters, or a 7 to 12 character abbreviation) is not a credential and should be kept. A colon-separated run of integers is only an IPv6 candidate when the groups are hexadecimal of at most four characters and there are at most eight of them; a six-group path with a group of three decimal digits above 255 is not an address. When the redactor does change the body, the command should show the before and after and let the author confirm or adjust before posting, instead of only echoing the redactions in the JSON output after the post.

Where

The redaction summary the command prints lists each change with field, lineNumber, original and redacted, so the scrubber already knows what it did; the fix is in its patterns and in the confirmation flow of src/cli/commands/issue*.ts (or wherever the issue scrubber lives).