Sync Checks and Troubleshooting

Part of Sync.

Checks

cedr sync check reads only the repo and fails on any finding. Use --format github in CI for pull request annotations.

Check	Finds	Level
CS001	A generated file is out of date: .cedr/ changed and cedr sync was not run	Error
CS002	A generated file was edited by hand	Error
CS003	A generated file is missing	Error
CS004	A file in .cedr/ is not valid	Error
CS101	An MCP server your organization bans	Error
CS102	Unrestricted shell allowed while your organization forbids it	Error
CS103	An MCP server not pinned to a version while your organization requires it	Error
CS104	A required organization skill is missing or changed	Error
CS105	An agent your organization requires is not in targets	Warning

Fix the Source, Then Regenerate

• CS001 or CS003: inspect the intended .cedr/ changes, run cedr sync --dry-run, then regenerate and run cedr sync check again.
• CS002: inspect the hand edit first. Move the intended change into .cedr/, then regenerate; do not discard someone’s work without reviewing it.
• CS004: fix the named source file and rerun the check before generating anything.
• CS101-CS105: compare the repository with its cached organization rules. Ask an owner or admin about policy changes; a repository setting cannot override an organization denial.

cedr sync check uses the organization’s last pulled rules. A passing offline check does not prove you have the newest organization version. Follow Organization Rules and Reports to pull and apply it.

For agents, Local MCP exposes sync_plan to preview changes without writing and sync_check to read findings. Supply the repository path explicitly when the server starts elsewhere.