jschoubben 0279c5c288 The check's cycle refusal meets no verb edge on a cycle and no package edge, and still refuses provisions and bases (ADR 0614 §3, §6; issue 774) ...

Rows in the judge's table: two modules invoking each other, or a verb closing a cycle with a provision, are not
refused; a cycle of provisions and one of bases are. The refusal's words name what a part waits on now.

Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn

2026-11-03 23:26:08 +01:00

..

testdata/captured

Build checks against the group's package heads, not go.mod pins

2026-11-01 02:41:22 +01:00

adr548_test.go

Tests wait on events or the clock they are given, never on milliseconds a loaded machine outlasts

2026-11-02 23:04:44 +01:00

askagain.go

Checker: delete a check's asks key at its end, so the state asks holds only the checks that run

2026-10-28 20:39:50 +01:00

beside.go

Place mesh-networking beside a node-engine check, so route-proxy's proofs of a composition are judged once this release runs

2026-11-02 20:40:01 +01:00

binaries_test.go

Checker refuses a program a commit of the branch added and a later one removed: it stays in history (issue 1577)

2026-10-26 19:47:53 +01:00

binaries.go

Checker refuses a program a commit of the branch added and a later one removed: it stays in history (issue 1577)

2026-10-26 19:47:53 +01:00

bounded.go

Builder and checker read tools read only the keys they need, in parallel, at most 1000 a call (issue 1827)

2026-10-26 00:39:08 +01:00

build_change.go

The check names a changed build module that invokes a verb no running build serves as one it cannot run (ADR 0614 §7; issue 774)

2026-11-03 23:26:08 +01:00

builds.go

A check failed on a build asks itself again once the build is done again, and a failed check never waits on builds (ADR 0603 §10)

2026-11-03 17:55:41 +01:00

case.go

Judge nothing and owe no status for a candidate outside the mesh (issue 774)

2026-10-30 18:12:33 +01:00

checker_test.go

Judge nothing and owe no status for a candidate outside the mesh (issue 774)

2026-10-30 18:12:33 +01:00

checker.go

A check failed on a build asks itself again once the build is done again, and a failed check never waits on builds (ADR 0603 §10)

2026-11-03 17:55:41 +01:00

composition_test.go

The check names a changed build module that invokes a verb no running build serves as one it cannot run (ADR 0614 §7; issue 774)

2026-11-03 23:26:08 +01:00

composition.go

mesh-delivery-checker: make a check's composition from every placed node's engine answer

2026-11-02 18:56:20 +01:00

digestform_test.go

Read a level's digest from mesh-sdk's list form, so kept verdicts hold for a check whose end names a package like token (issue 1930)

2026-10-23 23:37:49 +02:00

doc.go

Keep a passing package's verdict once under its digest, so a second check can take it (issue 1287)

2026-10-21 21:02:54 +02:00

engines_test.go

