d924d9059c
Felix #2 / Markus #1 (PR #366 review). In the synchronous-transactional path the existsById check could never return false — the rename and the propagation share one transaction, so the renamed Person is guaranteed to still exist when the listener runs. The check was forward-protection for an eventual @Async refactor but its presence today is misleading: it suggests a runtime branch that no test could reach against the real flow. Delete the call, drop the PersonService dependency from the listener, drop the now-unused PersonService.existsById, and remove the orphan-guard test (it asserted a behaviour that the synchronous path cannot produce). When async is added later the guard re-enters the codebase deliberately as part of that refactor. Refs #362 #366 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>