Release DCAB 0.27 form-data-only-save case

README.md

@@ -17,7 +17,7 @@ size_categories:
 
 # Document Change Assurance Benchmark (DCAB)
 
-This dataset mirrors the deterministic fixture corpus from [DCAB v0.26.0](https://github.com/SybilGambleyyu/document-change-benchmark/tree/v0.26.0). It contains 37 paired synthetic WordprocessingML cases for static document-change assurance.
+This dataset mirrors the deterministic fixture corpus from [DCAB v0.27.0](https://github.com/SybilGambleyyu/document-change-benchmark/tree/v0.27.0). It contains 38 paired synthetic WordprocessingML cases for static document-change assurance.
 
 Each case directory provides a baseline package, candidate package, and target-free `truth.json`. The public truth files describe only a narrow fact category and a reference review convention. They never disclose URI-like targets, field instructions or fragmented field-code runs, VML shape IDs or target frames, linked-OLE ProgIDs/object IDs/update modes, DrawingML nonvisual object names/descriptions/IDs, raw hidden serialization values, graphic-data URIs, ActiveX control names/class IDs/persistence metadata, document-variable names or values, mail-merge recipient hashes or inclusion values, save-through-XSLT anchors or local solution identifiers, attached-custom-XML-schema namespace values, raw `w:linkStyles` or `w:removePersonalInformation` serialization values, permission marker IDs or individual editor assignments, task-pane web-extension IDs, classic-comment anchors and paragraph IDs, comment author/initial/date/body values, raw `commentsExtended` serialization values, frameset layout/name/size values, thumbnail relationship sources/targets, content types, part paths, references, store descriptors, property values, XPath values, relationship IDs, custom XML values, thumbnail image bytes, Markup Compatibility branch bodies, feature-prefix or qualified-name values, compatibility-rule values, or opaque payload bytes.
 
@@ -33,7 +33,7 @@ fixtures/
   ...
 ```
 
-The corpus covers direct Word and legacy VML shape hyperlinks, `HYPERLINK`, simple and fragmented complex `INCLUDETEXT`, `DDE`, and `DOCVARIABLE` fields, persisted document variables, attached custom XML schema declarations, automatic field-recalculation-on-open, template-style-update-on-open, and personal-information-removal-on-save settings, editable-range permission markup, task-pane Office web-extension auto-show configuration, Office 2013 `commentsExtended` done metadata, attached-template, mail-merge data-source/recipient-selection, and save-through-XSLT settings, master-subdocument and frameset-source dependencies, legacy VML linked-OLE objects, DrawingML linked-picture relationships and direct nonvisual visibility declarations, alternative-format import payloads, hidden text, tracked insertion markup, Track Changes and document protection settings, bound and unbound custom-XML payloads, relationship-bound OPC package-thumbnail payloads, OOXML Markup Compatibility choice requirements, VBA project payload boundaries, embedded OLE payload boundaries, and ActiveX control-persistence payload boundaries.
+The corpus covers direct Word and legacy VML shape hyperlinks, `HYPERLINK`, simple and fragmented complex `INCLUDETEXT`, `DDE`, `DOCVARIABLE`, and fixed legacy `FORMTEXT` fields, persisted document variables, attached custom XML schema declarations, automatic field-recalculation-on-open, template-style-update-on-open, personal-information-removal-on-save, and form-data-only-save settings, editable-range permission markup, task-pane Office web-extension auto-show configuration, Office 2013 `commentsExtended` done metadata, attached-template, mail-merge data-source/recipient-selection, and save-through-XSLT settings, master-subdocument and frameset-source dependencies, legacy VML linked-OLE objects, DrawingML linked-picture relationships and direct nonvisual visibility declarations, alternative-format import payloads, hidden text, tracked insertion markup, Track Changes and document protection settings, bound and unbound custom-XML payloads, relationship-bound OPC package-thumbnail payloads, OOXML Markup Compatibility choice requirements, VBA project payload boundaries, embedded OLE payload boundaries, and ActiveX control-persistence payload boundaries.
 
 ## Safety boundary
 
@@ -47,6 +47,8 @@ The Markup Compatibility pair retains one `mc:AlternateContent`, one `mc:Choice`
 
 The DrawingML visibility pair retains one compact inline DrawingML carrier, its package topology, and all stored Word text while changing only direct `wp:docPr/@hidden` from `false` to `true`. It does not identify a visual object, calculate effective visibility, choose an MCE branch, lay out or render DrawingML, or claim client behavior.
 
+The form-data-only-save pair retains one fixed legacy `FORMTEXT` carrier, its package topology, and all stored Word text while changing only direct `w:saveFormsData/@w:val` from `false` to `true`. It does not read or evaluate a form-field value, open Word, save a document, emit a delimited record, determine a delimiter, or claim client behavior.
+
 ## Reproducibility
 
 The source repository includes a deterministic builder and independent structural verifier:
@@ -60,4 +62,4 @@ This mirror has no special execution requirement. It is provided under the MIT l
 
 ## Scope
 
-DCAB does not claim client rendering/runtime compatibility or universal security policy. It is a narrow, tool-neutral static-review benchmark. In particular, it does not resolve or follow links; retrieve sources, templates, frame documents, or mail-merge data; parse or decode opaque macro, thumbnail, OLE, ActiveX, or alternative-format payloads; interpret unbound custom-XML data; resolve an MCE feature prefix or choose an MCE branch; calculate effective DrawingML visibility; update/evaluate fields; open Word; activate objects; execute code; synchronize comments or task panes; or assert client behavior. See the [repository README](https://github.com/SybilGambleyyu/document-change-benchmark) and [v0.26 research notes](https://github.com/SybilGambleyyu/document-change-benchmark/blob/v0.26.0/RESEARCH.md) for the exact contracts and limits.
+DCAB does not claim client rendering/runtime compatibility or universal security policy. It is a narrow, tool-neutral static-review benchmark. In particular, it does not resolve or follow links; retrieve sources, templates, frame documents, or mail-merge data; parse or decode opaque macro, thumbnail, OLE, ActiveX, or alternative-format payloads; interpret unbound custom-XML data; resolve an MCE feature prefix or choose an MCE branch; calculate effective DrawingML visibility; update/evaluate fields; read a form value; open Word; save a document; emit a form-data record; activate objects; execute code; synchronize comments or task panes; or assert client behavior. See the [repository README](https://github.com/SybilGambleyyu/document-change-benchmark) and [v0.27 research notes](https://github.com/SybilGambleyyu/document-change-benchmark/blob/v0.27.0/RESEARCH.md) for the exact contracts and limits.

RESEARCH.md

@@ -43,6 +43,26 @@ None of that implies absence of other relevant work. It identifies a concrete in
 - [`w:documentProtection`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.documentprotection?view=openxml-3.0.1) records editing restrictions but is documented as not being a security feature; DCAB therefore models only a password-free declaration and makes no security claim.
 - [Word OOXML documentation](https://learn.microsoft.com/en-us/office/dev/add-ins/word/create-better-add-ins-for-word-with-office-open-xml) describes OOXML as Word's native file format and demonstrates structured document tag markup.
 
+## Form-data-only save boundary
+
+Microsoft's Open XML SDK documents
+[`w:saveFormsData`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.saveformsdata?view=openxml-3.0.1)
+as a direct `CT_OnOff` child of Document Settings. Its contract describes
+form-field-content-only saving as a delimited text record, while Word's
+[`Document.SaveFormsData` documentation](https://learn.microsoft.com/en-us/office/vba/api/word.document.saveformsdata)
+uses a different delimiter description. That disagreement is precisely why
+DCAB treats the fixture as a stored-configuration boundary, not an emitted-file
+assertion.
+
+The new pair fixes a complete, legacy `FORMTEXT` field (begin/separate/end
+markers, `w:ffData`, name, enabled state, exit-calculation state, text input
+default, maximum length, and fixed result) in both packages. It changes only
+the direct `w:saveFormsData/@w:val` `false`/`true` declaration in
+`word/settings.xml`. It does not open Word, evaluate a field, inspect a form
+value, save a document, emit a delimited record, infer a delimiter, or assert
+client behavior. Released DocFence 0.37 maps the aggregate state transition
+without exposing the setting serialization or form-field material.
+
 ## Design implications
 
 1. The oracle must be deliberately partial and target-free. A benchmark should not force tools to disclose URL-like destinations, field arguments, data-binding XPath values, or opaque payload fingerprints.

fixtures/manifest.jsonl

@@ -16,6 +16,7 @@
 {"id": "review.field_recalculation_on_open_enabled", "schema_version": 1, "truth": "review.field_recalculation_on_open_enabled/truth.json"}
 {"id": "review.template_style_update_on_open_enabled", "schema_version": 1, "truth": "review.template_style_update_on_open_enabled/truth.json"}
 {"id": "review.personal_information_removal_on_save_enabled", "schema_version": 1, "truth": "review.personal_information_removal_on_save_enabled/truth.json"}
+{"id": "review.save_forms_data_enabled", "schema_version": 1, "truth": "review.save_forms_data_enabled/truth.json"}
 {"id": "external.subdocument_target_retargeted", "schema_version": 1, "truth": "external.subdocument_target_retargeted/truth.json"}
 {"id": "external.frameset_source_target_retargeted", "schema_version": 1, "truth": "external.frameset_source_target_retargeted/truth.json"}
 {"id": "external.vml_linked_ole_object_target_retargeted", "schema_version": 1, "truth": "external.vml_linked_ole_object_target_retargeted/truth.json"}

fixtures/review.save_forms_data_enabled/truth.json

@@ -0,0 +1,21 @@
+{
+  "baseline": "baseline.docx",
+  "candidate": "candidate.docx",
+  "coverage_expectations": [],
+  "description": "A direct Settings leaf changes from explicit disabled to enabled while a fixed legacy FORMTEXT field remains stored in both documents. The pair does not open a client or perform a save/export.",
+  "facts": [
+    {
+      "kind": "save_forms_data_enabled",
+      "source": "word_settings"
+    }
+  ],
+  "id": "review.save_forms_data_enabled",
+  "invariants": {
+    "changed_member_count": 1,
+    "package_member_set_stable": true,
+    "stored_text_stable": true
+  },
+  "review_expectation": "review",
+  "schema_version": 1,
+  "title": "Form-data-only save enabled"
+}