fix(inbox): correct inverted exit code in collision check

process.exit(existsSync(p) ? 0 : 1) caused the Bash tool to report
"Error: Exit code 1" on every normal capture (no collision). Swap to
? 1 : 0 so the happy path exits 0 and collision exits 1.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: orioltf

.claude/commands/inbox.md

@@ -33,7 +33,7 @@ Examples:
 node -e "
   const root = require('child_process').execSync('git rev-parse --show-toplevel').toString().trim();
   const p = require('path').join(root, 'docs', 'inbox', '<slug>.md');
-  process.exit(require('fs').existsSync(p) ? 0 : 1);
+  process.exit(require('fs').existsSync(p) ? 1 : 0);
 "
 ```
 

docs/inbox/using-pr-review-on-active-ado-prs-wrongly.md

@@ -0,0 +1,6 @@
+---
+title: using pr-review on active ADO PRs wrongly identified as merged
+created: 2026-05-04
+---
+
+using pr-review on active ADO PRs wrongly identified as merged

docs/issues/inbox-collision-check/01-fix-exit-code.md

@@ -0,0 +1,37 @@
+# Fix inverted exit code in `/inbox` collision check
+
+**Status:** resolved
+**Category:** bug
+
+> *This was generated by AI during triage.*
+
+## Agent Brief
+
+**Category:** bug
+**Summary:** The `/inbox` command's collision-check script exits with code 1 on the happy path (no collision), causing Claude Code's Bash tool to display a false "Error: Exit code 1" on every successful capture.
+
+**Current behavior:**
+The collision check in `.claude/commands/inbox.md` uses:
+```js
+process.exit(require('fs').existsExists(p) ? 0 : 1);
+```
+Exit 0 (tool-success) means "file exists" (collision). Exit 1 (tool-error) means "file does not exist" (no collision). Since the no-collision path is the common case, every normal inbox capture shows a red "Error: Exit code 1" in the Bash tool output, even though the file is created successfully.
+
+**Desired behavior:**
+The no-collision path should exit 0 (tool-success) and the collision path should exit 1 (tool-error). This way the Bash tool shows no error on a normal capture, and Claude correctly detects a collision (non-zero exit) and appends `-2`, `-3`, etc.
+
+**Key interfaces:**
+- The collision-check `node -e` snippet in `.claude/commands/inbox.md` Step 2 — swap the exit code values
+
+**Acceptance criteria:**
+- [ ] Running `/inbox <new-idea>` produces no "Error: Exit code 1" in tool output
+- [ ] Running `/inbox <existing-slug>` still detects the collision and appends `-2` to the slug
+- [ ] The same fix is applied to the copy at the installed path (`.claude/plugins/marketplaces/unic-agent-plugins/.claude/commands/inbox.md`) if it is managed in this repo
+
+**Out of scope:**
+- Rewriting the collision-check with a different mechanism (fs.existsSync is fine)
+- Changes to other parts of the inbox skill
+
+## Blocked by
+
+None — can start immediately.