solidprivacy commited on
Commit
286037b
·
1 Parent(s): 0c5bee3

Add cross-flow regression implementation handover

Browse files
handover/workpackages/20260806_1157_processed_text_selection_cross_flow_regression.md ADDED
@@ -0,0 +1,57 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ # Handover — SCRUB-WP_PROCESSED_TEXT_SELECTION_CROSS_FLOW_REGRESSION
2
+
3
+ Repository: `solidprivacy-nl/scrub`
4
+ Role: `implementation_operations`
5
+ Status: `RELEASE_CANDIDATE_READY`; GitHub Actions and independent assurance pending
6
+
7
+ ## Summary
8
+
9
+ Added synthetic chain-level regression tests for the existing processed-text selection feature. The candidate exercises the real selection inspect/commit path and then proves that the resulting document-bound `manual_selection` row enters the same review-table-authoritative downstream path as other included rows.
10
+
11
+ This implementation handover is not assurance evidence. The separate assurance worker must record its initial decision before reading it.
12
+
13
+ ## Files added
14
+
15
+ - `tests/test_processed_text_selection_cross_flow_regression.py`
16
+ - `PROCESSED_TEXT_SELECTION_CROSS_FLOW_REGRESSION.md`
17
+ - `workpackage_claims/scrub_wp_processed_text_selection_cross_flow_regression.md`
18
+ - `handover/workpackages/20260806_1157_processed_text_selection_cross_flow_regression.md`
19
+
20
+ ## Files changed
21
+
22
+ - `ROADMAP.md`
23
+ - `WORKPACKAGES.md`
24
+ - `CHANGELOG.md`
25
+ - governance/project instruction files as recorded in the paired governance-adoption handover
26
+
27
+ ## Tests
28
+
29
+ Five focused synthetic regression tests were added for:
30
+
31
+ 1. one selection-created row as the shared authoritative input for processed-text export, replacement CSV, scrub report and bound Scrub Key;
32
+ 2. bound TXT export and verified TXT reinsert;
33
+ 3. original-DOCX replacement and verified DOCX reinsert;
34
+ 4. authoritative `include=false` behavior across export and Scrub Key omission;
35
+ 5. free custom replacement remaining in document export while verified bound-key validation fails closed.
36
+
37
+ The tests also assert selection provenance, all-exact occurrence count, document binding, local-only metadata, no AI/cloud processing and exact restoration of the synthetic source text.
38
+
39
+ ## Validation
40
+
41
+ - Local tests: unavailable in the connector-only implementation session
42
+ - GitHub Actions: pending on candidate PR
43
+ - Hugging Face sync: not applicable; no runtime files changed
44
+ - App verification: not applicable; no UI behavior changed
45
+ - Independent governance status: pending; implementation deliberately issued no PASS
46
+
47
+ ## Remaining risks
48
+
49
+ - The new tests still require execution on the exact PR head.
50
+ - The regression proves current supported TXT/DOCX surfaces; it does not expand known DOCX reinsert limitations such as split placeholders, comments, tracked-change-only parts, footnotes/endnotes, text boxes or metadata.
51
+ - No production behavior was changed; a test failure must return to implementation rather than be repaired by the assurance worker.
52
+
53
+ ## Next recommended step
54
+
55
+ - Open the candidate PR and obtain raw GitHub Actions evidence.
56
+ - A separate `governance_release_assurance` worker/session claims `SCRUB-WP_PROCESSED_TEXT_SELECTION_CROSS_FLOW_REGRESSION_VERIFY`, independently reconstructs the tests and candidate diff, and records `PASS`, `FAIL` or `INDETERMINATE` before opening this handover.
57
+ - Do not start `SCRUB-WP_PREMIUM_CORE_FLOW_UI_CONTRACT` until both the governance-adoption and cross-flow verification packages pass.