fix(test): wait for rendered milestone fences

[wan9chi]

Motivation

On Windows Server 2022 build 20348, ConPTY can emit an OSC 8 milestone before printable text that the child wrote and flushed first. expect_milestone returned as soon as it decoded the control marker, so milestone screen assertions could observe an empty terminal.

What changed

• Pair each milestone marker with its zero-width rendered anchor before returning screen contents.
• Parse milestone protocol events incrementally across PTY read boundaries and preserve FIFO ordering when markers overtake their anchors.
• Add deterministic coverage for delayed fences, split sequences, and multiple overtaken markers.
• Temporarily stress the two milestone integration tests 100 times on the Namespace Windows Server 2022 runner.
• Update anyhow, crossbeam-epoch, and memmap2 to releases that fix the advisories reported by Security Analysis.

[wan9chi]

• fix(test): wait for rendered milestone fences #527 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[wan9chi]

Namespace verification evidence:

• Candidate fix: 4ef49d00a1bb1091e2ee5688d087e3e774538b6f
• Runner: namespace-profile-windows-4c-8g, Windows Server 2022 10.0.20348 (build 20348)
• Command: cargo-nextest nextest run --archive-file windows-tests.tar.zst --workspace-remap . --stress-count 100 -E 'package(=pty_terminal_test) & kind(=test) & binary(=milestone)'\n- Result: 100/100 stress iterations passed, covering 200 executions of the two milestone tests in 7.818 seconds\n- Job: https://github.com/voidzero-dev/vite-task/actions/runs/28995536226/job/86044312788

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	cargo/​anyhow@​1.0.101 ⏵ 1.0.103	+1
	cargo/​memmap2@​0.9.9 ⏵ 0.9.11

View full report