Exercise feature activation rollback and old-session artifact retention
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
This commit is contained in:
parent
b8eec87f08
commit
e34ec3fafe
22 changed files with 1661 additions and 1 deletions
|
|
@ -90,3 +90,17 @@ Vertical Feature Slice need not imply Independent Feature Boundary.
|
|||
version-skew/load-failure/binding-rollback harness and independent walkthrough review.
|
||||
No cloud deployment, production artifact activation or operational team independence
|
||||
was verified. VC-04/05 remain planned; this draft does not complete VC-06's M2 gate.
|
||||
|
||||
## Executed model follow-up — 2026-09-26
|
||||
|
||||
[Seven-scenario native-module experiment](../reviews/FeatureReleaseExperiment.md)
|
||||
now supports steps 2–6's publication/activation, version mismatch, failed loading and
|
||||
session-scoped rollback distinctions in a synthetic host. Both browsers meet all seven
|
||||
expected observations, including deliberate failures. Old lazy sessions need retained
|
||||
artifacts even when loaded old sessions still work. Post-import compatibility gates
|
||||
cannot prevent evaluation side effects. Shared startup outage is a separate fault scope.
|
||||
|
||||
This supersedes the lack of any load/rollback execution in the initial self-review,
|
||||
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.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue