@pptx-studio/model 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,25 @@
+# @pptx-studio/model
+
+## 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/geometry@0.1.0
+  - @pptx-studio/opc@0.1.0
+  - @pptx-studio/paint@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,183 @@
+# @pptx-studio/model
+
+The document model: the sheets, the chain between them, and the resolver everything else reads.
+
+A `.pptx` renders correctly or it does not, and almost all of the difference is here rather than in
+any renderer. A slide placeholder that PowerPoint wrote has no geometry, no fill, no line and no
+style of its own; every one of those comes down a chain of two hops whose rules are asymmetric,
+undocumented, and different from what every implementation this project has read assumes.
+
+Sub-phase 2.9. Everything below was measured against Microsoft PowerPoint rather than argued from
+the standard; the fixture is `corpus/ground-truth/sheets.json` and the reasoning is
+`docs/adr/phase-2-geometry-and-paint/0024-model-parse-and-resolve.md`.
+
+## `undefined` means the file did not say
+
+Every visual property is `T | undefined`, and absence is a fact the file states rather than a gap to
+be filled in.
+
+PowerPoint proves this about its own output. Create a slide from a layout and its title placeholder
+has no `a:xfrm` at all. Type into it and it still has none. Nudge it one point to the right and the
+whole resolved rectangle appears at once — inherited two hops, from the master, baked in:
+
+```xml
+<!-- untouched, and after typing -->
+<p:sp><p:nvSpPr>…<p:ph type="title"/>…</p:nvSpPr><p:spPr/>…</p:sp>
+
+<!-- after moving it one point -->
+<p:sp>…<p:spPr><a:xfrm><a:off x="850900" y="365125"/><a:ext cx="10515600" cy="1325563"/></a:xfrm>…
+```
+
+So a parser that defaults geometry at parse time destroys the only record of which shapes are still
+bound to their layout. That record is what Change Layout reads, what the inspector's provenance
+chips read, and what tells a theme swap which shapes to invalidate.
+
+## The two hops do not use the same key, and neither uses the pair
+
+This is the finding of the sub-phase, and it contradicts the plan that led to it.
+
+| hop             | matches on                                   | when nothing matches |
+| --------------- | -------------------------------------------- | -------------------- |
+| slide → layout  | **`@idx` alone.** `@type` is never consulted | orphan               |
+| layout → master | **the folded `@type`**, taking the first     | orphan               |
+
+Measured over 46 probes, each a slide placeholder with no geometry of its own whose rendered
+position names the layout placeholder it matched. Scored against the 34 that had a candidate set:
+
+| candidate rule                    | right |
+| --------------------------------- | ----- |
+| `@idx` alone                      | 34/34 |
+| family (title/content) and `@idx` | 24/34 |
+| `(type, idx)`                     | 13/34 |
+| `@type` alone                     | 6/34  |
+
+A slide `title` at idx 0 takes a layout `body` at idx 0. A slide `body` at idx 2 takes a layout
+`sldNum` at idx 2. A slide `title` at idx 9, against a layout that holds a title at idx 0, matches
+**nothing** and renders at the origin with zero size. No type is privileged — not the title family,
+not the header-and-footer trio, which is what the shuffled-type deck was built to find.
+
+The asymmetry is not arbitrary:
+
+- Every stock PowerPoint layout numbers its date, footer and slide-number placeholders **10, 11 and
+  12**, and every stock master numbers the same three **2, 3 and 4**. A second hop that looked at
+  `@idx` would inherit nothing in the templates Office ships.
+- A slide master's placeholder vocabulary is only `title`, `body`, `dt`, `ftr`, `sldNum` and `hdr`.
+  A master carrying `ctrTitle`, `subTitle`, `obj` or `pic` is **repaired on open**. So a second hop
+  that looked at the type as written would find nothing for the `ctrTitle` in layout 1 or the
+  `<p:ph idx="1"/>` in "Title and Content".
+
+`ctrTitle` folds to `title` and every content type folds to `body` on the way up. And each hop asks
+with the placeholder of the sheet it is _leaving_: a slide `obj` at idx 0 reaching a layout
+`ctrTitle` lands on the master's **title**, not its body.
+
+`<p:ph/>` with no attributes is `type="obj" idx="0"` — read back through PowerPoint's own object
+model as `ppPlaceholderObject`. ECMA's default for the attribute is `body`. The two agree at the
+first hop because it ignores the type, and at the second because `obj` folds to `body`; they agree
+by construction rather than by luck, which is worth knowing.
+
+## Every binding comes from the part's own `.rels`
+
+A slide part does not name its layout, a layout does not name its master, and a master does not name
+its theme. Each binding lives in exactly one place, and every other candidate is a trap:
+
+- **`p:sldLayoutIdLst` is not the binding.** A two-master deck saved by PowerPoint puts all 22
+  layouts in one flat `ppt/slideLayouts/` folder numbered 1 to 22, and which master owns which is
+  recorded only in the two masters' relationship parts.
+- **`ppt/presentation.xml.rels` has a `theme` relationship**, it always points at `theme1.xml`, and
+  reading it gives every slide the first master's palette. On a one-master deck — which is every
+  deck most people ever test with — that is indistinguishable from correct. Measured: two masters,
+  two themes, and `accent1` resolves to a different colour on each.
+- **A `.rels` file is not in `rId` order.** PowerPoint routinely writes `rId8` first.
+
+A missing binding is not an error. PowerPoint repairs a slide with no layout, a layout with no
+master and a master with no theme rather than refusing them, so `loadDocument` records a problem and
+leaves `parent` or `theme` as `null`. Refusing to _write_ one is `@pptx-studio/validate`'s job.
+
+## The style matrix, `phClr`, and the background share one rule
+
+`a:fillRef` and `p:bgRef` index the same two lists with the same offset, and they were measured
+independently against the same six theme entries. All six agreed.
+
+| `@idx`       | means                          |
+| ------------ | ------------------------------ |
+| `0`          | nothing at all                 |
+| `1`…`999`    | `a:fillStyleLst[idx − 1]`      |
+| `1000`       | nothing at all                 |
+| `1001`…      | `a:bgFillStyleLst[idx − 1001]` |
+| out of range | clamps to the last entry       |
+
+Out of range **clamps**: a `fillRef idx="4"` against a three-entry list paints the third, and a
+`bgRef idx="9999"` paints the last background entry. PowerPoint opens both without repairing, so a
+renderer that throws refuses a deck PowerPoint shows.
+
+Each entry is a _function_ of a colour. `<a:solidFill><a:schemeClr val="phClr"><a:lumMod
+val="60000"/></a:schemeClr></a:solidFill>` is the body and the reference is the call, with the
+reference's own colour child as the argument — and that argument may carry transforms of its own.
+PowerPoint's shape-style gallery writes `<a:schemeClr val="accent1"><a:shade val="15000"/></a:schemeClr>`
+on seven of its forty-two entries. Miss `phClr` and every themed shape renders black.
+
+`a:fontRef/@idx` is **not** a number. It is `major`, `minor` or `none`, and PowerPoint repairs a
+numeric one.
+
+The background takes the nearest sheet that declares a `p:bg` — slide, else layout, else master. An
+absent `p:bg` is the only thing that inherits: a slide declaring `<p:bgPr><a:noFill/>` paints nothing
+and does _not_ fall through, which is why `Background` is a value rather than a nullable fill.
+
+## `masterClrMapping` means _parent_, not master
+
+`a:masterClrMapping` says "the map already in force". For a slide, that is the **layout's** map. A
+layout carrying an `a:overrideClrMapping` changes the colours of every slide bound to it, and a
+slide's own override beats its layout's — measured with two overrides that disagreed, because two
+identical ones cannot tell you which applied. `dk1`/`lt1`/`dk2`/`lt2` bypass the map either way, as
+2.6 established.
+
+And the map that resolves a `p:bgRef`'s colour is the one in force on the sheet being _asked about_,
+not on the sheet the `bgRef` was written on. A slide whose `clrMapOvr` remaps `bg1` gets a different
+background out of the same master.
+
+## The resolver reports where it looked
+
+```ts
+resolve(shape, sheet, (s) => s.xfrm);
+// → { value, origin: 'masterPh', explicit: false, sheet, shape }
+```
+
+Carrying the origin costs one field and buys four features from one function — provenance chips,
+per-property Reset, layout-compatibility scoring, and correct theme invalidation — all reading the
+same function the renderer reads, so none of them can drift from what is on the screen. `explicit`
+is not the same as `origin === 'shape'`: a layout placeholder that declares a fill is explicit about
+that fill, and the slide inheriting it is not.
+
+Geometry is not special. Fills, lines, effects and `p:style` all travel the same chain, and all four
+were measured arriving from the layout placeholder and from the master placeholder through a layout
+that declared nothing.
+
+## What is not here
+
+- Nothing is painted. The renderers are 2.10.
+- The ten-source **text** cascade is 3.1. `Origin` already declares the five members only that
+  cascade can produce, so 3.1 adds cases rather than widening a type every consumer has switched on.
+- Commands, undo and history are Phase 5; Change Layout is 7.4. What PowerPoint rewrites when a
+  layout changes is recorded in the fixture and not acted on.
+- `a:effectDag` is not modelled — a directed graph of effect primitives PowerPoint has never been
+  observed to write. An `undefined` there means the shape re-emits byte for byte.
+- Group child coordinate spaces are parsed (`a:chOff`/`a:chExt`) and not applied; that is 2.10.
+
+## Fixtures
+
+`corpus/ground-truth/sheets.json` — 114 probes in 37 packages, sub-phase 2.9.
+
+The measurement is a **position**, and PowerPoint reports it directly. C3 and C4 sampled bitmaps
+because a fill and a stroke are pictures; an inheritance is not. A placeholder with no `a:xfrm` of
+its own still has a position, `Shape.Left` reports it in points, and that is the resolver's own
+answer read out of the resolver rather than reconstructed from what it painted. So every candidate
+parent sits in a rectangle no other candidate shares, and the rectangle a probe lands in names the
+parent it matched — one number, no fitting, no error bars.
+
+23 of the 37 packages are hostile and each is alone in its own file. 16 were refused or repaired.
+
+`model.test.ts` re-derives the matcher from the fixture's 34 recorded cases rather than comparing
+against a summary of them, so a rule that drifts fails on the measurements.
+
+See `docs/adr/phase-0-foundation/0007-ground-truth.md`, `docs/adr/phase-2-geometry-and-paint/0021-colour.md`, `docs/adr/phase-2-geometry-and-paint/0022-fills.md`,
+`docs/adr/phase-2-geometry-and-paint/0023-lines.md` and `docs/adr/phase-2-geometry-and-paint/0024-model-parse-and-resolve.md`.