solidprivacy-nl commited on
Commit
911e093
·
1 Parent(s): de01c0b

Record v13.6 two-mode content separation cleanup

Browse files
Files changed (1) hide show
  1. CHANGELOG.md +67 -43
CHANGELOG.md CHANGED
@@ -26,48 +26,52 @@ For UI/UX-only work, prefer pure helper modules and tests before touching Stream
26
 
27
  ---
28
 
29
- ## WP12 — v13.6 Two-mode UI skeleton and tab separation
30
 
31
  Status: implemented; awaiting GitHub Actions, Hugging Face sync and app verification.
32
 
33
  Purpose:
34
 
35
- - Implement the first two-mode UI structure with minimal risk.
36
- - Make the two main user intents visible:
37
- - `Anonimiseren`;
38
- - `Originele waarden terugzetten`.
39
- - Keep existing behavior working.
40
- - Avoid a full landing-page refactor.
41
 
42
  Files added or changed:
43
 
44
  - Changed `fix_streamlit_nested_expanders.py`.
45
- - Added `tests/test_two_mode_ui_patch.py`.
46
  - Changed `WORKPACKAGES.md`.
47
  - Changed `CHANGELOG.md`.
48
- - Added `handover/workpackages/20260608_0000_v13_6_two_mode_ui_skeleton.md`.
49
 
50
  Main change:
51
 
52
- - Added an idempotent startup patch that injects a small two-mode skeleton near the top of the app after the local-processing note.
53
- - The skeleton uses Streamlit tabs:
54
- - `Anonimiseren`;
55
- - `Originele waarden terugzetten`.
56
- - Each tab contains a short caption explaining the mode intent.
57
- - The existing anonymization/scrub flow is left available.
58
- - The existing pasted-text reinsert flow is left available.
59
- - This is a navigation/skeleton step only; it does not move all app content into tabs yet.
60
-
61
- Tests added:
62
-
63
- - `tests/test_two_mode_ui_patch.py` checks:
64
- - `Anonimiseren` is present;
65
- - `Originele waarden terugzetten` is present;
66
- - `st.tabs` and named tab variables are present;
 
 
 
 
 
 
 
 
67
  - existing Scrub Key export/import labels remain;
68
- - existing pasted-text reinsert labels remain;
69
- - existing anonymization/download markers remain;
70
- - existing scrubbed download behavior markers are not rewired;
71
  - no TXT upload reinsert UI was added;
72
  - no DOCX upload reinsert UI was added;
73
  - no PDF reinsert was added;
@@ -76,10 +80,17 @@ Tests added:
76
 
77
  Validation:
78
 
79
- - Local clone/test run could not be performed in the container because outbound GitHub DNS failed:
 
 
 
 
 
 
 
80
  - `Could not resolve host: github.com`.
81
- - GitHub Actions: awaiting verification.
82
- - Hugging Face sync: awaiting verification.
83
  - App verification: required because UI behavior changed.
84
 
85
  Intentionally not changed:
@@ -91,28 +102,41 @@ Intentionally not changed:
91
  - No AI calls added.
92
  - No cloud processing added.
93
  - No automatic document rehydration added.
94
- - No existing TXT, CSV, DOCX or PDF scrubbed export/download semantics intentionally changed.
95
- - No Scrub Key export/import behavior intentionally changed.
96
- - No secrets, tokens or real personal data stored.
97
 
98
  Outcome:
99
 
100
- - WP12 is implemented and awaits GitHub Actions, Hugging Face sync and app verification.
101
- - Next recommended workpackage is `WP12B — v13.6 Two-mode UI skeleton app verification closeout`.
102
 
103
  ---
104
 
105
- ## WP11 — v13.5 Two-mode reinsert UI planning
106
 
107
- Status: completed; planning/specification-only workpackage.
108
 
109
  Purpose:
110
 
111
- - Plan the future two-mode UI before changing Streamlit UI code.
112
- - Clearly separate `Anonimiseren` from `Originele waarden terugzetten`.
113
- - Decide where pasted-text, TXT and DOCX reinsert should fit.
114
- - Compare current single-scroll workflow, tabs and landing-card options.
115
- - Define the next safe UI implementation workpackage.
 
 
 
 
 
 
 
 
 
 
 
 
 
116
 
117
  Outcome:
118
 
@@ -193,7 +217,7 @@ Outcome:
193
 
194
  Possible directions:
195
 
196
- - WP12B app verification closeout.
197
  - TXT reinsert upload/download UI.
198
  - DOCX reinsert upload/download UI.
199
  - PDF text extraction research only after separate reliability review.
 
26
 
27
  ---
28
 
29
+ ## WP12-FIX — v13.6 Two-mode UI content separation cleanup
30
 
31
  Status: implemented; awaiting GitHub Actions, Hugging Face sync and app verification.
32
 
33
  Purpose:
34
 
35
+ - Fix the WP12 app-verification issue where mode navigation existed but content was not separated enough.
36
+ - Ensure `Originele waarden terugzetten` does not show the full anonymization/review/export workflow above the reinsert flow.
37
+ - Keep `Anonimiseren` focused on the existing anonymization workflow.
38
+ - Keep `Originele waarden terugzetten` focused on Scrub Key load + local pasted-text reinsert.
 
 
39
 
