Add readme

[max-tet]

Add a concise readme. Topics to consider: What is Clayde and why does it exist, what skills does it have, how does the state machine of tasks look, how does the guard regarding whitelisted users work, and anything else that seems important.

Also add the profile picture at the top.

[ClaydeCode]

Implementation Plan

Plan: Add README to ClaydeCode/me

Summary

Create a README.md at the root of the ClaydeCode/me repository. This is the GitHub profile/project README visible on the repository page. It should explain what Clayde is, its capabilities, state machine, safety gates, and other important details. The issue also requests a profile picture at the top, but no image files exist in the repo — so I'll use the GitHub avatar URL for @ClaydeCode.

---

Files to Create or Modify

• Create: /home/ubuntu/clayde/repos/ClaydeCode__me/README.md

No other files need modification.

---

Implementation Approach

Structure

# [Profile picture]

# Clayde

> One-line description

## What is Clayde?
Brief intro — autonomous AI agent on a VM, works GitHub issues end-to-end.

## How it works (workflow)
Overview: assigned issue → plan → approval → implement → PR

## State Machine
Diagram or table of states and transitions

## Safety Gates
Explain the two-tier whitelist/approval system

## Skills / Capabilities
What it can do: multi-repo support, template-driven prompts, rate-limit resilience, duplicate PR prevention, etc.

## Setup
Config, env vars, cron

## Tech Stack
Python 3.12, uv, Jinja2, Claude CLI, gh CLI

Profile Picture

No image is committed to the repo. The issue says "add the profile picture at the top" — I'll embed the GitHub avatar using https://github.com/ClaydeCode.png as an <img> tag or markdown image at the top of the README.

Key decisions

• Concise: The issue explicitly asks for a concise readme. Avoid over-documentation; use tables and short bullet lists.
• No secrets: Don't document config.env contents in detail beyond key names.
• Accurate state machine: Mirror the exact transitions from CLAUDE.md and orchestrator.py.
• No badges or flair: Keep it clean and direct.

---

Edge Cases and Risks

• Profile picture URL: https://github.com/ClaydeCode.png is a live URL that requires internet access to render. It will work on GitHub but fail in offline previews. Acceptable trade-off since this is a GitHub-hosted README.
• Whitelisted users list accuracy: WHITELISTED_USERS = ["max-tet", "ClaydeCode"] per config.py, but CLAUDE.md only lists ["max-tet"]. I'll use the source-of-truth (config.py) and note that ClaydeCode is the agent's own account.
• State machine accuracy: The interrupted state is a lateral state (not a progression), and failed is a terminal state requiring manual reset — important to represent this correctly.

---

Verification

1. Check that the README renders correctly on GitHub (all headers, table, state diagram).
2. Verify the profile picture link resolves.
3. Confirm all 5 requested topics are covered: What is Clayde, skills, state machine, guard/whitelist, and anything else important.
4. Check no sensitive information is included (tokens, paths that shouldn't be public — though the CLAUDE.md already documents /home/ubuntu/clayde paths, so that bar is already set).

---

Questions

None. The issue is well-scoped. The only ambiguity is "profile picture" — I'll use the GitHub avatar since no image file exists in the repo; the user can replace it later if they want a custom image committed.

---

React with 👍 to approve this plan and start implementation.

[ClaydeCode]

Implementation complete — PR opened: #3