Streamline ppl-bugfix workflow: fix 5 cross-cutting issues

- Add fork remote discovery step to both harness and followup
  (replace <your_fork_remote> placeholder with concrete instructions)
- Remove redundant follow-up type from command dispatch — subagent
  discovers it from PR state via followup harness categorization table
- Fix Phase 0.1: remove fake REST API call, use integration test only
- Add no-coauthor rule to followup harness (was only in harness)
- Add --repo flag to gh pr checkout in followup for worktree context

Signed-off-by: Heng Qian <qianheng@amazon.com>

Author: qianheng-aws

.claude/commands/ppl-bugfix.md

@@ -86,8 +86,7 @@ Agent(
   name: "bugfix-<issue_number>",
   description: "PPL bugfix #<issue_number> followup",
   prompt: "Read .claude/harness/ppl-bugfix-followup.md and follow it.
-           PR: <pr_number> (<pr_url>), Issue: #<issue_number>
-           Follow-up type: <CI failure / review feedback / merge conflict>"
+           PR: <pr_number> (<pr_url>), Issue: #<issue_number>"
 )
 ```
 

.claude/harness/ppl-bugfix-followup.md

@@ -1,5 +1,9 @@
 # PPL Bugfix Follow-up
 
+## Rules
+
+- Do NOT add `Co-Authored-By` lines in commits — only DCO `Signed-off-by`
+
 ---
 
 ## Reconstruct Context
@@ -10,6 +14,11 @@ The follow-up agent runs in a fresh worktree. First checkout the PR branch, then
 # Checkout the PR branch in this worktree
 gh pr checkout <pr_number>
 
+# Resolve fork remote — the worktree may only have origin (upstream)
+git remote -v
+# If no fork remote exists, add it:
+git remote add fork https://github.com/<fork_owner>/sql.git
+
 # Load PR state — reviews, CI, mergeability
 gh pr view <pr_number> --json title,body,state,reviews,statusCheckRollup,mergeable
 gh pr checks <pr_number>
@@ -41,7 +50,7 @@ For each comment (human OR bot), **cross-check against the Decision Log first**:
 
 ```bash
 git add <files> && git commit -s -m "Address review feedback: <description>"
-git push -u <your_fork_remote> <branch_name>
+git push -u fork <branch_name>
 ```
 
 ## Clean Up Commit History
@@ -52,7 +61,7 @@ When you need to amend a commit (e.g. remove Co-Authored-By, reword message) and
 git checkout -B clean-branch origin/main
 git cherry-pick <fix_commit_sha>
 git commit --amend -s -m "<updated message>"
-git push <your_fork_remote> clean-branch:<pr_branch> --force-with-lease
+git push fork clean-branch:<pr_branch> --force-with-lease
 ```
 
 ## Handle CI Failures
@@ -71,7 +80,7 @@ gh run view <run_id> --log-failed         # Read logs
 git fetch origin && git merge origin/main  # Resolve conflicts
 ./gradlew spotlessApply && ./gradlew test && ./gradlew :integ-test:integTest  # Re-verify
 git commit -s -m "Resolve merge conflicts with main"
-git push -u <your_fork_remote> <branch_name>
+git push -u fork <branch_name>
 ```
 
 ## Mark Ready

.claude/harness/ppl-bugfix-harness.md

@@ -15,11 +15,7 @@ Read the issue title, description, and any reproduction steps before proceeding.
 ### 0.1 Reproduce the Bug
 
 ```bash
-# Minimal PPL query
-POST /_plugins/_ppl/_query
-{ "query": "<your PPL query here>" }
-
-# Or via integration test
+# Write a failing integration test, or run an existing one
 ./gradlew :integ-test:integTest -Dtests.class="*<TestClass>" -Dtests.method="<testMethod>"
 ```
 
@@ -237,9 +233,15 @@ git fetch origin && git merge origin/main
 # Always re-run tests after merge — even a trivial merge can introduce regressions
 ./gradlew test && ./gradlew :integ-test:integTest -Dtests.class="*<YourIT>"
 
-# Push to personal fork (NOT origin if it points to upstream)
-git remote -v  # confirm your fork remote
-git push -u <your_fork_remote> <branch_name>
+# Resolve fork remote — find or add it
+# 1. Check if a fork remote already exists (not opensearch-project/sql)
+git remote -v
+# 2. If only origin (upstream) exists, add the fork:
+git remote add fork https://github.com/<fork_owner>/sql.git
+# Use the git user name to infer the fork owner, or fall back to "qianheng-aws"
+
+# Push
+git push -u fork <branch_name>
 ```
 
 ### 3.3 Create Draft PR