8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	c46009709d	The key keeper is ssh-client's published package sshkeys, taken by series by the three build modules; Said, KindBuilder, ExecRunnerClean from the Delivery sdk (B5d; ADR 0634 §1; issue 1966) ... Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-05 14:55:59 +01:00
jschoubben	af280050d6	CAT-BN3: mesh-build-node publishes through the registry seats and holds no registry credential ... Bundles go through oci-artifact-registry and answer the seat's reference; a trunk package is packed under the builder's version and published through npm-package-registry, so the holder can check it with the builder. Reads are anonymous, so the write pair, the sealed secret and the store's address go. The one-part sender moves into buildstep for both build modules, so the move to the registry clients is made in one place. Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 15:30:06 +01:00
jschoubben	45084af849	A relative replace of a go.mod still resolves in the temporary modfile, so a module with a sibling package builds and verifies through the pins path ... ensureModfile copied go.mod word for word into pins/<dir>/, where `go mod verify` runs, so a replace to ./x or ../x pointed nowhere (route-proxy's failure of 2026-11-02 13:53, met a second time with the release's sibling packages). Every relative replace target is now made absolute under the tree the go.mod came from. mesh-build-node installs a module's own npm packages in a scratch copy of package.json, so a file:, link: or portal: dependency on a relative path would fail the same way; it is refused naming the package and its path, as a module without a lock is. Quick fix: rewrite the one replace route-proxy had, in ensureModfile (minutes). Thorough fix: the kind, a go.mod or package.json copied away from its tree, for every replace form (single, block, with a version, ./ and ../) in the one place all copies go through (ensureModfile, which versions.go and the pins share), and the same kind in the other build module that copies a manifest. Chosen: thorough, since it was met twice and hides a failure until the delivery (quick-or-thorough, fix-a-bug-met-twice). Test: TestARelativeReplaceStillResolvesInTheTemporaryModfile runs real go mod verify in the pins directory. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-11-02 19:36:15 +01:00
jschoubben	e8a953818c	Merge main into fix/1901-failure-contract: pin mesh-sdk a2759ec (the group's sdk head), the failure kit check's marker lists what it reads (issue 1936), and the registry test's password can no longer match a random workspace name (issue 1901)	2026-10-27 00:39:35 +01:00
jschoubben	3def293d94	Build modules: no thread limit without the composer's share; with it, the share over their own capacity (ADR 0553 round 2) ... Change A rebuilds the three build modules, so their runtimes restart once; it changes nothing else about their builds until change B gives them the share.	2026-10-26 14:41:12 +01:00
jschoubben	64b9ded2db	Build modules: a per-node processor cap, and each step's threads within it (issue 1806) ... The operator's desktop slows while it builds (shanks at 92%, the Go build runtime at 1650% of 24 processors). The build modules declare cpu-cap (default shanks=50,g14=50,ace=75), which the composer turns into the runtime's quota at idle priority; each step's go, node and buildah commands get GOMAXPROCS and UV_THREADPOOL_SIZE for their part of it, and the status tools show the limits and what the kernel holds the runtime to.	2026-10-26 13:41:05 +01:00
mesh-tools	00fa5e74d0	Review round 1 for the Node build module: registry for other @novox packages and refused bundles (1489), toolchain.reported stream (1483, 1488), re-pin to mesh-sdk 36d6f774; delta part 4 of 4	2026-10-20 21:12:10 +00:00
mesh-tools	bda49fb945	Test the Node build module's fetch, forge files, manifest and guard (issues 1489, 1484, 1488), part 19 of 19	2026-10-20 21:05:55 +00:00