refactor: update issue templates for clarity and conciseness

.github/ISSUE_TEMPLATE/bug_report.md

@@ -32,11 +32,9 @@ What happened instead?
 - Browser (if UI issue):
 - OS:
 
-## Relevant logs/errors
+## Relevant logs/errors (attach files)
 
-```text
-Paste error logs, stack traces, or API errors here.
-```
+Attach error logs, stack traces, or API error outputs as files/images. If needed, you can add a short summary here.
 
 ## Scope and impact
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -18,23 +18,13 @@ What do you want to happen?
 
 What alternatives did you evaluate?
 
-## Scope
-
-Which areas are affected?
-
-- [ ] API
-- [ ] Auth/access
-- [ ] Database
-- [ ] UI/UX
-- [ ] Docs
-- [ ] DevEx/Operations
-
 ## Acceptance criteria
 
 How will we know this is done?
 
-- [ ] Criterion 1
-- [ ] Criterion 2
+- [ ] User value: The proposed change solves the stated problem in an end-to-end user flow.
+- [ ] Security and access control: Existing authorization rules are preserved, and no sensitive data is exposed.
+- [ ] Verifiability: Completion is proven with test steps, reproducible evidence, or clear output/screenshots.
 
 ## Non-goals (optional)
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,14 +6,6 @@ Explain what changed in this PR.
 
 Explain the problem this PR solves.
 
-## Type of change
-
-- [ ] feat
-- [ ] fix
-- [ ] docs
-- [ ] refactor
-- [ ] chore
-- [ ] test
 
 ## Scope