4 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	0d5227ee77	Test a TypeScript module whose tests alone changed ... A change to a module's tests moves no build (hq ADR 0267), so the planner's modules leave it out; the TypeScript part also reads the modules the changed files are in.	2026-10-09 03:28:58 +02:00
jochen	f72903d05d	A TypeScript module with tests and no sources of its own is tested, not skipped ... powerlevel10k carries only data and a test that reads it; the part skipped it silently.	2026-10-09 03:23:01 +02:00
jochen	f072ca7297	Type-check and test every touched TypeScript module before it merges ... The catalogue's check ran only Go. A TypeScript module's change, the forge's among them, ran nothing of its own before it merged, and a type error would first have shown in its walk. A second part, declared with mesh-check-also and run in the TypeScript toolchain, type-checks each touched TypeScript module with the compiler and flags a build uses, against the SDK and Node types the toolchain holds, and runs its tests as its own npm test does. A module that needs a package the toolchain lacks, or has no tests, is said by name, never passed. The media catalogue's twin is hq issue 311.	2026-10-09 03:22:24 +02:00