#2882 `swamp issue bug` redactor treats the file name `settings.local.json` as a hostname and rewrites it to `[HOST-1].json`

What

swamp issue bug runs an automatic redactor over the title and body before submitting to swamp-club Lab. On 2026-10-01 it classified the file name settings.local.json as a hostname and replaced every occurrence with [HOST-1].json, so the submitted repro read .claude/[HOST-1].json in four lines. The report (Lab #2881) was about that very file, so the redaction made the repro unreadable until it was re-submitted with swamp issue edit --no-redact.

Repro (swamp 20260930.234450.0-sha.657fe527)

swamp issue bug --json --title 'x' --body 'The hook lives in `.claude/settings.local.json`.'

Result JSON: "redaction":{"message":"Redacted 1 hostnames from issue content." ...} with settings.local.json → [HOST-1].json.

Expected

A dotted token inside backticks, or one whose last label is a well-known file extension (.json, .yaml, .ts, .md, .toml, …), is a file name, not a host. At minimum the CLI should print the redaction diff before submitting (not only in --json) and ask, since --no-redact exists but you only learn you needed it after the issue is public.

Impact

Any bug report about a swamp config or settings file has its file names mangled. Workaround: inspect the redaction.changes array in the --json output and re-submit with swamp issue edit <n> --no-redact when the content is already sanitised.