4 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	4797790959	Catalogue checks follow the narrowed mesh-sdk: a sibling replace is no forge fetch, no source imports what left mesh-sdk, nothing requires the controller's repository (ADR 0593 §1, §11) ... deps skips a forge requirement the go.mod already replaces to a directory (a package of the module's own repository), which it used to look for in a clone beside the check and fail. The new check removedpackages refuses an import of a package mesh-sdk gave up and a use of the build runner through mesh-sdk's buildstep; it is red on mesh-provisioner until the provisioner stops composing (the release's provisioner subtask). controllerdeps also refuses a go.mod requiring the controller's repository. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 18:34:55 +01:00
jschoubben	ba49a7f0f9	mesh-build-go: a reads-outside marker lists what its tests read, so its package is kept until one of those files changes (issue 1936) ... 47 packages carried the marker and were never kept: about 2000 tests per level ran on every check, whatever it changed. The marker now lists, as paths or globs from the repository's root (? before a path whose absence is read), what the package's tests read outside it; the digest hashes those files with the package's own non-Go files. A marker that lists nothing, names an unclean path, or a line that matches nothing keeps today's never-kept digest. The 46 markers list their reads; checks/deps and checks/trunk lose theirs (their tests read only temporary directories). Digest form 6. Quick fix of issue 1936, chosen by the operator 2026-10-26 21:56; the thorough fix (the Go test log's files kept with each verdict) stays on the issue.	2026-10-26 22:02:58 +01:00
jschoubben	16d7b1898d	Mark the packages whose tests read files outside their directory, found by the review (issue 1935)	2026-10-24 04:38:49 +02:00
jochen	de8a866189	Fail the check when a module's tests could not run, and take a pinned SDK from its clone beside (issue 385) ... A module whose dependencies could not be fetched was said NOT TESTED and the repository check passed, so a merge on it would have landed untested code. The build seat clones the SDK beside every check already: a forge requirement the module cache lacks is now taken from that clone through a go.mod of its own, and a module that still cannot be built fails the check by name and why. A TypeScript module whose dependencies the toolchain lacks fails the same way.	2026-10-12 12:03:50 +02:00