Pimp My IDE / Garage Dispatch
Back to garage
September 26, 2026 | office runtimes / agent output / round-trip proof

Make the office file come back alive.

Univer 1.0.2 fixed workbook data that could disappear after reopening, PDF spacing errors, and chart colors that could vanish on render. That patch list is a test plan for every agent that edits office files.

The take. A successful save proves that bytes landed. It does not prove the structure is valid, formulas recalculate, the page looks right, or another application can reopen the file without losing meaning.
Build a round-trip test

A generated document has more than one truth.

Univer now describes itself as one runtime for spreadsheets, documents, presentations, boards, tables, and PDFs. Its site says agents can call a Facade API in a headless Node.js setup. That is a concrete shift from driving a visual office app through clicks. The agent can work against document data and commands directly.[1]

Direct access is useful. It also makes a weak check easier to mistake for a finished artifact. A data structure can serialize without proving that formulas ran, charts retained their data, fonts resolved, or another program interpreted the package the same way.

Do not test an office file only at the moment it leaves the agent.

The release notes name three distinct failure planes.

Univer 1.0.2 says it repaired whitespace handling during PDF import, added Courier fallbacks, and preserved PDF import reports while restoring or appending pages. Those are import and render concerns.[2]

The same release fixed standalone PivotCharts that could reopen without calculated data because saved source fields loaded before the chart definition. It also fixed explicit pie and doughnut slice colors that could become invisible with a transparent series fill. One bug lived in restoration order. Another lived in visual composition. Both could survive a simple "file exists" check.[2]

The format tree is necessary evidence, not the whole verdict.

Microsoft's Open XML SDK works with the package parts and strongly typed elements behind Word, Excel, and PowerPoint files. Its documentation is organized around word-processing, spreadsheet, presentation, drawing, chart, relationship, and version-specific element families. That structure is inspectable.[3]

A structural validator can catch malformed packages and unsupported elements. It cannot tell you whether a chart communicates the intended comparison, a slide has clipped text, a formula result is stale, or a reopened workbook kept the same calculated state. Those require different witnesses.

Run four laps against the artifact.

  1. Structure. Parse the saved package. Check relationships, required parts, names, sheets, styles, comments, alt text, and the exact fields the task asked to change.
  2. Calculate. Recalculate formulas and refresh derived objects where the format permits it. Compare key values against independent expected results.
  3. Render. Export representative pages, sheets, and slides. Check clipping, font fallback, hidden content, chart fills, contrast, and pagination.
  4. Reopen. Close the writer. Open the saved artifact in the target reader, save it again if that is part of the workflow, and repeat the critical structure, value, and render checks.

Use a fixture with the awkward parts your real work contains. For a workbook, include formulas, named ranges, hidden sheets, charts, dates, and blanks. For a presentation, include overflow-prone text, speaker notes, linked images, and a chart. The tunnel below writes the test plan. It does not inspect or certify a file.

Interactive makeover / artifact test planner

Office round-trip tunnel

Traditional purpose replaced: one "file saved" toast. Better version: choose the artifact, close four ordered inspection gates, and copy a plan that leaves results blank until you run the real tools.

Load the test fixture

The native radio group chooses one office artifact. Each square gate adds a required test section. Selection records intent, not a passing result.

Artifact under test
Round-trip inspection gates
ROUTE BLOCKED0 / 4 GATES
The dashed guide is not a cleared route. The file stops at the first missing test section.

Parse the saved file first.

No test section checks whether the artifact has the requested structure.

StructureMISSING
CalculateMISSING
RenderMISSING
ReopenMISSING

Four selected gates means the test plan has four sections. It does not mean any office file passed.

Print the round-trip plan

Replace each required marker with the exact application, version, file hash, command, output, and reviewed result.

Sources read, not vibes

Source log
  1. Univer Office SDK overview and installation and basic usage guide, read September 26, 2026. Product scope, headless Node.js path, Facade API, plugin and preset modes, dependency-version warning, and registration-order boundary.
  2. Univer 1.0.2 release notes, published September 24, 2026. PDF import and persistence fixes, PivotChart reopen-order fix, chart color-rendering fix, accessibility work, and no-public-API-change note.
  3. Microsoft Open XML SDK documentation, read September 26, 2026. Package and typed-element access for word-processing, spreadsheet, presentation, drawing, chart, relationship, and version-specific document structures.
  4. GitHub Trending and Hacker News were inspected for current developer-tool context. GitHub Trending surfaced Univer; neither listing supports the technical claims above.

Source boundary. The named defects and fixes come from Univer's own release notes. Pimp My IDE read the public repository, release record, product documentation, and Microsoft documentation. It did not install Univer, generate an office file with it, reproduce the defects, or certify format fidelity. The tunnel is a test-plan generator, not a validator.