Libra CodeHub

CedarCopilot/cedar-mail

Branch: staging

docs(config-tools): mention dealWriteGuard where the config agent looks first

merged#2923CedarCopilot

CedarCopilot wants to merge 1 commit into staging from worktree-deal-write-guard-tool-descriptions

What Libra verified

  • Config requests to block CRM deal writes surface dealWriteGuard

    Libra ran this behavior against the change and confirmed the check detects when it breaks.

    Technical evidence
    • the account-config routing catalog identifies external-writes when Cedar must block writes to matching CRM deals
    • the apply-config-change tool description points deal-write requests to update_crm_settings and dealWriteGuard
    • the connection-write tool description points deal-write requests to update_crm_settings and dealWriteGuard

    Changed code: SKILL.md.

  • Connection configuration guidance remains within the tool description budget

    Libra ran this behavior against the change and confirmed the check detects when it breaks.

    Technical evidence
    • the connection-write description remains within the enforced 2048-byte limit
    • the connection-write description keeps sync/push switches, dealSyncFilter, and dealWriteGuard available to the agent

    Changed code: connection-write-tool.ts.

  • The config tool explains how to set and clear dealWriteGuard

    Libra ran this behavior against the change and confirmed the check detects when it breaks.

    Technical evidence
    • the apply-config-change description states that dealWriteGuard blocks writes to HubSpot deals matching every field/value pair
    • the apply-config-change description states that clearing uses dealWriteGuard {} with clearDealWriteGuard true

    Changed code: applyConfigChangeTool.ts.

run a14fa260-bff6-4ee0-b1fc-87b0535e4e25, completed Sep 23, 2026, 2:12 PM