4 Commits

Include renames

Author	SHA1	Message	Date
jochen	b0c4b849a7	Judge an upstream pin's host like any name, and harden the upstream unpack (review 35, hq issue 345) ... The url was skipped by the installation check, so an installation's host or an address passed; it is judged whole now, the vendor's host declared in the artifact's names-on-purpose, and an address or a reserved name as the host is refused. Only the version's dotted-quad reading is skipped. The unpack caps its entries, drains xz before waiting for it, reads a pax global header and a nested within's parents, and a redirect off https is not followed.	2026-10-12 13:51:35 +02:00
jochen	b849af53dd	Let an archive be an upstream release pinned by URL and sha256, mirrored by the build seat (hq issue 345, ADR 0316) ... A mail client's release is about 80 MB per version, too large to keep in a repository at every upgrade, and an add-on whose licence forbids copying it to third parties may not be in a repository at all. An archive artifact may now name url, sha256 and version (and file or within) instead of from: the build seat fetches it once, refuses it when its digest is not the pin's and names both, keeps it in its workspace under the digest (a vendor that serves only its newest version cannot break a later build of the same pin), and packs it like any archive, so a node gets the mesh's own archive by digest and never asks the vendor. The build seat's image carries xz, which Go's standard library does not read. The installation check takes the vendor's address and version of such a pin for the world's, as a registry is an image's.	2026-10-12 13:51:35 +02:00
jochen	76babaea52	Read stored manifests leniently and mark the defaults layer (hq ADR 0262 review) ... A strict read of the stored catalogue fails every plan and send once a manifest uses a field an older controller lacks; registration stays strict. A node named default lost its layer to the name check. Judge the operator's keys by whole words, and scan a default under any key.	2026-10-08 17:24:32 +02:00
jschoubben	d9dbc9a59a	A definition names no installation: the check, an operator's value, a context on the git seat ... InstallationProblems judges every value the mesh acts on for a name under a public top-level domain or a public address, with prose, the world's registries, resolvers and certificate authorities exempt, and a name a resource means on purpose declared with its reason (names-on-purpose). Run by module check and a catalogue-wide test, not yet at registration, while the declared list shrinks. ${setting:<key>} fills a file from the assignment's settings and is refused when nothing set it. A build context may live on the git seat; the request carries the seat's clone base (novox/hq ADR 0112, ADR 0155, issues 122 and 134).	2026-09-30 18:38:06 +02:00