regenerate-claude-md-acceptlisted

# /regenerate-claude-md-accept — install an agreed persona > **Only the user runs this.** It happens when they type > `/regenerate-claude-md-accept`, and at no other time. If you are reading this > file because *you* decided to — to see what it does, or to carry out its steps > yourself — then stop and do neither. Following these instructions **is** > running the skill, whichever route you took to them. Say the skill exists and > let the user invoke it. The other half of `/regenerate-claude-md`. That skill *proposes* and writes nothing; this one installs what the user finally agreed to, after however many rounds it took. The split is the point: generation is cheap and reversible, installation overwrites a file read on every turn of every future session. ## What it does Three things, together, via one command: 1. Replaces `<target-env>/CLAUDE.md` with the persona given. 2. Sets that blueprint's `claude_md = "custom"` in aello's config, so `place` stops seeding a template over it on the next run. 3. Bumps `<target-env>/persona.gen` — `gen1 2026-08-03`, `gen2 …` and so on. Together those answer both questions the user asked of the system: *which envs have a real persona* (config says `custom`) and *which generation each is on* (the sidecar, sitting beside the file it describes). ## Input /regenerate-claude-md-accept <env-dir-or-blueprint-name> followed by the complete persona — normally pasted in after the command. - **The persona is the whole file.** Not a diff