coulomb/frontend-patterns
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Probe rendering and modal focus boundaries in pinned browser fixture

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-26 22:01:35 +02:00
parent 50c68575f1
commit 3eecd74b0d
18 changed files with 2067 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
workplans/FEP-WP-0003-contrasting-schools.md
View file

@ -81,3 +81,19 @@ pin an application and inspect feature imports versus release coupling; exercise
render versus request failures and modal focus after invoker removal. Previous
navigation/history/cache checks remain open. WP-0002 retains independent-human
validation. No frozen-pilot edits, canonical promotion or evidence-gate completion.
## Executed rendering/focus boundary slice — 2026-09-26
T01 progress: research/experiments/boundary-recovery pins React 19.3.0, Radix Dialog
1.1.23 and all dependencies; Chromium fixture exercises eight cases. Final immediate
run meets 7/8 assertions; separate 100 ms nested-settling condition meets 8/8. Three
earlier development results retained, including failures. Ordinary render containment,
event-handler exclusion, explicit 503 state, fallback escalation, existing/removed
trigger focus and explicit replacement target observed. Immediate nested Escape can
close the outer task; root cause unresolved. No delay prescribed as a fix.
Next T01 action: isolate nested dismissal timing, compare production and another
browser, verify readiness/ownership without arbitrary delay. Do not mark its assertion
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.