CedarCopilot wants to merge 2 commits 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 change adds a customer-specific Simcare account-setup record, expands MCP OAuth resource-path matching, and configures Sol automations to disable OpenAI reasoning. The account-setup document exposes customer operational data, and the MCP change accepts an ancestor resource identifier that is then sent through authorization and token exchange. The added TypeScript assertion also violates a repository requirement.
Not safe to merge: customer operational data is committed to the repository, the OAuth flow can request a token for a broader resource than the MCP endpoint, and the repository’s no-cast requirement must be satisfied.
Two independently reproduced security-impacting failures affect the customer setup document and MCP OAuth flow. The repository requirement violation is also present.
Files Needing Attention: docs/account-setup/simcare-ai-2026-09-10.md, apps/server/src/services/integrations/mcp/server-url.ts, and apps/server/src/services/aop/automations.ts
The Simcare setup record exposes customer-specific identifiers, internal Slack identifiers, live operational configuration, and account activation state to repository readers. Separately, MCP OAuth discovery now accepts an ancestor resource path and forwards that broader resource to authorization and token exchange.
What T-Rex did
General comment
Customer operational data is committed in the Simcare account-setup document
docs/account-setup/simcare-ai-2026-09-10.md commits a named user's personal email and internal user/org identifiers; internal Slack channel and user identifiers; live-database-derived account, playbook, sales-process, and customer operational details; and records that agent execution and Gmail draft pushing are enabled. It also states that customer account-password strings were found in source email examples, even though the copied examples were reportedly redacted. The executed evidence collector established that this document is tracked in commit d4eaacbf91315c1051e593ff61774130e978575b on the configured GitHub remote, sLibra has not measured any production surfaces for this change yet.