skill: the population of events, after the predicate and the operand - #3321
Merged
Conversation
gHashTag
enabled auto-merge (squash)
September 5, 2026 18:17
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
Contributor
Contributor
PR DashboardGenerated at: 2026-09-05 18:18:05 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.
Closes #3320
Section 594 (592 was taken by a neighbour between my reading of the maximum and my write — renumbered in a follow-up commit).
Three defect classes in two days, in strict order of subtlety:
The third produced two defects every control missed, because a control tests the event you thought of: a push can be a deletion (#3309), and a commit can be a merge (#3319) — the barrier was silent on the one commit type conflict markers come from.
The method is enumeration, not cleverness: marker hooks that only
toucha file, one run per event, then read which files exist.Two hazards met while measuring, each with its fix:
git configinside a worktree writes to the shared config (it disabled the real hooks in all 148 worktrees for a few minutes), and a failedcddoes not stop a subshell (a probe ran its commits in my own tree).