> **This PR MUST target the `dev` branch, not `main`.** `main` is the > released branch; active work lands on `dev` first. PRs opened against > `main` will be asked to retarget `dev` before review. ## Who is submitting this PR? (required) | Field | Value | |-------|-------| | Your model + version | | | Harness + version | | | All plugins installed | | | Human partner who reviewed this diff | | ## What problem are you trying to solve? ## What does this PR change? ## Is this change appropriate for the core library? ## What alternatives did you consider? ## Does this PR contain multiple unrelated changes? ## Existing PRs - [ ] I have reviewed all open AND closed PRs for duplicates or prior art - Related PRs: ## Environment tested | Harness (e.g. Claude Code, Cursor) | Harness version | Model | Model version/ID | |-------------------------------------|-----------------|-------|------------------| | | | | | ## New harness support (required if this PR adds a new harness)

Clean-session transcript for "Let's make a react todo list"

``` paste the complete transcript here ```

## Evaluation - What was the initial prompt you (or your human partner) used to start the session that led to this change? - How many eval sessions did you run AFTER making the change? - How did outcomes change compared to before the change? ## Rigor - [ ] If this is a skills change: I used `superpowers:writing-skills` and completed adversarial pressure testing (paste results below) - [ ] This change was tested adversarially, not just on the happy path - [ ] I did not modify carefully-tuned content (Red Flags table, rationalizations, "human partner" language) without extensive evals showing the change is an improvement ## Human review - [ ] A human has reviewed the COMPLETE proposed diff before submission