| 1 | # Atomic page nesting |
| 2 | |
| 3 | The candidate nests `child` and `grandchild` from `../03-renamed` beneath the |
| 4 | `Same title` page, at levels 2 and 3. Section series order, section metadata |
| 5 | copies and the two page metadata revisions publish in one transaction. Page |
| 6 | bodies and prior revisions retain their identities and contents. |
| 7 | |
| 8 | `../04-nested` is the independent native control. `cold` is a fresh OneNote |
| 9 | reopen of the Rust candidate; all active page and section objects compare exactly. |
| 10 | The files differ in 48 header bytes, including file identity and version metadata; |
| 11 | all bytes after the header are identical. Both images are retained. The capture's |
| 12 | owned clone was removed; `provenance.json` records its source and teardown. |
| 13 | |
| 14 | Set `ONESTORE_PAGE_BATCH_OUTPUT` to a new directory and run the core unit test |
| 15 | `write::tests::multi::nesting_publishes_section_order_and_page_levels_in_one_transaction` |
| 16 | to export another candidate. Capture it with `tools/native_runner.py INPUT OUTPUT |
| 17 | --expected-pages 9 --collect-notebook`. Run `tools.test_page_lifecycle` after |
| 18 | building workspace examples to compare native navigation and document content. |
| 19 | |
| 20 | This fixture verifies the internal transaction writer. It does not define a |
| 21 | public page operation, offline conflict policy or implicit subpage movement. |