feat(ask): 意圖欄供 AI 判斷使用者選擇動機並決定舊答案適用性

What：
補上意圖欄的讀取端行為。SKILL.md「Before asking」第 3 步要求 AI 取用舊答案時同時讀該節意圖，判斷答案是否適用當下情境、可否延伸到類似決策；意圖不符就重新詢問。「After asking」第 2 步點明意圖是給後續讀者判斷選擇動機用。範本佔位說明與 README 的 ask 段落同步。

Why：
上一輪只加了寫入端的意圖欄。使用者補充：意圖欄的目的是讓 AI 讀紀錄時能判斷使用者如此選擇的動機。缺了讀取端規則，AI 仍可能把舊答案硬套到情境不同的新決策上。

How：
SKILL.md 第 3 步句尾補兩句英文讀取規則，第 2 步「After asking」補半句呼應；templates/question-record.md 意圖欄佔位說明點出「供 AI 判斷選擇動機與答案適用性」；README.md ask 段落加一句「AI 取用舊答案時依意圖判斷適用性，意圖不符就重新問」。版本不變（0.0.2 尚未發布，同一條 PR）。

Who：
使用者於 jsc-ask 技能維護時提出；影響所有透過 jsc-ask:ask 取用舊答案的 jsc 技能。

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

README.md

@@ -24,7 +24,7 @@ Marketplace 統一為 `jsc`（https://gitea.jsc.idv.tw/plugins/jsc.git），安
 
 ### `ask`
 
-決策樹問詢：一題一個決策點、選項標明影響範圍、問到沒有疑慮為止。問前查 `QUESTION_CONTENTS` 與 `QUESTION_{HASH}`，已有答案不再問；問後套範本寫回 wiki，每節開頭記錄使用者意圖（沒有存取庫名稱就不紀錄）。
+決策樹問詢：一題一個決策點、選項標明影響範圍、問到沒有疑慮為止。問前查 `QUESTION_CONTENTS` 與 `QUESTION_{HASH}`，已有答案不再問；AI 取用舊答案時依意圖判斷適用性，意圖不符就重新問。問後套範本寫回 wiki，每節開頭記錄使用者意圖（沒有存取庫名稱就不紀錄）。
 
 <!-- JSC-SKILLS:END -->
 

skills/ask/SKILL.md

@@ -11,7 +11,7 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
 
 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`.
-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.
+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
 
@@ -24,6 +24,6 @@ Every jsc skill that needs user input MUST follow the rules in this skill.
 ## After asking
 
 1. Without a repository name, do not record; stop here.
-2. After each Q&A round, apply `templates/question-record.md` to create or update `QUESTION_{HASH}` (append new entries; never overwrite old records). Each section MUST open with the user's original intent (why this questioning round happened), per the template.
+2. After each Q&A round, apply `templates/question-record.md` to create or update `QUESTION_{HASH}` (append new entries; never overwrite old records). Each section MUST open with the user's original intent (why this questioning round happened), per the template; it lets a later reader judge why the user chose as they did and whether the answer still applies.
 3. Apply `templates/question-contents.md` to create or update `QUESTION_CONTENTS` (add the repository row if missing; otherwise refresh its last-updated time).
 4. The wiki writes above MUST run as a sub agent; the main agent only confirms the write succeeded.

templates/question-record.md

@@ -4,7 +4,7 @@
 
 ## {yyyy-MM-dd HH:mm} {問詢主題}
 
-- **意圖**: {使用者的原始需求與目的，一句話}
+- **意圖**: {使用者的原始需求與目的，一句話，供 AI 判斷選擇動機與答案適用性}
 
 ### Q1: {問題}