Repository navigation
Run the authority cases in CI, from the same kit the page documents - #16
Merged
Merged
Conversation
added 2 commits
October 23, 2026 19:33
One workflow file runs the eight authority cases on the reader's own account, verifies the sealed records offline, and writes a trustharness.report/v1 report. The action reads the kit at a pinned commit, so the command on the evidence page and the command in CI are the same command. The report carries only what the run measured: cost rows are null with a reason, and comparison figures stay on the evidence page.
The same eight cases, run per pull request, with the report shape and the pin-it rule stated on the page that owns the numbers.
Merged
1 task done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a composite action next to the reproduce kit so the eight authority-at-dispatch cases can run on every pull request of a reader's repository, and a short section on the evidence page pointing at it.
action.ymlreadsproofable/docsatkit-ref(pin a commit), installs the kit, runsaad.mjs setup/run/verify, builds the report, uploads the sealed run, and fails the job when the offline check does not pass.report.mjsbuildstrustharness.report/v1from the sealed run directory only. It measures nothing itself: cost and performance rows arenullwith a reason, and every comparison figure stays a link to the evidence page.schema.jsonis the one report shape, witharm: review | self-runrequired.report.test.mjscovers a clean run, a failing case, and a refused directory (node --test).The action lives inside
docson purpose: the command on the evidence page and the command in someone's CI cannot drift, and there is no second copy of the measurement logic.Verified locally: the sparse fetch resolves
docs@0525e435c,npm ciinstalls the kit,node --testpasses 3/3, a fixture run reports 8/8 with seals passing, a one-case failure reports 7/8 withunauthorized_actions_through: 1and exit 2, and both reports validate against the schema. Not verified: a billed end-to-end run (needs an access key and credits).