test-report-from-issuelisted

# Test Report from GitHub Issue ## Ask first if not already provided 1. Tester name 2. Which GitHub issue (number or URL) If either is missing, ask the user — do not assume or default. ## Output language The report's language must match the language the user is writing in (e.g. reply in Traditional Chinese if the user is chatting in Traditional Chinese, English if they're chatting in English). Do not hardcode a language — pass localized label strings to the script (see step 4). ## Workflow 1. **Read the issue**: `gh issue view <issue_number> --json title,body,comments,url` If the target repo isn't obvious, check `git remote -v` first, or ask the user for `owner/repo`. 2. **Find the verification/test checklist** (a judgment task — read and decide yourself, don't hardcode keyword rules) - Look through the body and all comments for a checklist (`- [ ] ...` items), commonly under a heading like "Test Plan", "Checklist", "驗證項目", or "測試項目" - If there are multiple checklists, or it's unclear which one is the final version (e.g. a later comment revised the list), list the options for the user to pick — don't decide on your own - If no checklist exists at all, ask the user to provide the test items directly 3. **Confirm you have everything**: issue title, tester name, date (default today, format `YYYY/MM/DD`), the list of items, and the target language. 4. **Generate the document** (a deterministic step — call the script, don't han