[HIGH] Inconsistent fallback logic violates DRY — `fallback_user` and `user` are redu

[ironclaw-ci]

[HIGH:75] Issue Found by Staging CI Review

Severity: HIGH
Confidence: 75/100
PR comment: #1279 (comment)

Description

Inconsistent fallback logic violates DRY — fallback_user and user are redundantly computed with overlapping resolution logic (lines 564-620). fallback_user is resolve_owner_scope_notification_user() but user is resolve_routine_notification_target() which calls the same function internally as a fallback. Redundant computation creates maintenance burden.

---

Auto-created by staging-ci Claude Code review

[henrypark133]

Triage verdict: STALE — already fixed

Fixed in commit bcc38ce. The DRY violation was resolved by extracting resolve_owner_scope_notification_user() as a reusable helper. resolve_channel_notification_user() now calls it for fallback instead of duplicating logic. The code properly composes the resolution functions without redundant computation.