Supported method and limits

Structural references, not rendered pages

The local worker reads the minimum selected package XML needed for section properties, internal relationships and optional first/even-page selectors. It reports section order, header/footer kind and type, relationship IDs, referenced part paths, inheritance source and a structural state. It does not display body text or read the contents of referenced header/footer parts.

An explicit valid active reference is distinguished from an inherited reference. A declared first/even reference can be unused when its selector is off. Supported omitted-reference cases can be blank or fall back to the default; these labels describe this limited rule model, not a rendered-page assertion.

Unknown remains unknown

Broken, conflicting or unsafe relationships are not guessed. In particular, the first-page chain through an omitted reference in a selector-off intermediate section into a later selector-on section remains unknown. Duplicate same-type references, unsupported packages and Word’s recovery from damaged files are not assigned a preferred visual outcome.

The current adapter supports the conventional transitional WordprocessingML namespace and conventional main-document relationships. Other valid package conventions are not promised. External relationships are not fetched, and macros are not executed. No document is repaired, modified or exported.

Bounded local processing

The file limit is 8 MiB, with at most 512 archive entries and 16 MiB declared expansion. Selected XML is limited to 512 KiB per part and 1 MiB in total, with an expansion-ratio cap of 100. XML depth/node limits are 64/20,000; section/reference limits are 64/384. Unsupported or over-limit inputs receive an unknown result rather than an inferred Word diagnosis.

The adapter has a cooperative 3-second processing bound. Separately, the page terminates its worker on Cancel, replacement, Clear, completion, error, page departure or a 5-second deadline. Browser scheduling can delay that deadline; it is not a real-time guarantee. A restored cached page reloads cleanly instead of retaining an inert controller, selected file or old result. A native BFCache round trip has not been demonstrated.