40
  Files added or changed:
41
 
42
  - Changed `fix_streamlit_nested_expanders.py`.
43
+ - Changed `tests/test_two_mode_ui_patch.py`.
44
  - Changed `WORKPACKAGES.md`.
45
  - Changed `CHANGELOG.md`.
46
+ - Added `handover/workpackages/20260608_0000_v13_6_two_mode_content_separation_cleanup.md`.
47
 
48
  Main change:
49
 
50
+ - The earlier WP12 two-mode skeleton already existed, but only added visible mode navigation.
51
+ - WP12-FIX replaces skeleton-only rendering with conditional mode rendering using `solidprivacy_work_mode = st.radio(...)`.
52
+ - If the user selects `Originele waarden terugzetten`, the app renders only:
53
+ - `Scrub Key laden`;
54
+ - Scrub Key upload/paste validation;
55
+ - pasted-text local reinsert;
56
+ - restored-output warning;
57
+ - local-only/no-AI/no-cloud text;
58
+ - `Zet originele waarden lokaal terug`;
59
+ - `Herstelde tekst`;
60
+ - `Download herstelde tekst (.txt)`;
61
+ - `Controleverslag terugzetten`.
62
+ - The existing anonymization workflow is rendered under the `Anonimiseren` branch.
63
+ - The anonymization/export review summary keeps Scrub Key JSON export, but no longer embeds Scrub Key import/reinsert inside the scrubbed export block.
64
+
65
+ Tests updated:
66
+
67
+ - `tests/test_two_mode_ui_patch.py` now checks:
68
+ - both mode labels exist;
69
+ - conditional work-mode rendering exists;
70
+ - reinsert markers are associated with `Originele waarden terugzetten`;
71
+ - anonymization markers are associated with the `Anonimiseren` branch;
72
+ - reinsert flow is not embedded in the anonymization review/export summary block;
73
  - existing Scrub Key export/import labels remain;
74
+ - existing scrubbed download markers remain;
 
 
75
  - no TXT upload reinsert UI was added;
76
  - no DOCX upload reinsert UI was added;
77
  - no PDF reinsert was added;
 
80
 
81
  Validation:
82
 
83
+ - Coordinator evidence for prior WP12 showed green Actions/sync, but app verification found the content separation issue:
84
+ - `Tests #145 green — commit 5d879cc`;
85
+ - `Sync #159 green — commit 5d879cc`;
86
+ - `Tests #146 green — commit 79d771e`;
87
+ - `Sync #160 green — commit 79d771e`;
88
+ - `Tests #147 green — commit e106f7c`;
89
+ - `Sync #161 green — commit e106f7c`.
90
+ - Local clone/test run for WP12-FIX could not be performed in the container because outbound GitHub DNS failed:
91
  - `Could not resolve host: github.com`.
92
+ - GitHub Actions: awaiting verification for WP12-FIX commits.
93
+ - Hugging Face sync: awaiting verification for WP12-FIX commits.
94
  - App verification: required because UI behavior changed.
95
 
96
  Intentionally not changed:
 
102
  - No AI calls added.
103
  - No cloud processing added.
104
  - No automatic document rehydration added.
105
+ - No existing TXT, CSV, DOCX or PDF scrubbed export/download semantics intentionally changed inside `Anonimiseren`.
106
+ - No Scrub Key JSON export behavior intentionally changed inside `Anonimiseren`.
107
+ - No Scrub Key storage, secrets, tokens or real personal data added.
108
 
109
  Outcome:
110
 
111
+ - WP12-FIX is implemented and awaits GitHub Actions, Hugging Face sync and app verification.
112
+ - Next recommended workpackage is `WP12-FIX-CLOSEOUT — v13.6 Two-mode content separation app verification closeout`.
113
 
114
  ---
115
 
116
+ ## WP12 — v13.6 Two-mode UI skeleton and tab separation
117
 
118
+ Status: implemented; coordinator evidence showed Actions/sync green, but app verification found insufficient content separation.
119
 
120
  Purpose:
121
 
122
+ - Implement the first two-mode UI structure with minimal risk.
123
+ - Make the two main user intents visible:
124
+ - `Anonimiseren`;
125
+ - `Originele waarden terugzetten`.
126
+ - Keep existing behavior working.
127
+ - Avoid a full landing-page refactor.
128
+
129
+ Outcome:
130
+
131
+ - WP12 created the first visible mode skeleton.
132
+ - App verification showed that content was not yet separated clearly enough.
133
+ - WP12-FIX was created to address this.
134
+
135
+ ---
136
+
137
+ ## WP11 — v13.5 Two-mode reinsert UI planning
138
+
139
+ Status: completed; planning/specification-only workpackage.
140
 
141
  Outcome:
142
 
 
217
 
218
  Possible directions:
219
 
220
+ - WP12-FIX-CLOSEOUT app verification closeout.
221
  - TXT reinsert upload/download UI.
222
  - DOCX reinsert upload/download UI.
223
  - PDF text extraction research only after separate reliability review.