Clean up the readme

[max-tet]

Your readme contains outdated and confuing information. Go through it and bring it up-to-date and make sure it is clear and easy to read.

Things that I found:

• The issue state machine is outdated.
• The "setup" and "Deploying Your Own Instance" sections overlap and should be merged.

Feel free to make other improvements you find useful.

[ClaydeCode]

Preliminary Plan

Approach

The README needs two main fixes plus general cleanup:

1. Update the state machine — The current README shows a simplified 4-state flow (planning → awaiting_approval → implementing → done), but the actual implementation has a two-phase planning flow: preliminary_planning → awaiting_preliminary_approval → planning → awaiting_plan_approval → implementing → pr_open → done, plus addressing_review. I'll render this as a Mermaid diagram (GitHub supports mermaid code blocks in markdown) alongside an updated state table.

2. Merge Setup + Deploying sections — Both sections repeat the same mkdir/cp step and backend configuration. I'll merge them into a single "Setup" section that naturally covers deploying your own instance.

3. Other cleanup — Fix CLAYDE_LOOP_INTERVAL_S (should be CLAYDE_INTERVAL), update the "What is Clayde?" description to mention the two-phase planning, update Safety Gates to mention content filtering, and add CLAYDE_INTERVAL to the config table.

No clarifying questions — the issue is clear and self-contained.

---

This looks like a small issue. React with 👍 to approve this preliminary plan and proceed directly to implementation.

[max-tet]

Can you render the state machine more pretty? Like in a mermaid diagram if that is supported by GH Readme rendering.

[ClaydeCode]

Plan updated. Added Mermaid diagram rendering for the state machine. GitHub does support Mermaid in markdown, so I'll use a mermaid code block for the state flow diagram instead of a plain text representation.

[ClaydeCode]

Implementation complete — PR opened: #57

[ClaydeCode]

Review addressed. Updated the state machine diagram to add two missing edge types: (1) self-loop edges on both awaiting_preliminary_approval and awaiting_plan_approval showing that new comments trigger a plan update in place, and (2) a direct edge from awaiting_preliminary_approval to implementing for small issues (bypassing the thorough planning phase). Also updated the state table descriptions and the 'What is Clayde?' step list to document both the small-issue shortcut and the plan-update behavior in the text.