@pptx-studio/validate 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,23 @@
+# @pptx-studio/validate
+
+## 0.1.0
+
+### Minor Changes
+
+- 7d905f4: First release.
+
+  `@pptx-studio/render-svg` turns a slide into an SVG string, and `pptx-studio render`
+  does it from the command line with no browser and no LibreOffice — text included,
+  measured out of the font's own tables. The other nine packages are what those two
+  are built on and are published because they have to be, not because their surface
+  is settled.
+
+  Everything here is pre-1.0 and the API will change. What will not change without a
+  very good reason is what the writer does to a package it was not asked to edit: a
+  part nobody touched is re-emitted byte for byte, across all 54 decks in the corpus.
+
+### Patch Changes
+
+- Updated dependencies [7d905f4]
+  - @pptx-studio/opc@0.1.0
+  - @pptx-studio/xml@0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Dewiride Technologies
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,43 @@
+PPTX Studio
+Copyright 2026 Dewiride Technologies
+
+This product includes software developed at Dewiride Technologies
+(https://github.com/Dewiride-Open-Source/Dewiride-PPTX-Studio).
+
+--------------------------------------------------------------------------------
+Third-party material redistributed in this repository
+--------------------------------------------------------------------------------
+
+Entries are added here at the moment the material lands, not at release time.
+
+  * Apache POI
+      Copyright The Apache Software Foundation
+      Licensed under the Apache License, Version 2.0.
+      https://poi.apache.org/
+
+    @pptx-studio/geometry contains the 187 DrawingML preset shape definitions,
+    transcoded at build time from POI's presetShapeDefinitions.xml by
+    tools/geometry-codegen. The transcoded form is a re-encoding of that file's
+    content and carries POI's copyright.
+
+    The file itself is not redistributed in this repository. The generated
+    modules in packages/geometry/src/presets record the SHA-256 of the exact
+    input they were produced from:
+
+      presetShapeDefinitions.xml, 538970 bytes
+      sha256 4a762444d8d85876881c02a5b1dedf6f73006fcd8acb7b4e393435615b37c780
+
+--------------------------------------------------------------------------------
+Attributions the plan commits us to, listed so the obligation is visible before
+the code arrives
+--------------------------------------------------------------------------------
+
+  * Pattern fill tiles (sub-phase 2.7) are generated from Mono libgdiplus.
+      libgdiplus - Copyright Novell, Inc. and contributors - MIT
+
+  * Metric-compatible substitute fonts ship in a separate package,
+    @pptx-studio/fonts-metric-compat, under SIL OFL 1.1 with its own
+    OFL.txt and reserved-font-name handling. They are deliberately kept out
+    of this Apache-2.0 tree so the licence boundary is a package boundary.
+
+See LEGAL.md for the clean-room record and the reimplementation basis.

package/README.md

@@ -0,0 +1,131 @@
+# @pptx-studio/validate
+
+**The repair firewall.** Twenty-nine rules a `.pptx` must not break, checked
+before any bytes are handed over, each finding carrying the part and the XPath.
+
+Apache-2.0 · browser and Web Worker only, no Node · part of
+[PPTX Studio](https://github.com/Dewiride-Open-Source/Dewiride-PPTX-Studio).
+
+```ts
+import { assertValid, formatReport, validatePackage } from '@pptx-studio/validate';
+
+// Diagnosing a file somebody sent you.
+const report = validatePackage({ bytes });
+console.log(formatReport(report, { explain: true }));
+
+// The export gate: throws unless the package is safe to hand over.
+assertValid({ store, baseline, bytes: store.write() });
+```
+
+## Why this exists
+
+PowerPoint emits no diagnostic log. When it refuses a file the message names no
+part, no element and no line — "PowerPoint could not open the file", or
+`0x80070570`, "the file or directory is corrupted and unreadable". When it
+_repairs_ one it says even less, and the user is left holding a deck that has
+quietly lost something.
+
+So this is not a schema validator with a nice report. It is the only feedback
+loop that exists, and it runs on every export in development and in production.
+
+## Twenty-nine rules, in two halves
+
+Roughly half come from ECMA-376: content-type coverage, `xsd:sequence` child
+order, `minOccurs`, the four identifier ranges. Those are derivable, and one of
+them literally is — the ordering table is generated from the Transitional
+schemas and checked against 194 148 elements PowerPoint wrote.
+
+The other half cannot be derived from anything. Each is the record of a package
+built with **one** change in it, opened in PowerPoint 16.0.20326, and declined:
+
+|        |                                                                                                |
+| ------ | ---------------------------------------------------------------------------------------------- |
+| `V022` | a `p:ph type="hdr"` on a slide. The other seven content types all open.                        |
+| `V023` | a geometry guide referenced but never defined. `ST_GeomGuideName` is an unconstrained token.   |
+| `V024` | a `c:strLit` inside a series `c:tx`, two elements away from where the literal forms are legal. |
+| `V025` | a `p:control`, in all eight forms tried. An empty `p:controls` is accepted.                    |
+| `V026` | a `cs:chartStyle` with thirty of its thirty-one entries. No chart style at all is fine.        |
+| `V019` | a master id colliding with a layout id. They are one number space and no schema says so.       |
+| `V020` | a `p:cNvPr/@id` between 2147483648 and 4294967294. 4294967295 opens; it is minus one.          |
+| `V009` | a slide without exactly one layout relationship; a `cx:chartSpace` with no `.rels`.            |
+| `V004` | a percent-escape of an _unreserved_ character in a part name. `0x808D1005`.                    |
+| `V012` | an `a:ahXY` directly under `a:custGeom`, without its `a:ahLst` wrapper.                        |
+
+Every rule carries a `why` recording what was tried and what opened, so whoever
+eventually contradicts one knows what they are contradicting.
+
+## It answers "did _we_ break it", not "is this valid"
+
+A fatal finding in a file the user imported ten seconds ago is information. The
+same finding in a file they just edited is a bug in us, and handing over the
+bytes would give them a repair prompt with no explanation.
+
+Refusing both would be the strict-looking choice and it is the wrong one: a deck
+with one pre-existing defect — a dangling image relationship, common in files
+that have been through three other tools — could then be opened here and never
+saved again. The editor would be refusing to give somebody back their own file
+over a problem it did not cause.
+
+So every finding carries an `origin`, and only `introduced` ones refuse an
+export. It is computed rather than judged per rule: the rules run a second time
+against the package **as it was opened** and the two reports are differenced.
+That second pass happens only when the first found something fatal, so a clean
+export pays nothing for it.
+
+## Nothing is silently skipped
+
+Three rules compare against the package as it was opened, and one reads the
+archive rather than the part store. Given neither, they do not run — and the
+report lists them under `skipped` with the reason, because a preservation rule
+that reports nothing because it had nothing to compare against looks exactly
+like one that found nothing. Parts that would not parse land in `problems` for
+the same reason.
+
+## How it is verified
+
+Two suites that check opposite things, and neither substitutes for the other.
+
+**It fires.** `validate.test.ts` breaks a minimal deck twenty-nine ways, one per
+rule, and asserts each rule reports the right part and the right XPath.
+
+**It is quiet.** `tools/corpus/suites/validate.test.ts` runs all fifty-two committed
+corpus decks through it and asserts no fatal finding. Every deck in that corpus
+opens in PowerPoint, so a rule that fires on one is a bug and there is no third
+possibility. Three rules were narrowed by exactly that run: `V012` was reporting
+`mc:AlternateContent` and other extension markup the ordering table simply has
+never read; `V020` was reporting shape ids reused across the two branches of one
+`mc:AlternateContent`, which are alternatives and may collide; and it found a
+real defect in our own `a20-tables`, which wrote a table style's fill without its
+`a:fill` wrapper in thirteen places.
+
+**And it fires on the right things.** `corpus/reject/` holds seventeen packages
+PowerPoint refuses, one measured finding each, and `C-REJECT` asserts each is
+caught by the rule its manifest names. Four rules have no instance anywhere in
+the good corpus — every file containing one is a file PowerPoint refuses — and
+without those fixtures they would be enforced entirely on trust.
+
+## What passing does not mean
+
+Necessary, not sufficient. PowerPoint rejects some schema-legal markup for
+reasons nobody has enumerated, and this package knows the ones we have found.
+The strongest defence is architectural — _never synthesize markup we did not
+read_. The second strongest is `cli bisect` (sub-phase 1.5), which reduces a deck
+PowerPoint refused until the smallest reproducing change is left, and whose
+output is how the measured rules above got here.
+
+## API
+
+|                                            |                                                                            |
+| ------------------------------------------ | -------------------------------------------------------------------------- |
+| `validatePackage(options)`                 | check a package; returns a `Report`, never throws for a finding            |
+| `assertValid(options)`                     | the same, but throws `ValidateError` when something we introduced is fatal |
+| `formatReport(report, options)`            | the report as text, grouped by part                                        |
+| `RULES`, `ruleById`, `RULE_IDS`            | the table, with `title`, `why`, `evidence` and `severity`                  |
+| `xpathOf`, `elementLocation`, `lineColumn` | locations, for a caller building its own report                            |
+
+`ValidateOptions` takes `store` (the package about to be written), `bytes` (the
+archive, for the two rules that read it), `baseline` (the package as it was
+opened) and `rules` (a subset). On an export, `store` must be the store the
+writer emitted from and not one re-opened from the written bytes — a re-opened
+store thinks every part came from the archive, and `V027` would then have no
+history to ask about.