Conversation
…ode is made of Two cheap questions, both answered wrong across this repository. WHAT DID IT REACH? coq-proofs.yml has failed 62 of 62 at `opam update` -- step 2 of 5, and step 3 is the one that calls `coqc`. Thirteen files, never compiled by anything. brain-seal-refresh.yml has failed 8 of 8 across five months because its last step is a `git push` to master and this repository's own ruleset answers GH013. Neither needs a fix to what it checks; both stop before the check. WHAT IS THE EXIT CODE MADE OF? l1-traceability.yml's L3 PURITY step, inside one of the four workflows that can block a merge, reads `$BASE_BRANCH` in a fresh shell where it is empty, and tests `a | b | head`, which returns head's status. The warning branch was unconditional and the green branch has never executed. The section also records why these survive: `::warning::` never fails a run, so a fabricated verdict inside a required workflow lasts indefinitely; `--min-runs 50` hid four of six dead gates including the structurally impossible one; and `state=="active"` is the API's word, not the repository's -- 61 registrations against 48 files. And one instrument note: Apple's `grep -P` does not behave like GNU's, so reproducing a runner's `grep -P` step on macOS measures the wrong thing. Substitute a matcher you control, prove the branching, keep the runner's dialect in the workflow. Refs #2914 Refs #2917 Refs #2919
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
gHashTag
enabled auto-merge (squash)
August 29, 2026 23:33
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
1 similar comment
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-08-29 23:37:26 UTC
Summary
Seal Status
|
Contributor
PR DashboardGenerated at: 2026-08-29 23:38:37 UTC
Summary
Seal Status
|
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
1 participant
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.
Two cheap questions, both answered wrong here.
What did the workflow reach?
coq-proofs.ymlopam update, step 2 of 5 — step 3 callscoqcbrain-seal-refresh.ymlgit pushto master, answeredGH013by this repo's rulesetNeither needs a fix to what it checks. Reading only the last line of the log says
"Coq proofs are broken"; the truth is that no Coq proof has ever been read.
What is the exit code made of?
l1-traceability.yml's L3 PURITY step, insideone of the four workflows that can block a merge:
$BASE_BRANCHis computed in the two steps above; eachrun:is a freshshell, and this one lost the
env:block →git diff origin/..HEAD→fatalif a | b | headreturns head's status → the warning branch isunconditional and the green branch has never executed
Issues: #2914, #2915, #2917, #2919, #2920.
Why they survive
::warning::never fails a run, so a fabricated verdict inside a requiredworkflow lasts indefinitely.
--min-runs 50hid four of six, including the one that cannot work byconstruction. Few runs is not few enough to be safe.
state=="active"is the API's word: 61 registrations against 48 files, andone phantom carries 31 failures — more than four of the six real ones.
grep -Pis not GNU's, so reproducing a runner's grep step onmacOS measures the wrong thing.
Refs #2914
Refs #2917
Refs #2919