[joaquim-verges]

Stacked on #172 (base fix/publish-own-issue-not-duplicate). Merge #172 first. This closes the two publish gaps #172 leaves open.

Stored false skips

A stored skip on a verified fix that cites the item's own issue came from the false duplicate that #172 stops. These items stayed hidden until someone cleared the field.

• The publisher now offers them to the judge again. It does not force a PR, so the judge can still skip for another reason.
• The PR clears the stored skip when it opens.
• The skip stands when the item's own issue is closed, or when an open PR will close it, so a fix shipped outside Bugpatrol does not get a second PR. A failed lookup keeps the skip for the next run.
• Every other stored skip still holds, and bugpatrol issue reopen <id> remains the manual clear.

Runs that end without publishing

A run that ended without publishing or skipping an item looked like a quiet pass.

• Those items now return as unpublished with the reason: the publisher finished, stopped early (budget, steps, timeout), crashed, or lost a publish to a tool error.
• The session is marked failed, bugpatrol publish exits 1, and a patrol records a problem for the cycle.
• A cancelled session is a deliberate stop and is not reported.

Verification

• New cases in publish.test.ts cover both gaps. Against the fix(publish): stop skipping a verified fix as a duplicate of its own issue #172 publisher, the revive and unpublished cases fail on their own assertions. With the closed-issue, open-PR and failed-lookup guards removed, those three cases fail.
• The real CLI with a no-op judge command printed the unpublished line and exited 1.
• pnpm typecheck, pnpm lint, pnpm knip, biome check and the full vitest suite pass locally.

🤖 Generated with Claude Code

---

Assisted by Nebula.

---

^{Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.}

Closes #171

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
bugpatrol	Skipped		Nov 11, 2026 12:36am UTC

[github-actions]

Bugpatrol review: fixture-app

No problem introduced · tested 683c9e0 against main 6d26970

Tested

• Home (index.html) loads and renders
• Settings (via nav link) loads and renders

Not tested

• The rest of the change (publish role, patrol, CLI, docs): outside the fixture app

_{Updated on each push. Tests only what the diff can affect. Does not block the merge.}

[github-actions]

Bugpatrol review: dashboard

No problem introduced · tested 683c9e0 against main 6d26970

Tested

• Overview page
• Issue detail (Save button overlaps account text)

Not tested

• The rest of the change (publisher skip recheck, unpublished reporting, CLI publish output): outside the dashboard
• Reviews, Activity, Flow, Screens, Memory pages: unchanged by this PR; no dashboard file is in the diff

_{Updated on each push. Tests only what the diff can affect. Does not block the merge.}

[github-actions]

Bugpatrol review: cli

No problem introduced · tested 683c9e0 against main 6d26970

Tested

• Publisher skip-recheck and unpublished logic via publish.test.ts (all 21 pass)
• CLI publish output block (kind mapping, unpublished exit 1) via code review + cli tests
• issue reopen/dismiss manual skip-clear paths on fixture CLI
• packages/cli and packages/agents typecheck
• agents + cli vitest suites
• patrol unpublished-to-problem loop via code review

Not tested

• Live publish run against GitHub (PR open, skip clear end-to-end): guide forbids running publish/patrol; covered by unit tests with fake gh
• review.test.ts claim-check recording failure: untouched by PR, test-only, appears pre-existing/environmental

_{Updated on each push. Tests only what the diff can affect. Does not block the merge.}

[merge-loop]

Merged as 06faf8d.