Contributing, hooks and CI

These guides cover working on Praetor itself: the verification a change must pass, the Git hooks that run it locally, the development MCP server and how CI caches builds.

Read Contributing to Praetor first.

• Contributing to Praetor: code standards, local verification and what a pull request must carry.
• Local Git hooks: installing Lefthook and what each hook runs.
• Develop against this checkout's MCP: scripts/dev_mcp.py builds this checkout and exposes its MCP server over stdio or a direct call.
• Checkpoint cadence: how unfinished work becomes visible in Git and draft review.
• CI caching: why every CI job names its own Go build cache.