Isolate nested dismissal ownership across browsers and builds

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-26 22:35:12 +02:00
parent 3eecd74b0d
commit 85ae4f62af
12 changed files with 7090 additions and 0 deletions

View file

@ -97,3 +97,19 @@ browser, verify readiness/ownership without arbitrary delay. Do not mark its ass
resolved from the settled run. Feature/release inspection and navigation checks remain
pending. T02/T03 unchanged, sixteen hypotheses, no independent human validation or
M1/M2 completion. See research/reviews/BoundaryRecoveryExperiment.md; no model calls.
## Nested dismissal isolated across browsers/builds — 2026-09-26
T01 progress: unchanged pinned fixture compared across Chromium 151.0.7922.34 and
Firefox 155.0, development/production, raw/traced/readiness/experimental-guard variants,
three trials each. 43/48 obligations met; all outcomes retained in isolation-results.json.
Trace captures inner layer registration/focus before Escape listener ownership transfers:
stale outer handler can close both tasks. Production traced failures reproduce the
mechanism; unmodified production trials passed. Firefox passed 24/24, not immunity.
Private listener-readiness condition passes 12/12; guard loses input in one production
trial and is not a fix. Original fixture/receipts unchanged. See
research/reviews/NestedDismissalIsolation.md. Residual under T01: assess lifecycle-safe
ownership/routing during activation and teardown before recommending a product repair.
No upstream message, deployment, new inference, canonical promotion or M2 completion.
Feature/release coupling and navigation evidence remain pending; T02/T03 unchanged.