chore(deps): bump vyncint/termlens/.github/actions/report from 0.11.4 to 0.11.5

[dependabot]

Bumps vyncint/termlens/.github/actions/report from 0.11.4 to 0.11.5.

Release notes

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

v0.11.5

Changed

• The documentation was reviewed against the code, and each correction was checked by reading the code or running it:
  • README.md and the skill recommend cargo install termlens-cli --locked, the dependency set a release is tested with (#552), and AGENTS.md's layout lists the termlens-cli crate (#553).
  • The skill's rule 9 gives the true reason to return termlens::Result: a failing test prints the error's Debug form, screen included, as unwrap() would. §6 now reads that form as well as Display, and its unanswered-probe row links to docs/LIMITATIONS.md (#559). Rule 10, §6 and the mask row no longer say that format!("{:?}") equals Display, that every error carries a screen, or that mask_matching matches across a soft wrap (#562).
  • The rustdoc gains runnable examples for Screen::mask_matching (#551) and ScreenDiff::changed_rows and style_changes (#560). On docs.rs, Unsupported no longer shows Clipboard's summary, and Clipboard has one of its own (#562).
  • docs/DESIGN.md, CONTRIBUTING.md, docs/RELEASING.md, docs/LIMITATIONS.md and SECURITY.md now match the code. They cover the two translated character sets and DECSC saving the charset state, the SHELL=/bin/sh pin under env_clear, the tools/ directory, and the release checklist's two ungated copies of the version (#558). They also cover the unbounded writer queue, which CSI … t reports are answered, and Dependabot's carve-out from the bot-identity rule (#562).

Fixed

• A relative TerminalBuilder::current_dir, and so termlens inspect --cwd ./dir, runs a relative program path such as ./myapp inside that directory. The directory was applied twice — the program was looked up as dir/./myapp from inside dir — and the child died of a Rust runtime abort it could not report (fatal runtime error: assertion failed: output.write(&bytes).is_ok()), which inspect showed as exited: killed by signal: Aborted. A relative directory is now taken from the test process's own, as std::process::Command does. An absolute directory, or a bare program name found on PATH, was never affected.
• termlens inspect --help and examples/inspect.rs --help describe the wait and the environment as they are: the silence window starts only once the program has drawn something; the child also gets TERM=xterm-256color and SHELL=/bin/sh; and --inherit-env still replaces the caller's TERM unless --env TERM=… sets it. --cwd's argument is called DIR in the help and in its diagnostic, beside a paragraph about the PATH variable, and the help says a relative program path is found inside it. The CLI README's --cwd example ran a program from the wrong directory and is corrected.

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.6] - 2026-10-14

Fixed

• On Unix, a program that exists but cannot be executed now fails TerminalBuilder::spawn with an Error::Spawn that says why, and termlens inspect exits 2 with that message (#563). Typical causes are a missing #! interpreter, an interpreter that is not a program, a missing dynamic loader, and an argument list over the kernel's limit. The message names the interpreter, with any \r that CRLF line endings left on it shown escaped. spawn used to return Ok with a child already killed by SIGABRT (fatal runtime error: assertion failed: output.write(&bytes).is_ok()), which inspect showed as exited: killed by signal: Aborted. portable-pty closed the pipe std reports a failed exec through, so on Unix termlens now starts the child itself. Program resolution, the environment, the session and the signals are unchanged, and the child still inherits no descriptor besides its terminal. A working directory the child cannot enter is now named in the error. A few rare setups are still left to portable-pty, as before, and docs/DESIGN.md lists them.
• The second writer termlens opens on the PTY master is close-on-exec. A process the test started while a terminal was alive inherited it before, which kept the master open in a process unrelated to the terminal.
• With TERM set twice through .env, XTGETTCAP's TN reply reports the later value, the one the child gets. It reported the first, so an application could get two answers to "which terminal is this?".

[0.11.5] - 2026-10-07

Changed

... (truncated)

Commits

• 5b6bf71 chore: release v0.11.5 (#564)
• 5f4203e fix: a relative current_dir runs a relative program, and inspect's help says ...
• a9edfe7 docs: a review pass, fifteen claims the code contradicts (#562)
• a603aa9 docs: ScreenDiff's changed_rows and style_changes get runnable examples (#560)
• 6e7d7c4 docs: DESIGN, CONTRIBUTING and RELEASING catch up with the code (#558)
• 3181981 docs(skill): rule 9 gives the true reason, and §6 reads the Debug form too (#...
• cbd7f88 chore(deps): bump taiki-e/install-action (#557)
• f8ddee5 test: compare the written asciicast with the exported one apart from the cloc...
• cbf2ca8 docs: list termlens-cli in AGENTS.md's layout (#553)
• 3ff9c04 docs: recommend cargo install termlens-cli --locked (#552)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)