cv4vs-ci-loglisted

# Read a CI run A green run is not evidence the package is good. On 2026-07-21 three separate defects shipped through a `success` build: - The VSIX was packaged without the `WebView2/` folder — 16 entries instead of 22. It installed cleanly and threw `DirectoryNotFoundException` the moment the chat pane opened. - `dotnet-typegen` was not installed on the runners: the `Exec` exited 9009, `ContinueOnError` swallowed it, and the DTO codegen never ran. - `tgconfig.json` was shipped inside the VSIX (23 entries instead of 22). None of them was an error in the log. They were **absences** — a line that should have been printed and wasn't, or an `MSB3073` buried under 147 known warnings. Reading the log by hand took five attempts and two wrong filters, because CodeQL query *names* contain the word "error". This skill reads a finished run and answers one question: did every check actually run, and did anything real go wrong? **Read-only.** No fixes, no re-runs, no git commands. ## Procedure ### 1. Find the run ```powershell gh run list --branch <branch> --limit 1 --json databaseId,headSha,status,conclusion ``` No argument given → last run of the current branch. An argument may be a run id, a PR number, or a branch name. Two things to check before going further: - **`status` must be `completed`.** On a run still going the expected lines have not been printed yet and would read as absences. Say so and stop — this skill does not wait. - **Compare `headSha` with `git rev-p