fix: resolve memory_store unbound error and RAI condition logic in user_clarification endpoint

[Copilot]

Two bugs in the user_clarification endpoint introduced during telemetry improvements.

memory_store UnboundLocalError

When plan_id was provided but the session_id lookup threw (caught by except: pass), memory_store was never assigned — causing an UnboundLocalError on the subsequent get_current_team() call. Fixed by initializing memory_store unconditionally before the plan lookup block.

RAI check condition always evaluates to True

# Before — always True: when answer is None, (None != "") is True; when answer == "", ("" is not None) is True
if human_feedback.answer is not None or human_feedback.answer != "":

# After — only runs RAI check for non-empty answers
if human_feedback.answer is not None and str(human_feedback.answer).strip() != "":

This caused the content safety check to run even when no answer was provided.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.