merge: 合併 develop（統一 wiki hash 規則）到 feat/ask-question-record-intent

同時保留兩邊變更：develop 的共用 wiki hash 規則說明，與本分支的意圖欄讀寫規則。
README.md 與 skills/ask/SKILL.md 的衝突段落合併成單一句子，不遺漏任一邊的規則。

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

skills/ask/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: ask
-description: Decision-tree questioning until no doubt remains. Check wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-ask answered questions. Every option must state its impact scope. After each answer, save the record back to the wiki. Use whenever a jsc skill needs user input; skip recording when no {owner}/{repo} is known.
+description: Decision-tree questioning until no doubt remains. Check wiki QUESTION_CONTENTS and QUESTION_{HASH} first and never re-ask answered questions. Compute HASH with the shared 8-character wiki hash rule. Every option must state its impact scope. After each answer, save the record back to the wiki. Use whenever a jsc skill needs user input; skip recording when no {owner}/{repo} is known.
 ---
 
 # ask — decision-tree questioning
@@ -10,7 +10,7 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
 ## Before asking
 
 1. Confirm the repository name `{owner}/{repo}` of the current work. Without one, skip steps 2 and 3: ask directly but do NOT record.
-2. Compute `HASH`: `printf '%s' "{owner}/{repo}" | sha1sum | cut -c1-8 | tr a-f A-F`.
+2. Compute `HASH` with the shared wiki hash rule: 8 characters, uppercase hex, and if the first character would be `0-9`, `A`, `B`, or `C`, replace it with `H` and keep the total length at 8.
 3. Read `QUESTION_CONTENTS` and `QUESTION_{HASH}` via `jsc-gitea:wiki`. Never re-ask a question already answered in the record; use the recorded answer directly. When reusing an answer, read the section's intent to judge whether the answer fits the current situation and whether it extends to similar unrecorded decisions. If the intent differs from the current situation, ask again instead of forcing the old answer.
 
 ## Questioning rules