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:
parent
e34ec3fafe
commit
f273a190f0
13 changed files with 1385 additions and 0 deletions
|
|
@ -109,3 +109,8 @@ distinguishes artifact retention, document binding and module-instance lifetime.
|
|||
Old delayed loads can fail after artifact retirement even while already-loaded old
|
||||
sessions work. Deployment independence remains conditional on a session-support
|
||||
contract; no general answer or canonical promotion follows from this fixture.
|
||||
|
||||
Q06 activation/reload follow-up: [conditional update and draft tests](../reviews/ActivationConflictsAndReload.md)
|
||||
show why disjoint-intent retry differs from competing rollback, and why preflight
|
||||
compatibility must be rechecked after reload. Same-tab draft preservation is narrower
|
||||
than durability or remote-outcome recovery. No question or maturity gate is closed.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue