build(deps): bump termlens from 0.11.2 to 0.11.4 in the cargo-minor-patch group across 1 directory

[dependabot]

Bumps the cargo-minor-patch group with 1 update in the / directory: termlens.

Updates termlens from 0.11.2 to 0.11.4

Release notes

Sourced from termlens's releases.

v0.11.4

Changed

• The published termlens-cli no longer ships its tests (#519), as the library stopped shipping its own in 0.11.2 (#385). Its corpus test read ../termlens/tests/compat, a directory outside the package, so cargo test on the download failed for everyone; the rest drove a binary built from the workspace. src/ and the README are unchanged. A new gate, check-package-contents.sh, fails CI if either crate ships tests/ again.
• The rustdoc gains runnable examples for Key::encode (#511) and Screen::cell, whose coordinates are row first, the opposite of Screen::size (#512), and an # Errors section on Screen::parse (#510). Ten doctests stopped discarding the Result of the send that ends them (#513).
• SECURITY.md counts the three unsafe blocks there are, File::from_raw_fd included, and says the lint enforces each block's #[allow] rather than the count (#520).
• docs/DESIGN.md names all seven _for wait twins (#507), says what DECSTR resets instead of "not modelled at all", and counts visual_bells among four cumulative counters (#508). CONTRIBUTING lists every job required-green needs (#509), and tools/preflight.sh -h prints its usage instead of refusing the flag as misuse (#518).

Fixed

• termlens diff --help and termlens render --help say what exit code 2 means, as the top-level help does: bad arguments, or a file that is missing or not a saved screen, and for render an --out path that cannot be written. diff --help said only "a file could not be read", and render --help stated no exit codes at all (#514).
• Every --help — termlens inspect, diff, render and examples/inspect.rs — names the --flag=value spelling their parsers have accepted since 0.11.2 (#515).
• On Windows, termlens inspect and examples/inspect.rs give a program 2 s after the wait ends to report its exit, up from 500 ms (#501). ConPTY never reports the terminal closing, so a program that has just exited ends the wait by the silence window instead, and a shell that took more than 800 ms from its last byte to its exit status was reported still running (killed on exit). A program that is still running, as a TUI is, now waits the extra 1.5 s before it is killed. Nothing changes on Unix.

v0.11.3

Changed

• termlens render refuses a second format flag or a second --out, naming the conflict, printing its usage and exiting 2, instead of silently keeping the last one (#450). render --svg --html screen.snap asked for an SVG and got HTML at exit 0; --out first.txt --out second.txt wrote only second.txt and said nothing. This is #364's

... (truncated)

Changelog

Sourced from termlens's changelog.

[0.11.4] - 2026-09-27

Changed

• The published termlens-cli no longer ships its tests (#519), as the library stopped shipping its own in 0.11.2 (#385). Its corpus test read ../termlens/tests/compat, a directory outside the package, so cargo test on the download failed for everyone; the rest drove a binary built from the workspace. src/ and the README are unchanged. A new gate, check-package-contents.sh, fails CI if either crate ships tests/ again.
• The rustdoc gains runnable examples for Key::encode (#511) and Screen::cell, whose coordinates are row first, the opposite of Screen::size (#512), and an # Errors section on Screen::parse (#510). Ten doctests stopped discarding the Result of the send that ends them (#513).
• SECURITY.md counts the three unsafe blocks there are, File::from_raw_fd included, and says the lint enforces each block's #[allow] rather than the count (#520).
• docs/DESIGN.md names all seven _for wait twins (#507), says what DECSTR resets instead of "not modelled at all", and counts visual_bells among four cumulative counters (#508). CONTRIBUTING lists every job required-green needs (#509), and tools/preflight.sh -h prints its usage instead of refusing the flag as misuse (#518).

Fixed

• termlens diff --help and termlens render --help say what exit code 2 means, as the top-level help does: bad arguments, or a file that is missing or not a saved screen, and for render an --out path that cannot be written. diff --help said only "a file could not be read", and render --help stated no exit codes at all (#514).
• Every --help — termlens inspect, diff, render and examples/inspect.rs — names the --flag=value spelling their parsers have accepted since 0.11.2 (#515).
• On Windows, termlens inspect and examples/inspect.rs give a program 2 s after the wait ends to report its exit, up from 500 ms (#501). ConPTY never reports the terminal closing, so a program that has just exited ends the wait by the silence window instead, and a shell that took more than 800 ms from its last byte to its exit status was reported still running (killed on exit). A program that is still running, as a TUI is, now waits the extra 1.5 s before it is killed. Nothing changes on Unix.

[0.11.3] - 2026-09-23

Changed

• termlens render refuses a second format flag or a second --out, naming the conflict, printing its usage and exiting 2, instead of silently keeping the last one (#450). render --svg --html screen.snap

... (truncated)

Commits

• de7fe39 chore: release v0.11.4 (#531)
• 7e1b0be fix(inspect): a longer reap grace on Windows; inspect tests print the trailer...
• 5fd72ad fix: the published termlens-cli no longer ships tests it cannot pass (#529)
• e3b6a38 fix(cli): every --help names the attached spelling and what exit code 2 means...
• 305bb02 test: a hard reset keeps its records; the key table covers every F-key and Ct...
• 948eb9f docs: six stale claims in DESIGN, CONTRIBUTING, SECURITY and rustdoc (#526)
• 812916d docs: propagate send's Result in doctests (#525)
• e57326d docs(screen): add a row-first example to Screen::cell (#524)
• 026b259 fix: accept preflight help flags (#523)
• af29a04 docs: add Key encode example (#522)
• Additional commits viewable in compare view

[github-actions]

Commit policy check failed. AI assistance is welcome; AI attribution is not. Remove the trailer and recommit — you are the author of record.

Fix a branch with git rebase -i (or git commit --amend) to drop the trailer, then force-push. The offending commits are listed in the job log.

[vyncint]

@dependabot recreate