A request MUST be refused unless it names a program in lower case words, a version, a program file and at least one platform, and every address in it (an artifact or a checksum file) MUST be https with no credentials; a refusal MUST say which part is wrong.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
For each platform the tool MUST fetch the artifact and take its SHA-256 itself; a hash it was not asked to check MUST never be copied from the request or from a publisher's file as if it were its own.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
Where the request names the publisher's checksum, the tool MUST compare it with the hash it took and say verified, mismatch (with both hashes), absent (none named) or unreadable (the file or the line could not be read); a checksum file lists many artifacts and the line of the one named MUST be the one taken.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
Tests: passed: suite/pin.test.ts the hash is taken by the tool, and the line of the artifact in a checksum file of many is ; passed: suite/pin.test.ts a mismatch, a file with no line for the artifact and no checksum named each make the propo
For each platform the tool MUST prove the artifact unpacks by the rules of an install (0002-native-pinned-install) with the program at the folder named, and report why not where it does not; a platform that could not be fetched MUST say so and MUST NOT stop the other platforms.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
The proposal MUST be ready only where every platform is verified by the publisher and has its program; it MUST list for each platform every concern a reviewer should know (no checksum named, a mismatch, a program missing); it MUST say it is a proposal and MUST hold no secret; and its text MUST be the same for the same request whatever the order the platforms were written in.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
Tests: passed: suite/pin.test.ts a mismatch, a file with no line for the artifact and no checksum named each make the propo; passed: suite/pin.test.ts the proposal says it is a proposal, holds no pin, and has the same text whatever the order
The program pin REQUEST [--out FILE] MUST write the proposal to the file or print it, MUST change no pin and no store, and MUST end with status 0 where the proposal is ready, 2 where it is not, 1 where the request could not be read and 64 on a wrong use.
Enforced (check): .github: cd commons/archon-dialect-native-pinned && bun run verify — suite/pin.test.ts
Given a request with an http address, When it is read, Then it is refused naming the platform, per FR-001.
Given an artifact and a checksum file that lists it among others, When a pin is proposed, Then the hash is the one the tool took, the publisher's line is the one of the artifact and the platform is verified, per FR-002 and FR-003.
Given a publisher's checksum that differs, When a pin is proposed, Then the platform is mismatch with both hashes and the proposal is not ready, per FR-003 and FR-005.
Given no checksum named, When a pin is proposed, Then the platform is absent with the concern that this hash is the first seen, per FR-003 and FR-005.
Given an artifact that has no program where it is said to be, When a pin is proposed, Then the platform says why and the proposal is not ready, per FR-004.
Given one platform that cannot be fetched, When a pin is proposed, Then the other platforms are still proposed, per FR-004.
Given a request, Whenpin runs, Then the status is 0 where ready and 2 where not, and nothing but the proposal file is written, per FR-006.
A publisher's checksum file is served from the same account as the artifact, so verified shows the download was not damaged, not that the publisher is honest; the reviewer decides that.