Separate UX diagnostics from curation
This commit is contained in:
@@ -667,6 +667,16 @@ Acceptance criteria:
|
||||
|
||||
### Phase 5: Final tooling boundary cleanup
|
||||
|
||||
Status:
|
||||
|
||||
- implemented in the web app on March 15, 2026
|
||||
|
||||
Implemented model:
|
||||
|
||||
- the primary critical-cell editor now keeps only compact correction tools plus advanced review for generated-versus-current comparison
|
||||
- engineering-only parser metadata, source text, and payload inspection moved to a dedicated Diagnostics page in the main navigation
|
||||
- normal curation no longer mixes raw JSON and storage-facing diagnostics into the default correction flow
|
||||
|
||||
Scope:
|
||||
|
||||
- verify that normal curation mode contains only user-facing correction tools
|
||||
|
||||
Reference in New Issue
Block a user