hashiiiii-issueslisted

# Issue Conventions Use the same headings and order in every issue body. ## Locale Before you draft an issue, resolve its language: 1. If project instructions specify an issue language, use that language. 2. If project instructions do not specify a language, use the resolved `issues` key from the context. 3. If the context has no resolved keys, read the first existing locale file. 4. Use this file order: local, project, user, and bundled `LOCALE.default.md`. 5. Use `<absolute-git-dir>/rules-for-ai/LOCALE.md` for the local file. 6. Use `<repo>/.rules-for-ai/LOCALE.md` for the project file. 7. Use `${XDG_CONFIG_HOME:-${HOME:-}/.config}/rules-for-ai/LOCALE.md` for the user file. 8. If no locale file exists, use `en_US`. 9. Use the `issues` language for the issue title and body. Always write the section headings in English. Do not change the template structure. If `issues` is `ja_JP`, keep the English headings. Write the text below each heading in Japanese. ## When to Use - Before `gh issue create` - Before you edit an issue body - If the user asks you to draft an issue ## Issue Body Template Use these exact headings in this order: ```markdown ## Background ## Problem ## Scope ### In scope ### Out of scope ## Design ## Acceptance criteria ## Notes ``` ## Section Guide | Section | Purpose | |---------|---------| | Background | Explain the context, reason, and earlier decisions. | | Problem | Describe current defects or missing behavior. | | Scope / In scope | L