CedarCopilot wants to merge 1 commit into main from staging
Not deployed
Libra has no production signal for this change yet because it has not deployed. Libra checks hourly for 3 days after each deploy.
This update adds broad client, server, and infrastructure work across inbox interactions, document deletion and restore flows, chat proposal replay, boards, integrations, and supporting UI. One non-blocking issue remains: older proposal cards can present an approval action even when the persisted proposal cannot be replayed.
Safe to merge, with a non-blocking usability defect in historical chat proposal cards.
The confirmed issue affects an older proposal state by offering an action that the server will reject, but does not compromise data integrity or access control.
Files Needing Attention: apps/mail/modules/cedar-os/src/store/messages/renderers/ProposedMutationRenderer.tsx
What T-Rex did
### Issue 1
apps/mail/modules/cedar-os/src/store/messages/renderers/ProposedMutationRenderer.tsx:195
**Hide unavailable legacy approvals**
Historical proposal messages without persisted replay instructions still render an enabled approval button because a thread ID and message ID are treated as sufficient to apply them. The server rejects these rows as too old to apply, so users can confirm a change that is guaranteed to fail instead of seeing the unavailable state. Expose an applicability flag for rehydrated messages, or preflight applicability before enabling the action. This is non-blocking, but it creates misleading approval controls and avoidable failed requests.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Reviews (1): Last reviewed commit: "Merge pull request #2726 from CedarCopil..." | Re-trigger Greptile
Greptile also left 1 inline comment on this PR.
Libra has not measured any production surfaces for this change yet.