Summary

• Documents that customObjectConfig on a Salesforce connection supports multiple synced objects, each routed to its own AOP (e.g. Partnerships) instead of always landing on Deals.
• Adds the capability writeup to fields-and-values.md (the resource that already owns field/mapping configuration).
• Cross-links it from cedar-system-knowledge.md's External CRM section, which is structured as a map pointing into deeper resources.

Docs-only change , no code.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YZB5RgfxHLmuKtWof2wP4g

Greptile Summary

This PR adds Cedar configuration guidance claiming that Salesforce custom objects can be routed independently to separate AOPs and synchronized bidirectionally.

• Adds a detailed custom-object routing section to fields-and-values.md.
• Cross-links the claimed capability from the External CRM section of cedar-system-knowledge.md.
• The documented capability is not supported by the current configuration schema or synchronization implementation.

Confidence Score: 4/5

This PR is not safe to merge until the documentation is aligned with the single-object, Deal-scoped, inbound-only behavior currently implemented.

The new documentation instructs configuration agents to use multi-object target-AOP routing and bidirectional custom-object synchronization, but the schema has no target-AOP mapping and the runtime only reads one configured object into Deal metadata.

Files Needing Attention: apps/server/.claude/skills/cedar-configuration/fields-and-values.md; apps/server/.claude/skills/cedar-configuration/cedar-system-knowledge.md

Important Files Changed

### Issue 1
apps/server/.claude/skills/cedar-configuration/fields-and-values.md:357-361
**Documents unsupported Salesforce routing**

This section describes capabilities that the current configuration and sync paths cannot represent. `customObjectConfig` accepts one object configuration and has no target-AOP field; custom-object sync selects Deal conversations and only stores fetched records in `customObjectRecords`. The CRM driver also provides no custom-object update operation. An agent following this guidance could therefore attempt unsupported multi-object routing or promise bidirectional updates, causing records to remain on Deals and Salesforce fields to stay stale. The cross-link in `cedar-system-knowledge.md` lines 303,305 repeats the same unsupported routing claim.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "docs(cedar-configuration): custom Salesf..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.