scenario-a bleeding detected

scenario-a bleeding fixed

scenario-a leaking detected

scenario-a leaking fixed

scenario-b vague messages detected

scenario-b vague messages fixed

scenario-b misaligned criteria detected

scenario-b misaligned criteria fixed

scenario-c deleted

audit report produced

Uses GraphQL `requestReviews` mutation

Inline comment explains why REST doesn't work

Pinned bot ID with fallback to dynamic discovery

Resolves the PR's GraphQL node ID

Verifies the review request was registered

Feature-branch guard

PR title follows conventional-commits format

PR body structure

Pre-push readiness checks

No hardcoded inputs in the script body

CI failure: fix required

Applies the reasonable suggestion

Declines the over-engineered suggestion

All three threads get replies

Accept reply uses the `Fixed in <sha>` format

Decline reply uses the `Declining — <reason>` format

Decline reply cites a verifiable reference

Fixes pushed to the same branch

No dangling threads before merge

Patch: no manual manifest update

Patch: explains CI auto-bump

Minor: manifest bumped to `1.5.0`

Major: manifest bumped to `2.0.0`

Major: flags breaking-change impact for downstream

Release sequencing: patch first, major last

Readiness gate: tests + linter

Runbook covers all three changes separately

names canonical cause

prescribes rewrite-criteria

rejects fix-task and retire

replacement criteria are tile-specific

names canonical cause

prescribes fix-task

preserves the criterion

task rewrite strips technique, keeps situation

names canonical cause

prescribes retire

reasoning cites baseline equivalence

no spurious fix-task or rewrite-criteria

Uses `gh pr checks` with structured output

Uses `gh api .../pulls/<N>/reviews` for review state

Uses `gh api .../pulls/<N>/comments` for inline comments

Does NOT use `/issues/<N>/comments`

Retrieves per-reviewer state distinctly

No hardcoded PR, owner, or repo in the script body

Waits for CI to finish before surfacing state

Surfaces CI state in the summary

Surfaces review states in the summary

Surfaces inline comment content or count

Surfaces merge-readiness state for conflict diagnosis

Diagnoses why the fork PR is not reviewed

Brings the branch into the base repo

Preserves the contributor's commits unchanged

Opens a same-repo PR from the adopted branch

Leaves the original fork PR open

Links the adopted PR back to the original

Does not fabricate an Author-Model declaration

Identifies the PR as originating in the repository itself

Recognizes the reviewer already covers it

Creates no branch and pushes nothing

Opens no duplicate PR

Reports the PR's status

Creates a feature branch

Plan populates .github/workflows with both source + lock pairs

Commits both sources and both locks

Pushes and opens a PR

PR body lists OPENAI_API_KEY

PR body lists ANTHROPIC_API_KEY

PR body lists TESSL_TOKEN

Does not merge

Does not bypass pre-commit hooks

Explains the cross-family reviewer rationale

Rule file frontmatter declares alwaysApply: false

Rule file frontmatter declares applyTo with glob patterns

applyTo value combines globs with a natural-language clause

plugin.json rules array includes the new rule path

Rule body has H1 title matching the filename concept

Existing rules and manifest entries are preserved unchanged

Rule file frontmatter flipped to alwaysApply: false

Rule file frontmatter gains applyTo with glob patterns

applyTo value combines globs with a natural-language clause

plugin.json carries no per-rule config and its rules array is intact

Rule body content is preserved unchanged

Existing rule (commit-conventions) is preserved unchanged

Rule file frontmatter declares alwaysApply: true

Rule file frontmatter declares no scoping fields

plugin.json rules array includes the new rule path

Rule body covers the stdlib-first practice

Rule body covers the dependency-pinning practice

Existing rules and manifest entries are preserved unchanged

Detects existing workflow

Refuses to overwrite

No downstream actions after refusal

Explains why the guard matters

Offers an actionable next step

Preserves existing file

identifies suite as clean

does not fabricate diagnoses

recognizes negative-case acceptability

output is appropriately minimal

Merge strategy uses `gh pr merge --merge`

Merge includes `--delete-branch`

Fast-forward-only pull after merge

Safe local-branch delete with `git branch -d`

Stale remote-tracking refs pruned

Pre-merge CI gate

Pre-merge review gate

Verifies merge landed on main

Pre-merge registry baseline captured

SHA-bound publish-run resolution

Watch publish run to terminal state

Conjunction check: run-success AND registry-advance AND moderation-clear

Final summary includes merged PR URL

Graceful failure on unmet preconditions

No hardcoded PR, owner, or repo in the script body

Runs the migration mechanics

Renames the tessl tile CLI alias

Keeps the v1/tiles API route

Keeps code identifiers

Keeps the legacy tile.json reference

Distinguishes prose from contract rather than blanket-replacing