swexcel

Current development package and historical checkpoints

2026-10-06: Full API interfaces, examples and helpers are implemented in 0.1.0-dev.4. The explicit VBA compile gate passed through the authorized Windows script. See current evidence and API guide. Update 2026-10-07: downloaded-package checks passed on the existing profile; see download evidence and preview quickstart. Clean-profile stable-release acceptance remains pending.

The sections below preserve the earlier checkpoint record; their pending/stop statements describe those earlier versions, not the current development package.

Historical checkpoint and stop boundary

2026-10-05 update: The user lifted the pre-Parallels stop and authorized Windows verification. Recorded evidence includes a fresh MSVC x64 DLL with 106 matching exports, real Microsoft 365 workbook generation, source parity, all 18 smoke checks, numerical parity, fresh-session reopening, relocation, failure diagnostics and state isolation. Version 0.1.0-dev.3 includes fixes discovered in the real Windows build. The explicit full-project VBE compile check is unverified because Parallels UI control was unreliable. Full API and downloaded-release acceptance remain pending. The preparation record below is historical; its earlier stop is superseded.

This checkpoint prepares plan step 1, proving integration. The next required work executes Windows tools and real Microsoft 365 Excel in Parallels. The user requested a pause before that work; the VM must not be resumed or used during checkpoint preparation.

Present

Required Windows gate

Follow WINDOWS-TESTING.md: compile the latest engine with x64 MSVC, build/import the VBA workbook, explicitly compile VBA, execute the integration checks, inspect scalar/spill/detail formulas, record Excel build and actual process architecture, compare with freshly built swetest, and save/reopen the package. Neither architecture compatibility nor successful VBA compilation can be inferred from static tests on macOS.

The official latest-release Windows DLL is unchanged from the original binary. A fresh source build is therefore required to verify that the engine update actually uses the latest source. Retain build evidence separately from the runtime version string.

V1 still pending after the gate

Complete semantic buffer/units/file contracts for all exports; safe wrappers and every appropriate worksheet function; configuration command interfaces; UTC/UT1/TT and fractional offsets; houses and range helpers; all API-family examples; all required numerical/error/state/coverage tests; data/body-specific boundaries; source/workbook parity; downloaded-ZIP macro onboarding, path and conflict cases; final public release acceptance. Do not expand worksheet coverage before resolving foundational loader/ABI/spill failures.

Verification evidence

Version 0.1.0-dev.1, verified on 2026-10-01:

Windows engine build, VBA compilation, live calculations, rendered workbook inspection and packaged release acceptance remain pending. Generated source-only packages carry checkpoint-status.json with that distinction. The VM was not started or resumed.