# Windows native picture lifecycle, September 21, 2026

Two fresh minimal picture controls pass on the recovered Windows host. A PowerPoint-created PNG picture and a PNG deck exported with the installed registry packages both open/save/close/reopen successfully, retain their current alt text and geometry, and produce identical original/reopened native PNG bytes. Both exact owned presentations closed successfully. The supervisor reviewed the full native slide images below.

This establishes a minimal lifecycle checkpoint. It does not certify actual picture edits, shared furniture, crop/reflow fidelity, notes-master ordering, native tabs, physical font identity or the full ecosystem. The September 10 failures remain historical evidence; this run does not identify their original cause.

## Exact context

The owner confirmed saving wanted presentations, closing and reopening PowerPoint normally, and resolving recovery/dialog state before this task resumed Office access. Supported UI inspection then showed PowerPoint ready. Only one bounded Office helper ran at a time; the deadline was 45 seconds. Per-call stages, input snapshots, original and saved presentations, PNGs, exact verifier sources, parent results and cleanup observations are retained.

| Component | Recorded value |
| --- | --- |
| Node | 24.21.0, isolated task executable |
| Windows | 25H2, build 26200.9457 |
| Windows PowerShell | 5.1.26100.9444 |
| PowerPoint | 16.0.20326.20158 |
| PowerPoint executable SHA-256 | `07cbe68cde7596058a6890c471389a7a70a090ee42f01975d72ea6d643f82021` |
| Native control SHA-256 | `e3ae357f0e2cd45a72c83a0ac545d42d8698d84d81498a8bffd9dba8c761017a` |
| Existing process helper SHA-256 | `2a49f620b77fd998b791b835dd17bc64487f9539fa20935cbbba50ea5b7dc015` |
| Registry train | core 0.11.0, CLI/renderer 0.9.0, PPTX 0.9.1, editor 0.8.0 |
| Registry consumer lock SHA-256 | `4868f13254e3e681566164da8427d3716ceaa025435e4606e5e15fc8a87bc305` |
| Harness PR | [opf-pptx #46](https://github.com/OpenPresentation/opf-pptx/pull/46), implementation `d1eabc20fd7caeadc56c7238f50d8c4ea7d1a26b`; subsequent CI commit adds non-Office Windows checks |

`source-pins.json` identifies the refreshed source repositories. This native input was generated by a **separate registry consumer**, not a linked source graph. The package audit passed 561 checks, including 519 public export/bin resolutions, installed version/integrity checks, and absence of sibling links. Four OPF package manifest/dist trees plus the PPTX vendor tree and consumer lock are byte-bound by `registry-picture-01/generation.json`. This is not a claim about every installed transitive dependency byte. The CLI version is independently audited, but it was not the exporter used by the PNG fixture.

## Results by acceptance surface

| Surface | Result and boundary |
| --- | --- |
| Archive/XML | Registry generation validates XML and internal relationship/content-type targets. Independent Python ZIP CRC/XML checks pass for original and PowerPoint-saved PPTX files. This is not Open XML SDK or native edit certification. |
| Current content reimport | The PowerPoint-saved registry deck imports one current PNG with exact source image bytes and alt text, with no diagnostics. |
| Native lifecycle | Both workers completed, exited zero without timeout, and confirmed closure of their own exact paths. Actual native edits remain a later gate. |
| Geometry and raster | One embedded native picture per control. Original and reopened bounds match expected geometry within the unchanged 0.02pt gate. Native original/reopened PNG hashes are identical. This does not establish OPF-preview pixel identity. |
| Fonts/embedding | These picture-only controls exercise no text/font identity or embedding acceptance. No font programs or PDF proofs are distributed here. |
| Portable/installed checks | Registry audit passes; targeted source image-fit, image-import, shared-furniture and furniture-provenance checks pass under Node 24. Their controlled XML edits are not desktop Office edits. Browser acceptance remains separate. |

Native-created picture: expected left/top/width/height **180 / 120 / 600 / 300 pt**, 30 comparator checks pass. Saved PPTX SHA-256: `4702a6cef0635e47b5ae29ea237f623d8d3c6d896f185f0f8e98267b82ec45f9`. Both native PNG hashes: `465ef449c7776df237bdac5a3ddd3a610d7fa783c61c76498eb2ae0184d752c2`.

![Reviewed native-created picture](native-created-01/reopened.png)

Registry-created picture: expected **43.2 / 51.6 / 873.6 / 436.8 pt**, 35 comparator checks pass. Source PPTX SHA-256: `9bc1779b13d77641bb4040abed99178b5bee146ba505b7ef49fed82ea6f5a937`. Saved PPTX SHA-256: `636256e030cc3cd007d0ef6102540ee08abe4842869fcfee18a691e001bec533`. Both native PNG hashes: `f773035c4cfc0e2203e1ecc66de2a348ee328fd2cc58f79389593aa3f11b4455`.

![Reviewed registry-exported picture](registry-native-01/reopened.png)

## Harness checks and preserved failures

`worker-controls-01/` records successful literal argument handling, an exact failure exit, and termination of the one owned dummy helper after its deadline; it never creates Office. `picture-harness-controls-01.json` and `picture-harness-controls-03.json` independently verify PowerShell parsing, preservation of empty/populated collection identity and the stop-after-error latch.

`comparator-controls-01/` is explicitly **synthetic, offline evidence**, not additional Office runs. All eight controls behaved as intended: missing generation binding, missing raster, altered source snapshot, an out-of-run raster path, geometry beyond 0.02pt, and bad/missing worker results fail with durable reports. Repeating a comparison preserves the first comparison; attempting to overwrite the saved imported OPF fails explicitly.

The initial generator used CommonJS resolution on the ESM-only core export and failed before Office. Its source snapshot/error are preserved. A subsequent child-process sandbox denial is retained in the generation log, followed by the successful permitted generation log. The first standalone checker revision failed because Windows PowerShell could not use `PSScriptRoot` in its parameter default; that exact failed script/error is preserved, and the corrected body-level default passes. None of these preparation failures is classified as a product or Office failure.

See [the harness instructions](https://github.com/OpenPresentation/opf-pptx/blob/d1eabc20fd7caeadc56c7238f50d8c4ea7d1a26b/docs/native-picture-control.md) for reproduction. The absolute paths in raw reports identify the original machine; copied evidence does not imply those paths resolve elsewhere. `SHA256SUMS.json` binds every included file except itself. Keep later runs in fresh directories and retain this checkpoint unchanged.

## Next gates

Proceed with actual native picture edits and current shared-furniture content/provenance. Then compare original versus controlled notes-master ordering, refresh native tabs/mixed-size paragraphs without relaxing tolerances, and test permitted fonts/embedding without overstating per-glyph identity. Core issue 87 and renderer issue 24 remain open; issue 88 stays with the main public-app task. No p:hf implementation, shaping archive merge, geometry draft, package publication or site deployment is part of this checkpoint.