skill: spool five lessons from pass 119 - #3361
Merged
Merged
Conversation
Written with `tri skill add` and left UNNUMBERED, deliberately. A branch that also runs `fold` picks its number against its own base and collides exactly like a direct append; folding belongs after the merge. The five: - A refusal recorded only in prose is invisible to the tool that advises against it. `gates unmeasured` printed `dispatch: NO` beside "add `workflow_dispatch:` first" for the workflow #3325 had just deliberately removed one from -- that is, it advised putting a dispatch back in front of `cargo publish` on a live registry. A two-state predicate over a three-state domain is the shape. - Two date fields render in two timezones. `%ad` and `%cd` each print in their OWN recorded offset, which made one commit read as a seven-hour clock skew. Compared as epochs: 0 of 20. The tell was that the date order ran against topology. - Assert that the edit moved, not that the anchor exists. Two scripted edits reported success and changed nothing; the second because `find()` returned -1, `s[-1:j]` is the empty string, and `replace("", new)` inserts at position 0. - A private target dir hides the binary from the hooks. `.githooks/pre-commit:52` probes `$ROOT/target/{debug,release}/tri`; with `CARGO_TARGET_DIR` elsewhere the commit silently does not form while the next push reports success. - A gate whose workflow is not a required context cannot block a merge. This one refutes a claim I had already published in #3332: replayed over twelve first-parent commits with the tool unchanged, exactly one fails, blessed nineteen minutes later. `tri skill check`: 556 sections, no number used twice. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
`Documented t27c subcommands exist` went red on this branch alone: dead `tri`
mentions rose 141 -> 142. The offender was mine, and it was a QUOTATION.
The lesson about stale binaries quoted the hook's own warning inside one code
span -- `target/debug/tri is older than cli/tri/src`. The gate extracts
`tri <word>` from code spans, so it read a subcommand `is`, which resolves on
none of the four surfaces. Correctly: the gate is right, the text was wrong.
Split into two spans, so the prose reads the same and the code spans name only
paths: `target/debug/tri` is older than `cli/tri/src`.
Measured rather than assumed, with both controls run first because the obvious
probe was itself broken -- `$B $sub --help` does not word-split in zsh, so both
mentions reported DEAD until the probe used `${=sub}`. With a must-resolve and a
must-not-resolve control behaving correctly, the two `tri` mentions my files
introduce (`tri census pin`, `tri gates unmeasured`) both resolve, and `tri is`
is gone. The ratchet returns to 141.
Not amended: the branch is pushed, and this repository never force-pushes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
PR DashboardGenerated at: 2026-09-06 05:37:04 UTC
Summary
Seal Status
|
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
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.
Refs #3236
Five lessons from pass 119, written with
tri skill addand left unnumbered on purpose. Abranch that also runs
foldpicks its number against its own base and collides exactly like adirect append; folding belongs after the merge.
gates unmeasuredprinteddispatch: NObeside "addworkflow_dispatch:first" for the workflow #3325 had just deliberately removed one froma=09-06 02:15 / c=09-05 19:15read as a 7-hour skew; as epochs, 0 of 20find()→ −1,s[-1:j]empty,replace("")inserts at 0.githooks/pre-commit:52probes$ROOT/target/{debug,release}/tri; commit silently does not form, push reports successThe last one refutes a claim I published myself in #3332 — that the hook had been failing for
every author since a workflow edit landed unblessed. It was one commit and nineteen minutes. The
PR body is corrected at source.
tri skill check: 556 sections across the tree, no number used twice.