feat: update docs for token efficient usage

.gitea/ISSUE_TEMPLATE/feature.yml

@@ -1,70 +0,0 @@
-name: "Feature"
-about: "New capability or enhancement"
-title: "[Feature]: "
-labels:
-  - "type/feature"
-  - "status/backlog"
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Use this for a new feature or enhancement. Keep scope tight and include clear acceptance criteria.
-
-  - type: textarea
-    id: problem
-    attributes:
-      label: "Problem / user need"
-      description: "What problem are we solving, and for whom?"
-      placeholder: "As a user, I want..., so that..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: solution
-    attributes:
-      label: "Proposed solution"
-      description: "Describe the expected behavior at a high level."
-      placeholder: "When the user does X, the system should..."
-    validations:
-      required: true
-
-  - type: textarea
-    id: non_goals
-    attributes:
-      label: "Non-goals / out of scope"
-      description: "What are we explicitly not doing in this feature?"
-      placeholder: "- Not doing...\n- Not doing..."
-    validations:
-      required: false
-
-  - type: textarea
-    id: acceptance
-    attributes:
-      label: "Acceptance criteria"
-      description: "Concrete checks for ‘done’. Prefer bullets and testable statements."
-      placeholder: |
-        - [ ] ...
-        - [ ] ...
-        - [ ] ...
-    validations:
-      required: true
-
-  - type: textarea
-    id: notes
-    attributes:
-      label: "Implementation notes (optional)"
-      description: "Links, APIs, file paths, edge cases."
-    validations:
-      required: false
-
-  - type: textarea
-    id: test_plan
-    attributes:
-      label: "Test plan"
-      description: "How will we verify? Include commands or steps."
-      placeholder: |
-        - Unit:
-        - Integration:
-        - Manual:
-    validations:
-      required: true