CedarCopilot wants to merge 0 commits into staging from chore/refresh-cedar-configuration-knowledge
Live on prod, no production signal yet
internal_only
internal_only
Libra has no production signal for this change on prod yet. Libra checks hourly for 3 days after each deploy.
refresh-agent-knowledge skill against current staging and repaired drift accumulated over PRs #2716-#2722 (the local checkout had been 19 commits stale).config-propagate's new force-write/multi-target semantics (force:true refuses the whole call if more than one target diverges; "org" targets exclude the source connection's own owner; connection-write's update_crm_field_mappings now also reconciles select/list options via the shared writeCrmFieldMapping()) were either undocumented or directly contradicted across fields-and-values.md, scope-and-sharing.md, and limits-and-escalation.md.when_to_use and model subagent frontmatter fields are retired (folded into description), but SKILL.md, building-an-agent.md, choosing-a-trigger.md, diagnose-and-repair.md, and playbook-anatomy.md all still described the old shape. Notably, knowledge-claims-resolve.test.ts stayed green through this drift since both fields remain real, resolvable identifiers , only their meaning changed.pnpm --filter @zero/server exec vitest run src/mastra/skills/account-config , all tests pass before and after these editsaccount-config/index.ts , no routing-relevant identifiers changed, no doc edits needed therecedar-configuration/** files are in this diff (no unrelated working-tree changes swept in)🤖 Generated with Claude Code
https://claude.ai/code/session_013iVAVojFcUXtRjhwFt8X8P
This documentation-only PR refreshes the Cedar configuration skill to match current subagent metadata, CRM mapping reconciliation, and configuration propagation behavior.
when_to_use and model guidance with the live description contract.The documentation changes appear safe to merge and match the current implementation.
No actionable mismatch remained after checking the revised metadata, mapping reconciliation, target resolution, force-write, and propagation-scope claims against current code and tests.
| Filename | Overview |
|---|---|
| apps/server/.claude/skills/cedar-configuration/building-an-agent.md | Correctly updates subagent authoring guidance for live metadata and create-only options. |
| apps/server/.claude/skills/cedar-configuration/choosing-a-trigger.md | Correctly distinguishes informational descriptions from binding trigger-block prose. |
| apps/server/.claude/skills/cedar-configuration/fields-and-values.md | Accurately documents mapping reconciliation, propagation targets, and force-write safeguards. |
| apps/server/.claude/skills/cedar-configuration/playbook-anatomy.md | Updates the documented subagent frontmatter shape to the current runtime contract. |
| apps/server/.claude/skills/cedar-configuration/scope-and-sharing.md | Correctly limits propagation support to fields and CRM mappings rather than playbook content. |
Reviews (1): Last reviewed commit: "docs(cedar-configuration): refresh knowl..." | Re-trigger Greptile
Context used:
Libra has not measured any production surfaces for this change yet.