Remove sanitation on room load

[tlokeshrao]

Description

Loosen RoomMessageStore validation so a room with an invalid parentMessageId in its message tree no longer blocks load, ask, or persist. Broken parent references now log a warn and continue instead of throwing.

Changes Made

• Wrap validateForPersistence calls at four sites with try/catch + classLogger.warn:
  • loadFromPersistedJson — open corrupt rooms from the durable store
  • normalizeForProviderPayload — allow ask to proceed against a corrupt tree
  • validateSerializedProjection (called by persist) — don't block DB write on a broken tree
  • validateProviderPayload — the walker-produced branch can still contain an orphan-parent message
• Tool-call/tool-result matching inside validateProviderPayload remains strict — genuine payload defects still fail loudly.

How to Test

1. Open a room whose persisted messages contain a message with a parentMessageId not present in the tree (e.g. STREAMING_PLACEHOLDER_ID).
2. Ask a new message. Room loads, ask completes, response persists.
3. Warn logs (Failed to validate messages for …) appear at load and again during ask/persist for that room.

Notes

• No self-heal: the orphan-parent message stays in room.messages and will produce a warn every subsequent load/ask/persist. Pruning orphan-parent messages inside normalizeForProviderPayload would provide real self-heal; follow-up if log noise becomes a problem.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.