docs(rules): extend gh-json-fields with CI check fields and W23 evidence#1469
Draft
laurigates wants to merge 1 commit into
Draft
docs(rules): extend gh-json-fields with CI check fields and W23 evidence#1469laurigates wants to merge 1 commit into
laurigates wants to merge 1 commit into
Conversation
W23 friction analysis (2026-06-01, ending 2026-W23) surfaced 8 new `Unknown JSON field` events across 8 distinct sessions, breaking the zero-hold from W21/W22. Fields tried: | Field | Sessions | |---|---| | `merged` on PR | 4 | | `conclusion` on PR | 2 | | `checksStatus` on PR | 1 | | `issueType` on issue | 1 | `merged` is documented in the existing rule, but `conclusion` and `checksStatus` (both CI-check fields that live on `statusCheckRollup`, not flat on the PR object) are new and were not covered. Extending the rule with a dedicated "CI check fields" section, including: - The correct `statusCheckRollup` recipes for "are all checks passing", "which checks failed", and "conclusion of one specific check" - The full conclusion / status value enumerations - A pointer to the simpler `gh pr checks --required` exit-code path when per-check detail isn't needed Also refreshed the "The merged mistake" preamble to acknowledge the W23 reappearance alongside the original W20 evidence. Evidence: ~/.claude/rules/friction/2026-W23-frictions.md Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
laurigates
added
enhancement
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.
Summary
W23 friction analysis (week ending 2026-06-01) surfaced 8
Unknown JSON fieldevents across 8 distinct sessions — breaking the zero-hold the rule maintained through W21 and W22. Four of those events tried--json mergedagain (already documented), but four tried fields the rule did not cover:mergedon PRstate == "MERGED"ormergedAt != null(documented, recurring)conclusionon PRstatusCheckRollup[].conclusionchecksStatuson PRstatusCheckRollup[]issueTypeon issueissueType.name(documented, but tried as flat field)The new "CI check fields" section adds
statusCheckRolluprecipes for the common questions (are all checks passing, which failed, conclusion of one specific check), the full conclusion / status value enums, and a pointer togh pr checks --requiredfor the lighter exit-code-only path.This is a pure rule-text extension — no code change, no test infrastructure to touch (
regression-testing.mdrequires a script check only for bug fixes).Evidence
Findings file:
~/.claude/rules/friction/2026-W23-frictions.md(user-global, not in this repo)Key drift:
Test plan
gh pr view --helpoutputconclusion,checksStatus,issueTypeas flat) drop to zeromergedrecurrence rate trajectory will indicate whether project-local rule placement is insufficient (next-week decision: promote to user-global~/.claude/rules/)Decision context
PR opened by the
reduce-frictionscheduled task on behalf offeedback-plugin:friction-learner. Per the GitHub Metadata Hygiene rule, the PR author (laurigates) is not added as reviewer because GitHub rejects self-review with HTTP 422.🤖 Generated with Claude Code