Release DCAB 0.26 visibility fixture

README.md

@@ -17,9 +17,9 @@ size_categories:
 
 # Document Change Assurance Benchmark (DCAB)
 
-This dataset mirrors the deterministic fixture corpus from [DCAB v0.25.0](https://github.com/SybilGambleyyu/document-change-benchmark/tree/v0.25.0). It contains 36 paired synthetic WordprocessingML cases for static document-change assurance.
+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.
 
-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, 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.
+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.
 
 ## Layout
 
@@ -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, 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`, 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.
 
 ## Safety boundary
 
@@ -45,6 +45,8 @@ The package-thumbnail pair retains the standard root thumbnail relationship, `im
 
 The Markup Compatibility pair retains one `mc:AlternateContent`, one `mc:Choice`, one `mc:Fallback`, its package member set, and all stored Word text while changing only a private `Choice/@Requires` feature prefix. It does not validate MCE conformance, resolve the prefix, choose a branch, preprocess or save a package, or claim any client rendering behavior.
 
+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.
+
 ## Reproducibility
 
 The source repository includes a deterministic builder and independent structural verifier:
@@ -58,4 +60,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; 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.25 research notes](https://github.com/SybilGambleyyu/document-change-benchmark/blob/v0.25.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; 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.

RESEARCH.md

@@ -38,6 +38,7 @@ None of that implies absence of other relevant work. It identifies a concrete in
 - Microsoft's [Custom XML parts overview](https://learn.microsoft.com/en-us/visualstudio/vsto/custom-xml-parts-overview) describes embedded custom XML parts as package data that Office solutions can create or modify while a document is open or closed. A control binding is therefore not a precondition for a stored custom-XML review surface. DCAB's unbound pair fixes the ordinary custom-XML data/properties topology, relationship, and all Word text while changing only inert synthetic XML bytes. It neither parses the payload as application data nor asserts that Word displays, uses, or removes it. Released DocFence 0.33 records the same aggregate payload change and offers an opt-in candidate gate for a clean handoff.
 - The OOXML [Thumbnail Part contract](https://ooxml.info/docs/15/15.2/15.2.16/) defines a thumbnail image as an internally related package or part target, with at most one thumbnail relationship per source and no relationships from the thumbnail image itself. The Open XML SDK exposes a `WordprocessingDocument` [`AddThumbnailPart`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.packaging.wordprocessingdocument.addthumbnailpart?view=openxml-2.20.0) method. DCAB fixes one root-package relationship and `image/png` content type while changing only deterministic 1×1 synthetic PNG bytes. It neither decodes nor renders the image, and it does not claim that its pixels reflect the document or will be displayed by a client. Released DocFence 0.34 reports the same-count payload transition through an aggregate-only thumbnail inventory.
 - Microsoft's [introduction to markup compatibility](https://learn.microsoft.com/en-us/office/open-xml/general/introduction-to-markup-compatibility) explains that `AlternateContent` holds alternatives selected at runtime according to a consumer's processing settings and supported features, and that preprocessing may select and remove branches before a document is saved. DCAB fixes one standard MCE namespace declaration, a `Choice`/`Fallback` shape, all branch text, and the package topology while changing only `Choice/@Requires` between two declared feature prefixes. It does not validate MCE conformance, resolve a prefix, select a branch, target an Office version, preprocess or save a package, or make a client-behavior claim. DocFence 0.35 reports the same-count private requirement rewrite through an aggregate-only MCE inventory without exposing branch content or prefix values.
+- The Open XML SDK documents [`NonVisualDrawingProperties.Hidden`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.drawing.nonvisualdrawingproperties.hidden?view=openxml-3.0.1) as a stored state for an object that can remain present but hidden, with omission shown by default. DCAB fixes one compact inline DrawingML carrier, its package topology, and all stored Word text while changing only the direct `wp:docPr/@hidden` XML Boolean 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. DocFence 0.36 reports the aggregate-only static transition without exposing object metadata or the raw stored value.
 - [`w:vanish`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.vanish?view=openxml-3.0.1) and [`w:ins`](https://learn.microsoft.com/en-us/dotnet/api/documentformat.openxml.wordprocessing.insertedrun?view=openxml-3.0.1) are explicit WordprocessingML markup classes.
 - [`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.

fixtures/manifest.jsonl

@@ -31,6 +31,7 @@
 {"id": "review.unbound_custom_xml_payload_changed", "schema_version": 1, "truth": "review.unbound_custom_xml_payload_changed/truth.json"}
 {"id": "review.package_thumbnail_payload_changed", "schema_version": 1, "truth": "review.package_thumbnail_payload_changed/truth.json"}
 {"id": "review.markup_compatibility_choice_requirement_changed", "schema_version": 1, "truth": "review.markup_compatibility_choice_requirement_changed/truth.json"}
+{"id": "review.drawing_object_hidden_state_changed", "schema_version": 1, "truth": "review.drawing_object_hidden_state_changed/truth.json"}
 {"id": "macro.vba_project_payload_changed", "schema_version": 1, "truth": "macro.vba_project_payload_changed/truth.json"}
 {"id": "embedded.ole_payload_changed", "schema_version": 1, "truth": "embedded.ole_payload_changed/truth.json"}
 {"id": "embedded.activex_control_persistence_payload_changed", "schema_version": 1, "truth": "embedded.activex_control_persistence_payload_changed/truth.json"}

fixtures/review.drawing_object_hidden_state_changed/truth.json

@@ -0,0 +1,20 @@
+{
+  "baseline": "baseline.docx",
+  "candidate": "candidate.docx",
+  "coverage_expectations": [],
+  "description": "A compact DrawingML inline keeps its package topology and stored Word text fixed while the direct nonvisual wp:docPr hidden attribute changes from explicit false to true.",
+  "facts": [
+    {
+      "kind": "drawing_object_hidden_state_changed"
+    }
+  ],
+  "id": "review.drawing_object_hidden_state_changed",
+  "invariants": {
+    "changed_member_count": 1,
+    "package_member_set_stable": true,
+    "stored_text_stable": true
+  },
+  "review_expectation": "review",
+  "schema_version": 1,
+  "title": "DrawingML object hidden state changed"
+}