Merge pull request 'feat/change-requests/pr-reporting' (#14) from feat/change-requests/pr-reporting into feat/change-requests/main

Reviewed-on: #14

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills",
   "author": {

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills"
 }

README.md

@@ -50,7 +50,7 @@ Marketplace 統一為 `jsc`（https://gitea.jsc.idv.tw/plugins/meta.git），安
 
 ### `pr`
 
-先認可所有變更，再依階梯命名目標分支、push、以範本描述建立 Gitea PR。基底分支由 `base-branch.sh --derive` 從分支名推出上一階；呼叫方傳入的基底與推導結果不同，就當成越級擋下並說明正確階梯，不會悄悄改目標。分支名只允許 ASCII：類型取 commit 優先度最高者，功能與標題先翻譯成英文短語再 slug 化。分支已有開啟中的 PR 時不重開，改成比對標題、描述、前置 PR 依賴三項，只有不一樣的那幾項才送出 API 呼叫。
+先認可所有變更，再依階梯命名目標分支、push、以範本描述建立 Gitea PR。基底分支由 `base-branch.sh --derive` 從分支名推出上一階；呼叫方傳入的基底與推導結果不同，就當成越級擋下並說明正確階梯，不會悄悄改目標。分支名只允許 ASCII：類型取 commit 優先度最高者，功能與標題先翻譯成英文短語再 slug 化。分支已有開啟中的 PR 時不重開，改成比對標題、描述、前置 PR 依賴三項，只有不一樣的那幾項才送出 API 呼叫。收尾回報使用 `jsc-meta/references/pr-report.md` 的 PR 資訊表格。
 
 <!-- JSC-SKILLS:END -->
 

plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills/"
 }

skills/pr/SKILL.md

@@ -46,7 +46,8 @@ Every PR targets the next rung up. Skipping a rung is forbidden.
    - The dependency differs → run `pr-depend` as in step 8.
    - All three match → change nothing. Every needless edit notifies every reviewer, so silence is the correct outcome here.
    - Done when each of the three items is reported as either matched or updated, and the number of API calls made equals the number of items that differed.
-10. Report the PR URL, the base branch, the target branch, which of the three calibration items were updated, and the feature trunk the script auto-created when step 3 printed that line. Done when the report names all of them.
+10. If this run follows PR comment fixes and the caller supplied handled comment ids, reply to each comment now with `jsc-gitea/tools/gitea.sh comment-reply`. Rules: `jsc-meta/references/pr-report.md`. Done when every handled comment has a reply URL, or a reported reply failure reason.
+11. Report the PR with the table format in `jsc-meta/references/pr-report.md`, then report the base branch, the target branch, which of the three calibration items were updated, and the feature trunk the script auto-created when step 3 printed that line. Done when the report includes the PR table columns `{owner}/{repo}`, PR number, PR URL and PR summary, and names all branch and calibration details.
 
 ## Rules