[drietsch]

Follows core v0.71.13 (additive on protocol 71, core ADR 159).

A record flow re-splits after a handle resize

subscribeChainReflow already re-paginates a record flow on any document.onDidChange event that carries reflow, keyed off the field's presence. Until now only a resizeFrame (mutationApplied) carried one. Core v0.71.13 also reports it on gestureCommitted when a chain frame is resized by its handles, and plugin-sdk 0.2.58 passes it through. So the fix needs no logic change in this bundle. An older host reports a handle resize without it and nothing is re-paginated, as before. The docs say so.

Real-core lanes on canvas-wasm 0.71.13, and what that moved

The real-core tests ran on canvas-wasm 0.71.1. On 0.71.13 two engine facts moved the Data Merge budget (W8), and the merge now follows them:

• Every frame, a fresh one included, lists frameDropShadowKnockedOut: true (InDesign's default), and the merge copied it onto each of the 57 merged frames. It joins the fresh-frame defaults that are not copied, so mutation ops stay 403.
• An item's geometry names its page's origin (pageOrigin) and answers the item transform in page space, so the hit-test probe for the page's spread origin took four tries. Where the engine names the origin, no probe runs: host calls go 17 → 16 and reads 11 → 10 (the budget is lowered). An engine without it is probed as before.

Tests

• chain-gesture-reflow-real-core.spec.ts: 40 records paginated over two chained frames (real core, data-js, DuckDB); the first frame shortened by a resize/south gesture through the host (begin, update, commit). The flow re-paginates, the first frame holds fewer records and the second more, and all 40 are placed. A move by the gesture kit re-paginates nothing. On the 0.2.45 contract it fails ("the handle resize re-paginated the flow: expected 0 to be greater than 0").
• merge-real-core.spec.ts: one template read with and without the page's origin gives the same frames; no probe runs with it.
• merge.test.ts: the knocked-out shadow is a fresh-frame default.

Release

• @paged-media/data 0.1.0-canary.16 → 0.1.0-canary.17 (package and manifest; a merge publishes it).
• Peers unchanged: @paged-media/plugin-api / @paged-media/plugin-sdk >=0.2.45-canary.0. Detection is by field presence; nothing needs 0.2.58.
• Real-core tests: canvas-wasm 0.71.1 → 0.71.13; contract pins (plugin-api, plugin-sdk, devDependencies) 0.2.45-canary.0 → 0.2.58-canary.0.
• docs/status.md is read from this code at 0.1.0-canary.17 and now describes the live chain pagination.

CI note

The check job (cargo-deny) fails on three RustSec advisories against zip published 2026-10-16/17: RUSTSEC-2026-0367, -0368, -0369. All three concern ZipArchive::extract() / ZipStreamReader::extract(), which this repo does not call. This PR changes no Rust or Cargo file, so main fails the same way. Whether to upgrade zip or record an ignore is a separate decision.

🤖 Generated with Claude Code