issue create, issue comment and pr comment write a new record every time they run, so an agent that retries after exit 6 — the one status that says the write may have landed — can file a public duplicate on someone else's repo. pr create already avoids this by asking the repo's knot for its earlier attempt; the issue verbs did not. Closes #1377.
This gives those three verbs the same contract: unless --new, they read the repo's knot for a record this account wrote in the last ten minutes with the same title and body (or the same subject, body and reply), report it as found, and write nothing. A knot that cannot answer the pre-read is a refusal, not a guess. --json gains found, and dry runs report it too.
🤖 Generated with Claude Code