Nicky LeachandPaperclip 0c7d90397a fix(recovery): do not auto-assign board-owned blockers to the creator agent ...

Board-owned blocker issues (those with `responsibleUserId` set) were
being silently reassigned to the creating agent by the orphan-blocker
recovery path, causing board-assigned work items to land on the
creating agent instead of remaining with the board.

Guard: if `responsibleUserId` is non-null, skip agent reassignment and
post a "Blocked on Board Review / Board action required" comment
instead so the parent surfaces as awaiting a human action.

Plain orphaned blockers (no `responsibleUserId`) continue to recover
as before.

Tests:
- Renamed existing test (which already had responsibleUserId) to
  document the board-owned skip behaviour and assert no reassignment.
- Added new test for the plain-orphan path to cover the existing
  recovery behaviour.

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-07-13 20:36:11 +00:00

..

scripts

fix(server): use stable tsx/cli entry point in dev-watch

2026-03-28 06:42:03 +07:00

src

fix(recovery): do not auto-assign board-owned blockers to the creator agent

2026-07-13 20:36:11 +00:00

CHANGELOG.md

chore: release v0.3.1

2026-03-12 13:09:22 -05:00

package.json

Preserve built-in agent assets in server builds (#9339)

2026-07-10 07:44:08 -05:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

vitest.config.ts

refactor(deps-dev): bump vitest from 3.2.4 to 4.1.8 (#7581)

2026-06-05 21:11:32 -07:00