Files
onenote-tools/docs/REFERENCE_IMPLEMENTATIONS.md

4.9 KiB

Specifications and pinned references

Version 0.1.0 records these immutable implementation revisions:

Repository Exact revision Use
toolbox-sdk 5e206baf42dfae5a00f2743fb2cc501bb12d9b7a App contract, React shell, manifest schema/testkit, and nested-path behavior
toolbox-portal 5d2e466ad61e36a0e2be2a2d8459b1a127f53f11 Reviewed ZIP shape, exact checksum lock, and independent-app assembly model
onenote.rs 5138a39a3f4e72b840932f9872fecde52fa9da60 Selected desktop/FSSHTTPB OneStore and MS-ONE structures adapted into TypeScript
rust-cab c5839f5fdfa4c4e7cc9b22f570c79c96af0560e2 CAB structures, checksum, enumeration/extraction, MSZIP history, and unit fixtures
compcol 04a6db2aa7bd487a89c559631d79d1b384139f50 Quantum bit reader, arithmetic models, LZ window, CAB sentinel behavior, and tests
lzxd 0.2.5 4748e43594e3e30cff2ace3a6ad7a376c9816fdd LZX bitstream, Huffman, block/window, match, and E8 logic adapted into TypeScript

The SDK and Portal revisions were inspected from the local repositories. The four parser references were cloned and reviewed at the hashes above; a branch name or package version alone is not used as provenance. Source-level mappings and behavioural deviations are in PORTING.md.

Normative Microsoft documents

The implementation uses the official specifications as the source of format truth and the pinned projects as implementation references:

The Microsoft documents are linked rather than copied. Their published pages can change independently; the source references and golden bytes remain pinned for reproducibility.

one2html is deliberately not pinned or inspected because visual HTML rendering is outside this release.