transcript-to-editslisted

# Transcript → Edits Turn a messy call into a clean, confirmed, applied set of changes — without guessing. ## Procedure 1. **Extract the edit list.** Read the transcript and pull every concrete, actionable change (copy, pricing, features, contact info, photos, new sections). Ignore small talk and maybes — but list ambiguous items separately as "needs confirmation." 2. **Show the list BEFORE editing.** Two sections: - **Will apply** — unambiguous changes, each with the site section it touches. - **Need your call** — judgment items as numbered questions the user can answer tersely ("1. yes 2. skip 3. use the second option"). 3. **Apply confirmed edits** to the repo. One commit per logical group, clear messages referencing the call date. 4. **Verify visually** — serve locally and check each changed section renders correctly. 5. **Deploy per the `ship-site` skill** — git push always; host deploy only on an explicit go. 6. **Log the call** — file the transcript + applied edit list into the client's note, so the next call has history.