ci: run the adapter tests and fuzz campaigns on every push #55

Open

james.maes wants to merge 2 commits from ci/gate-adapters-and-commits into main

pull from: ci/gate-adapters-and-commits

merge into: KofTwentyTwo:main

KofTwentyTwo:main

KofTwentyTwo:fix/settings-store

KofTwentyTwo:feat/gitea-links-and-share

KofTwentyTwo:test/pin-untrusted-input-boundaries

KofTwentyTwo:fix/activation-startup

KofTwentyTwo:fix/renderer-input-bounds

KofTwentyTwo:ci/sdk-pin-matches-locks

KofTwentyTwo:dependabot/github_actions/actions-0bd4aa7237

KofTwentyTwo:dependabot/npm_and_yarn/eslint-10.13.0

KofTwentyTwo:feat/windows-viewer

Conversation 0 Commits 2 Files Changed 15

+266 -89

2 Commits

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	1b47a0a07a	ci: count coverage from the lines and fail a fuzz filter that matches nothing ... The coverage gate now counts covered lines itself instead of reading the report's summary rate, matches package names exactly, and shows the percentage rounded down. Its tests cover reports whose stated rate disagrees with their lines, several packages, and several reports. The long fuzz campaigns run only on main and tags, where they differ from what the ordinary test run already did, decide that from the ref, print the iteration count, and fail when their filter matches no test. Test helpers no longer remove the temp folder and registry key that all test processes share: a second process could be creating its own entry there at that moment. AGENTS.md, the fuzzing assessment and the installed-update guide describe what runs today. Refs #54 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-10 19:03:52 -06:00
james.maesandClaude Fable 5.2	24d5d13fc4	ci: run the adapter tests and fuzz campaigns on every push ... The Gitea build now runs the Windows adapter tests (everything in the UiTests assembly outside the new Desktop category) and the seeded parser campaigns: 500 iterations on topic branches, 10000 on main and tags. It clears the results directory first, because the host runner keeps its workspace, and no longer passes secrets it does not use. The coverage gate rejects a package with no measured lines, names the report it used, and lists only that report's uncovered lines. The core project no longer locks the SDK linker package: no project publishes as a single file, and the entry broke locked restore whenever the SDK patch level moved. Locked self-contained publishing of the app and the update probe still restores. Developer docs give the commands CI runs, say which checks have no automated run while the GitHub mirror has Actions switched off, and state that a tag currently publishes nothing. Test temp folders and the test registry parent key are removed when the last test is done. Closes #54 Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-10 18:15:39 -06:00