The checker decides a node the sandbox did not judge by the contract's field (composer.Machine.NotJudged, verdict not-judged) and names it with the composer's words, never by a phrase in its reason (ADR 0593 §9; the prepare's seams finding on "not judged")

2026-11-03 16:44:47 +01:00

engines.go

The checker decides a node the sandbox did not judge by the contract's field (composer.Machine.NotJudged, verdict not-judged) and names it with the composer's words, never by a phrase in its reason (ADR 0593 §9; the prepare's seams finding on "not judged")

2026-11-03 16:44:47 +01:00

every_failure_test.go

mesh-delivery-checker: a check runs every member, level and the composition to its end and names every failure

2026-11-02 18:56:19 +01:00

examiner_test.go

The check's cycle refusal meets no verb edge on a cycle and no package edge, and still refuses provisions and bases (ADR 0614 §3, §6; issue 774)

2026-11-03 23:26:08 +01:00

failure_words_test.go

The checker pins the SDK of review round 1, and its hid-the-failure cases join the older build module's test (issue 1901)

2026-10-26 20:19:07 +01:00

fakes_test.go

Checker: delete a check's asks key at its end, so the state asks holds only the checks that run

2026-10-28 20:39:50 +01:00

gate_test.go

checker: a trunk move never ends a check; once it ended, its pass is carried and names the commits it was carried from, and a failed carry names the move (ADR 0548 §1, §5; issue 568 D2)

2026-10-26 11:30:46 +01:00

graph_cycle.go

The check's cycle refusal meets no verb edge on a cycle and no package edge, and still refuses provisions and bases (ADR 0614 §3, §6; issue 774)

2026-11-03 23:26:08 +01:00

heard.go

Judge each pull request's check as one ask on the build seats' check stream, a re-judge on recheck, so the checker chooses no node and a lost node's check is redelivered, not moved (issue 1887 A5a, ADR 0525 §1, §3, ADR 0536 §4)

2026-10-23 16:05:55 +02:00

judge.go

The check names a changed build module that invokes a verb no running build serves as one it cannot run (ADR 0614 §7; issue 774)

2026-11-03 23:26:08 +01:00

judged_test.go

Place the change's own repository beside it at its trunk, so a shrink-only list test compares with the trunk's copy at $MESH_CHECK_BESIDE/<name> (issue 1887 A12, ADR 0529 §2)

2026-10-23 15:35:37 +02:00

kept_test.go

Checker: a package with skipped tests is withheld from the kept verdicts, not the whole result (issue 890)

2026-10-26 12:29:14 +01:00

kept.go

Checker: a package with skipped tests is withheld from the kept verdicts, not the whole result (issue 890)

2026-10-26 12:29:14 +01:00

line_test.go

mesh-delivery-checker: the line test holds ADR 0591's case of a first failure longer than the forge's limit

2026-11-02 18:56:19 +01:00

line.go

mesh-delivery-checker: make a check's composition from every placed node's engine answer

2026-11-02 18:56:20 +01:00

lostask_test.go

Tests wait on events or the clock they are given, never on milliseconds a loaded machine outlasts

2026-11-02 23:04:44 +01:00

lostask.go

Builder owns the step runner; a build's imports reach its done key and log

2026-11-02 18:29:56 +01:00

manifests_judge.go

Answer review round 1: fresh is only what a take-in newly wrote, a merge keeps the verdict, the check compares with the trunk (ADR 0578, 0579)

2026-11-01 03:12:09 +01:00

package_cause_test.go

The checker pins the SDK of review round 1, and its hid-the-failure cases join the older build module's test (issue 1901)

2026-10-26 20:19:07 +01:00

pins_test.go

Place mesh-networking beside a node-engine check, so route-proxy's proofs of a composition are judged once this release runs

2026-11-02 20:40:01 +01:00

pins.go

Build checks against the group's package heads, not go.mod pins

2026-11-01 02:41:22 +01:00

preview_named_test.go

Build checks against the group's package heads, not go.mod pins

2026-11-01 02:41:22 +01:00

preview.go

Build checks against the group's package heads, not go.mod pins

2026-11-01 02:41:22 +01:00

rank_test.go

checker_status reads the node-engine at its running commit, as the checker's decision does, so it stops listing every candidate as waiting for a trunk move (issue 568)

2026-10-26 13:25:18 +01:00

read_test.go

checker_status names the builds a running check waits on (ADR 0603 §10)

2026-11-03 17:51:09 +01:00

read.go

A check failed on a build asks itself again once the build is done again, and a failed check never waits on builds (ADR 0603 §10)

2026-11-03 17:55:41 +01:00

results.go

Build checks against the group's package heads, not go.mod pins

2026-11-01 02:41:22 +01:00

store.go

Judge nothing and owe no status for a candidate outside the mesh (issue 774)

2026-10-30 18:12:33 +01:00

try_test.go

mesh-delivery-checker: a check runs every member, level and the composition to its end and names every failure

2026-11-02 18:56:19 +01:00

try.go

Builder owns the step runner; a build's imports reach its done key and log

2026-11-02 18:29:56 +01:00

turns.go

checker: claim no check of a repository an approved merge holds a turn on, and claim it when the turn goes (ADR 0548 §3; issue 568 D1)

2026-10-26 11:29:25 +01:00