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

Test activation conflicts and draft-preserving application reload

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 23:30:15 +02:00
parent e34ec3fafe
commit f273a190f0
13 changed files with 1385 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
research/walkthroughs/VC06-MicrofrontendEstate.md
View file

@ -104,3 +104,14 @@ This supersedes the lack of any load/rollback execution in the initial self-revi
but the quality criterion remains revise: browser focus/accessibility, unsaved work,
real API/data compatibility and independent review are still unverified. VC-06 stays
provisional; no production release or M2 acceptance is inferred.
## Activation/update-reload follow-up — 2026-09-26
[21 expected observations](../reviews/ActivationConflictsAndReload.md) now cover
stale binding writers and the application-controlled reload path with unfinished work.
Conditional replacement rejects stale maps; disjoint intent is explicitly reapplied,
while conflicting rollback awaits a decision. Preserve the latest authorized draft
before reload and revalidate its schema on the next document; a preflight check can
be invalidated by a later activation. Storage failure and unknown write outcome block
the fixture's reload. This does not establish distributed-map atomicity, native-unload
protection, backend acceptance, authorized retention or complete VC-06 validation.