[RFE] Better indicator of why Code stopped, with clear visual indicator of when it wants a specific type of input.

When asking Claude Code to get something done, it would often stop before it's finished, and it does not explicitly say why it stopped and what it wants. Politely telling it not to stop without a good reason does not work at all. Using "WTF" is only about 10% effective (w.r.t how much I want it to be effective)

Then proceed executing your todos list, subject to the following rules:
    - When something not entirely expected happens (such as things failing or not working) - investigate thoroughly before taking a corrective actions - do not make changes, particularly significant invasive ones, without looking at the problem from every angle and considering whether you might still be missing something. 
    - When not sure about my preferences, stop and ask, do not assume.
    - When you are sufficiently confused that you are not certain your idea for moving forward is the right one, describe the issue, what you know for sure, what you suspect but not sure about, and what you are confused about to me, then ask for guidance and stop.
    - When you do not have questions for me, and you are less than 110% done, do not stop!!! If I see you stopped, and the last line of your output is not a question for me and not a statement of complete success, with every single thing fixed and every single test passing, my next response to you will start with “WTF??? Why did you stop???” and you better have a good answer. That said, if I see that you did something questionable without stopping, *thoroughly* thinking it through and/or asking me for guidance, my next response to you will start with “WTF??? Why did you [...]??? Undo it!!!” These are using very strong language based on frustration with your earlier failure to follow similar directions - proceed with utmost care!

Note that when it does stop part way because it could use guidance, it's often not asking for that guidance in any explicit way. It would actually be very helpful it it was instructed that just before stopping it has to always provide a 1-line summary of what it needs from the user, or the fact that it believes that it's done - perhaps including a standard visual representation at the beginning of this line (e.g. green checkmark for "I am done", red question mark for "I need your input"), maybe something else when it just wants a "go ahead" (maybe some sort of a stoplight symbol?), etc).