Test activation conflicts and draft-preserving application reload

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
tegwick 2026-09-26 23:30:15 +02:00
parent e34ec3fafe
commit f273a190f0
13 changed files with 1385 additions and 0 deletions

View file

@ -168,3 +168,20 @@ safe reload with unfinished work; navigation/history/cache evidence remains pend
Do not build a production release platform to satisfy this research model. T02/T03,
independent-human gate and M1/M2 completion remain unchanged.
See research/reviews/FeatureReleaseExperiment.md.
## Requested activation-update conflicts and safe reload — 2026-09-26
T01 progress: conflicts-reload.mjs adds three HTTP stale-writer cases and nine reload
cases in Chromium/Firefox, 21/21 expected observations. Blind overwrite and unguarded
reload reproduce loss as negative controls. Conditional replacement rejects stale maps;
disjoint intent is explicitly reapplied, same-feature rollback stays unresolved.
Draft deferral, preserve/restore, injected storage failure, schema mismatch, explicit
discard, unknown-write gating, edit-during-preflight and post-check activation covered.
New-page schema revalidation retains incompatible text read-only. See
research/reviews/ActivationConflictsAndReload.md. Original release artifacts unchanged.
Requested bounded tests complete; no distributed-store atomicity, native-unload/crash,
real backend outcome or retention authorization claim. These remain T01 limits for
any production recommendation. Next breadth task: pending VC-03 navigation/history/
full-versus-fragment cache evidence. Seventeen hypotheses; T02/T03 and M1/M2 gates
unchanged. No model inference or production actions.