Creates a feature branch

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

Identifies the missing dependency

Stops before making changes

Provides the install command

Explains why gh-aw is needed

Invites re-invocation

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 at least two uncovered decision branches

Writes new scenario directories

Criteria files follow the weighted_checklist format prescribed by the tile

Criteria weights sum to 100 and are not equally distributed

New task.md files pass the no-bleeding check

New criteria don't leak tile internals

Failure descriptions are specific

At least one new scenario exercises a negative case

Coverage analysis justifies each gap

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 `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

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

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

Publish CI verification

Final summary includes merged PR URL

Graceful failure on unmet preconditions

No hardcoded PR, owner, or repo 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