build(deps): bump vyncint/termlens/.github/actions/report from 0.11.2 to 0.11.3 in the actions-minor-patch group

[dependabot]

Bumps the actions-minor-patch group with 1 update: vyncint/termlens/.github/actions/report.

Updates vyncint/termlens/.github/actions/report from 0.11.2 to 0.11.3

Release notes

Sourced from vyncint/termlens/.github/actions/report's releases.

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 defect in the other argument position, refused for its reason: in a script the two usually come from two variables, and the loser is the one somebody meant. A repeat of the same flag is refused too. Both spellings of --out count, a refused render creates no file, and one format with one --out behaves exactly as before. Neither form was ever documented — the usage has always read (--svg | --html | …) [--out PATH] — but a script that passed two saw exit 0 and now sees 2.

• The 1.0 readiness criteria are a section of docs/STABILITY.md — "The 1.0 readiness criteria", the seven of #335 verbatim — instead of an issue (#472). #335 closed on 2026-09-16 while the candidate statement in the README, this file and STABILITY.md, and three places in docs/RELEASING.md, still cited it as the live record; all of them now link the section, which is where a criterion is recorded as met.

• skills/termlens/SKILL.md's reference tables: locate has one row instead of two that disagreed, with its accessors and why there is no row() (#459); Screen::visual_bells() and Terminal::frame_timings() have rows (#460); .record_budget(cells) states its unit and its default, 2,000,000 cells (#476). §9b names every render format, not only SVG.

• CONTRIBUTING §3 states the rule the skill gives agents first — no sleep as a wait — and names the suite's two sleeps as its exceptions, each with a comment where it sits saying why (#474).

• docs/LIMITATIONS.md names one more Unix-only assertion: the tab-stop extension a resize performs. ConPTY applies ResizePseudoConsole on its own thread, so a program's output written right after a resize can be laid out at the old width; the stress run for this release caught the test that pins the rule doing exactly that, once in 300 Windows iterations. On Windows, wait for the program's own repaint after resize() before asserting on layout. resize itself is unchanged and still claimed there.

Fixed

• termlens inspect --help documents --, the end-of-options marker it has always accepted (#453). It changes the outcome in exactly one case, a program whose name begins with -, which is the one case where a user could not discover it: the help they were pointed at did not have it. examples/inspect.rs has documented it since 0.9.0; the command now says the same thing, and a test tells a flag-shaped program name from an option by which failure comes back.

... (truncated)

Changelog

Sourced from vyncint/termlens/.github/actions/report's changelog.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.11.0 is the stability candidate: from that release no promised item changes incompatibly before 1.0. A change that must break one ships as a new candidate (0.12.0) with a migration table and restarts the observation window of the 1.0 readiness criteria; a patch release does not. 1.0 follows those criteria, not a date.

A breaking change is always listed under a Changed or Removed heading, in a bullet that begins Breaking: — the semver gate in CI reads that marker.

[Unreleased]

[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).

... (truncated)

Commits

• 5830c93 test: wait for the last row painted before masking, and one MSYS exclusion (#...
• bc1a2f8 test: the resize tab-stop rule is Unix-only under ConPTY (#499)
• 37609b7 test: wait for the newline, not the marker, before typing a Tab (#498)
• c15b62f chore: release v0.11.3 (#496)
• 54e4d8d test(ci): hold the published binary to both trailers and every = spelling (#495)
• 73266e4 docs: the 1.0 criteria in STABILITY.md, and the skill tables caught up (#492)
• 47bf4f9 fix(cli): a bare termlens - is still an unknown command (#494)
• ff0e070 fix(cli): refuse a second render format or --out, and document inspect -- (#489)
• ce61e56 test(ci): add a DCO gate selftest (#493)
• 0c8e4c1 fix(cli): start inspect's silence window at the first output, not the spawn (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions