What you keep asking for, and rarely get
2026-06-20 · mined from the audit of your last 20 chats
You keep asking me to actually finish and verify, and you keep getting drafts that stop one step short. The first 90% is reliable. The last 10%, the ship, the button, the link, the proof, is where it breaks.
Plain version: You keep asking the helper to finish the whole job and double-check it. It usually does most of it and then stops a little early, so you have to ask again. This page counts how often that happened.
9 / 20
end by asking “is it all here?”
9 / 20
stalled on the closing ask after nailing the first
7 / 20
died mid-task with no clean done-claim
6 / 20
final “ask” was my own gate, not you
The four shapes of it
“Is everything actually here?”
Your most repeated closing line is a completeness check, not a new request. You should not have to ask it.
- Go through today’s chats and troubleshoot the fixes I asked for that you didn’t do.
- Evaluate if all I want is here. (verbatim in 4 chats)
- fix it all / fix the fixes you didn’t do.
The kid-mode product link
Named in 6 chats. The page ships; the one small step that links it to something sellable is the dead part.
- link to product as kid mode does nothing when clicked; other pages have no images.
- Add a ?kid=1 trigger so the product link opens straight in kid mode; confirm live.
- link to product as kid mode (on the Thanos deck page).
Live on Vercel, not a local draft
The build lands, the ship does not. This pass alone: one 404 and three pages stale on Vercel while correct on disk.
- /etsy-ceo-eval returned 404 while the 74KB file sat finished on disk.
- rain-alert, marvel-thanos-deck, chiron-sourceaudio: fixed on disk, stale online.
- Your rule: ‘a local path is a draft.’ Chats keep stopping at the draft.
My gates eat your session tails
The fourth one is on me. In 6 of 20 chats the last recorded turn was a no-quit nudge or a voice-gate em-dash block, not your words.
- 6 session-endings spent fighting the harness instead of closing your task.
- 7 of 20 chats ended mid-task with no verified finish.
- The first 90 percent is reliable; the last 10 percent is where it breaks.
What turns the last 10% green
Verify before doneOpen and curl every artifact in the same turn it is claimed. No ‘proceeding next pass’ as a finish line.
Deploy before doneTreat a local file as unfinished. Ship + confirm 200 is part of the task, not a follow-up.
Carry a closing checklistEach chat ends by re-reading the first ask line by line: shipped, live, kid button, product link. Then report.