CedarCopilot wants to merge 0 commits into main from staging
Live on prod, no production signal yet
Strict CloudWatch fallback found 9 recent prod failure log lines for [UpdateExternalCrmWorkflow] Driver update failed (Step updateOpportunityField failed: HTTP 400: [{\), but the same failure had 4 log lines in the comparable pre-deploy baseline. Libra is not blaming this PR.
Strict CloudWatch fallback found 9 recent prod failure log lines for [UpdateExternalCrmWorkflow] Driver update failed (Step updateOpportunityField failed: HTTP 400: [{\), but the same failure had 4 log lines in the comparable pre-deploy baseline. Libra is not blaming this PR.
Strict CloudWatch fallback saw 1,587 success-shaped log lines matching pipeline, analytics, quota, aop, but no tied operation was present, so Libra is not calling this working.
Strict CloudWatch fallback found 5 recent prod failure log lines for [SCHEDULED] Failed to enrich unenriched calendar event (No valid connection tokens found for user <id>), but the same failure had 16 log lines in the comparable pre-deploy baseline. Libra is not blaming this.
Strict CloudWatch fallback saw 20,912 success-shaped log lines matching email, emails, gmail, mail, inbox, but no tied operation was present, so Libra is not calling this working.
Strict CloudWatch fallback saw 1,590 success-shaped log lines matching pipeline, analytics, quota, aop, but no tied operation was present, so Libra is not calling this working.
unknown
single_user
Libra has verdicts on 0 of 7 tracked behaviors on prod; 7 are still being checked. Libra has 2 low-confidence degraded verdicts it is still confirming. Libra attributed 2 failures to this change at medium confidence and is still confirming them. Libra checks hourly for 3 days after each deploy.
This staging merge adds CRM meeting reconciliation improvements, guarded playbook writes, on-demand subagent execution, notification updates, taxonomy/search behavior, supporting tests, operational scripts, and audit artifacts. One guarded-write rollback path can erase a concurrent valid playbook edit.
The guarded-write concurrency failure should be fixed before merging because a failed verification can erase another writer's valid playbook update.
The new rollback restores an unconditional stale snapshot after verification failure even though the main patch operates on live content, allowing overlapping playbook writes to lose committed content.
Files Needing Attention: apps/server/src/services/playbook/guarded-write.ts
| Filename | Overview |
|---|---|
| apps/server/src/services/playbook/guarded-write.ts | Adds guarded write and rollback behavior, but the rollback can overwrite a concurrent edit using a stale snapshot. |
| apps/server/src/services/crm/calendar-events.ts | Adds time-and-attendee-based calendar matching with user scoping and ambiguity checks. |
| apps/server/src/services/crm/meeting-events.ts | Adds structured extraction of external meeting speakers while excluding known hosts and coworkers. |
| apps/server/src/services/playbook/run-single-subagent.ts | Adds isolated execution of one named playbook subagent through the existing automation runtime. |
| apps/server/src/trpc/routes/admin-subagent.ts | Extends the staff-only administration route with cron execution, delivery suppression, output capture, and optional staff relay. |
| apps/server/src/services/turbopuffer/field-values-search.ts | Updates field-value filtering and search behavior with accompanying focused tests. |
apps/server/src/services/playbook/guarded-write.ts, line 228-237 (link)
Rollback overwrites concurrent edits
If two writers patch the same PLAYBOOK.md concurrently and verification fails after the second writer commits, this rollback unconditionally restores the stale pre-write snapshot, deleting the other writer's valid content and metadata.
Knowledge Base Used: Database Schema
This is a comment left during a code review.
Path: apps/server/src/services/playbook/guarded-write.ts
Line: 228-237
Comment:
**Rollback overwrites concurrent edits**
If two writers patch the same `PLAYBOOK.md` concurrently and verification fails after the second writer commits, this rollback unconditionally restores the stale pre-write snapshot, deleting the other writer's valid content and metadata.
**Knowledge Base Used:** [Database Schema](https://app.greptile.com/cedar/-/custom-context/knowledge-base/cedarcopilot/cedar-mail/-/docs/database-schema.md)
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
Libra has not measured any production surfaces for this change yet.