docs(skill): 434-435 -- the pipeline rule is about the last command, and a verification is dated - #3012
Merged
Conversation
…and a verification is dated
434. Section 428 named `$?`. The trap fired again through `&&`:
git apply --check "$patch" | head -3 && echo " APPLIES"
printed APPLIES for two patches that do not apply, because `head` succeeded. The
real answer -- `error: bootstrap/stage0/FROZEN_HASH: patch does not apply` --
went past on the piped line. `$?` was never the subject: `&&`, `||`, `if`,
`while`, `until` and `set -e` all read the LAST command of a pipeline. A command
whose exit code you care about does not go in a pipeline.
435. I published that two externally-authored patches apply cleanly and their
FROZEN_HASH is valid, hedged correctly that any edit to compiler.rs would end
that, and then ended it myself four hours later by merging #3005 -- which
rewrote the seal from fd842146… to 1b52250f…. A hedge moves the work to a reader
who may never come. Name the commit rather than the branch, and when you merge
something touching the same files, go back and say so: you are the one person
holding both facts at once.
The tell was a review agent reporting that the brief's premise -- "compiler.rs is
byte-identical between X and master" -- had expired during its own run.
`tri skill check`: 399 sections, no number used twice.
Refs #2988, #3005
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
PR DashboardGenerated at: 2026-09-03 08:51:23 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 sections, both from walking into traps this page already records.
434 — the pipeline rule is about the LAST command, not about
$?. Section 428 named$?. This time it fired through&&:git apply --check "$patch" | head -3 && echo APPLIESprinted APPLIES for two patches that do not apply, becauseheadsucceeded. The real answer went past on the piped line.&&,||,if,while,untilandset -eall read the last command of a pipeline — naming$?made it look like a caution about one variable when it is a property of pipelines.435 — a verification of applicability is dated, and you are the likeliest person to expire it. I published that two externally-authored patches apply cleanly and their
FROZEN_HASHis valid, hedged correctly that any edit tocompiler.rswould end that — then ended it myself four hours later by merging #3005, which rewrote the seal. The tell was a review agent reporting that the brief's premise had expired during its own run.tri skill check: 399 sections, no number used twice.Refs #2988, #3005
🤖 Generated with Claude Code