fix(ui): recover scripted chat responses in fresh consumers

[HomenShum]

Freshly generated chat apps could crash on their first prompt after resolving an incompatible dependency cohort. Keep the existing ranges and include the tested template lock. Add native Stop, failed/incomplete tool state and explicit Retry to the source and generated chats. A synchronous claim on the actual response ID prevents rapid duplicate retries while allowing a later failed response to be retried. The generated layout contains enlarged controls, and keyboard-focused Retry stays above the source's sticky composer.

Validation: a normal packed/installed CLI and generated consumer bind 242 exact files. The unchanged first-run proof passes 59 checks/25 captures; recovery passes 289/76 across six source/generated widths. Independent review adds 130 checks/34 captures, including Stop after a completed tool result, two failed-response identities and duplicate pointer/keyboard activation. Tests (41), typecheck/build and tour citations pass. The portable packet includes exact before/after evidence, replay instructions, preserved failures and raw-byte Git attributes.

This covers scripted local chats. Stop cannot undo completed computation or external actions, and browser reload resets conversations. The separate Pi draft is preserved. Source-header overflow with doubled text, graph readability, development advisories, full grades, provider integration and production readiness remain open.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}