9 Commits

Include renames

Author	SHA1	Message	Date
Sergey Matyunin	336d8f30ba	test: allow inert summary style in lost-space smoke (#437) ... Issue: #437 User-Visible: no	2026-09-08 19:30:18 +03:00
Matysh	ce07db748e	Witness synchronous warm confirmation refusal ... Issue: #470 User-Visible: no	2026-09-05 22:59:28 +03:00
Matysh	5ff97858f8	Repair escaped mutation witnesses ... Issue: #466 Issue: #467 Issue: #468 Issue: #469 User-Visible: no	2026-09-05 22:13:25 +03:00
Sergey Matyunin	53847e3997	fix: harden beta 2 audit paths ... Issue: #440 User-Visible: yes	2026-09-03 16:50:54 +03:00
Codex	d4dd027b0a	build: prepare v1.71.0-beta.2 candidate ... Issue: #426 Issue: #427 Issue: #428 Issue: #431 Issue: #432 Issue: #434 User-Visible: no	2026-09-03 15:23:40 +03:00
Sergey Matyunin	59ea93b4ba	Make lost-space smoke prove synchronous refusal ... Issue: #417 User-Visible: no	2026-09-02 16:26:50 +03:00
Sergey Matyunin	e46220f3eb	Fix confirmation guards for unrenderable branches ... Issue: #417 User-Visible: yes	2026-09-02 16:25:24 +03:00
Sergey Matyuninandclaude[bot]	372d838ec2	fix: close beta 2 polish gaps ... Issue: #406 User-Visible: yes	2026-09-01 16:32:25 +00:00
Codex	00b6f41233	fix: the danger confirmation lives outside render()'s branches (#402) ... hp-confirm sat at the end of a chain of early returns, so in onboarding («no spaces yet»), in the fixed-floor states and without a space it did not exist at all: the trash button next to a saved plan was dead and the promise hung forever, because the decision event had no source in the DOM. An already open dialog vanished the moment the card slipped into one of those branches, leaving the caller waiting for a resolution that could never come. Before #32 a browser confirm() worked there. render() is now a wrapper: it takes the body — the old chain, unchanged, as _renderBody — and renders the confirmation beside it. That fixes the class rather than the instance: a branch added later cannot lose the dialog again. noChange and nothing are passed through untouched, since neither may be wrapped in a template; in those states _confirmDanger refuses the request outright instead of leaving it pending, which is the honest answer while the card is not on screen and the user has pressed nothing. _tapConfirm and _vacCalConfirm deliberately stay where they are. They share the same final branch, but they have no promise (a synchronous exec, a dialog closed by hp-close), so the defect cannot occur there, and their entry points require a drawn plan. Proven by a separate smoke rather than an addition to smoke_danger_confirmation: that file keeps deliberately incomplete dialog fixtures open, and the extra re-renders this change needs make them throw. The new smoke runs under touch emulation, because TOUCH-SUPPORT § Safety floor forbids bypassing a destructive confirmation and the broken branch pierced that floor on finger as surely as on mouse. Reverting the wrapper reddens it. User-Visible: yes Issue: #402	2026-08-31 16:47:05 +03:00