Implement critical editor override state
This commit is contained in:
@@ -551,6 +551,17 @@ Acceptance criteria:
|
||||
|
||||
### Phase 3: Generated versus overridden state model
|
||||
|
||||
Status:
|
||||
|
||||
- implemented in the web app on March 15, 2026
|
||||
|
||||
Implemented model:
|
||||
|
||||
- result-level override flags separate generated description and collection state from manual edits
|
||||
- effect rows and condition rows carry explicit origin keys plus override markers
|
||||
- re-parse now merges generated parser output with the current override state instead of replacing the whole editor payload
|
||||
- saved editor state is persisted so later edit sessions keep the same generated-versus-overridden boundaries
|
||||
|
||||
Scope:
|
||||
|
||||
- explicitly track which values are parser-generated and which values were manually overridden
|
||||
|
||||
Reference in New Issue
Block a user