docs(templates): refine issue/pr templates for evidence patterns

ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,66 @@
+name: Bug
+description: Report a reproducible defect.
+title: "[bug] "
+labels: ["type:bug", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Repository and path, if known.
+      placeholder: "pccxai/repo-name, path/to/file"
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version or commit
+      description: Tag, branch, or commit where the defect was observed.
+      placeholder: "main at abc1234"
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed result
+      description: What happened?
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected result
+      description: What should have happened?
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Reproduction
+      description: Minimal commands, inputs, or steps.
+      placeholder: |
+        1. ...
+        2. ...
+        3. ...
+    validations:
+      required: true
+  - type: textarea
+    id: environment
+    attributes:
+      label: Environment
+      description: OS, toolchain versions, target board, and other relevant context.
+  - type: checkboxes
+    id: evidence_available
+    attributes:
+      label: Evidence available
+      description: Optional. Mark evidence that can be attached now or linked from the issue.
+      options:
+        - label: Failing command, log excerpt, or CI run
+        - label: Timing, synthesis, implementation, or utilization report
+        - label: Board run, serial log, screenshot, or host output
+        - label: Minimal reproducer, trace, or input fixture
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence links or excerpts
+      description: Optional. Link reports, checks, logs, screenshots, traces, or board records. Say "not available yet" if evidence is pending.

ISSUE_TEMPLATE/evidence.yml

@@ -0,0 +1,72 @@
+name: Evidence
+description: Submit or request evidence for repository claims, release gates, or review decisions.
+title: "[evidence] "
+labels: ["type:docs", "area:verification", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Repository where the claim, gate, or review decision lives.
+      placeholder: "pccxai/repo-name"
+    validations:
+      required: true
+  - type: textarea
+    id: subject
+    attributes:
+      label: Subject
+      description: Claim, release gate, or review decision that needs evidence.
+    validations:
+      required: true
+  - type: textarea
+    id: timing_state
+    attributes:
+      label: Timing state
+      description: Timing status, target clock, WNS/TNS, failing paths, report link, or "not run".
+      placeholder: |
+        Target clock:
+        WNS/TNS:
+        Report path or link:
+        Status:
+    validations:
+      required: true
+  - type: textarea
+    id: synthesis_state
+    attributes:
+      label: Synthesis and implementation state
+      description: Tool/version, commit, utilization, DSP/BRAM/LUT/FF counts, implementation status, report link, or "not run".
+      placeholder: |
+        Tool/version:
+        Commit:
+        Utilization:
+        Report path or link:
+        Status:
+    validations:
+      required: true
+  - type: textarea
+    id: board_state
+    attributes:
+      label: Board state
+      description: Target board, bitstream, host command, driver/app version, serial log, screenshot, output link, or "not run".
+      placeholder: |
+        Board:
+        Bitstream:
+        Host command:
+        Output path or link:
+        Status:
+    validations:
+      required: true
+  - type: textarea
+    id: evidence_links
+    attributes:
+      label: Evidence links
+      description: Logs, reports, checks, screenshots, commits, or board records. Say "missing" for each unavailable item.
+    validations:
+      required: true
+  - type: textarea
+    id: limits
+    attributes:
+      label: Limits
+      description: Known gaps, blocked inputs, unsupported scope, stale reports, or follow-up work.
+    validations:
+      required: true

ISSUE_TEMPLATE/feature.yml

@@ -0,0 +1,54 @@
+name: Feature
+description: Propose a scoped capability or repository change.
+title: "[feature] "
+labels: ["type:feature", "status:triage"]
+body:
+  - type: input
+    id: repository
+    attributes:
+      label: Repository
+      description: Target repository or repositories.
+      placeholder: "pccxai/repo-name"
+    validations:
+      required: true
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What concrete problem does this solve?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: Describe the smallest useful change.
+    validations:
+      required: true
+  - type: textarea
+    id: boundary
+    attributes:
+      label: Boundary
+      description: What is in scope, and what is explicitly out of scope?
+    validations:
+      required: true
+  - type: checkboxes
+    id: decision_required
+    attributes:
+      label: Decision required
+      description: Optional. Use a checked item when maintainer confirmation is needed before implementation. Copy the relevant [CONFIRM] line into the issue body or follow-up PR.
+      options:
+        - label: "[CONFIRM] Choose the architecture, data format, or policy before implementation."
+        - label: "[CONFIRM] Choose the parameter, limit, default value, or accounting baseline before implementation."
+        - label: "[CONFIRM] Choose the timing, synthesis, board, or release gate before implementation."
+        - label: No maintainer decision required; the proposal can proceed as scoped.
+  - type: textarea
+    id: evidence
+    attributes:
+      label: Evidence or references
+      description: Related issues, design notes, traces, logs, board records, or prior work.
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance checks
+      description: How should maintainers verify this is done?

PULL_REQUEST_TEMPLATE.md

@@ -1,34 +1,17 @@
-<!-- Keep the description tight; the diff itself is the source of truth. -->
-
 ## Summary
 
-<!-- What changed and why, in 1-3 sentences. -->
-
-## Type of change
-
-- [ ] Bug fix
-- [ ] New feature
-- [ ] Documentation
-- [ ] Refactor / cleanup
-- [ ] Build / CI / chore
+-
 
-## Verification
+## Evidence State
 
-<!-- How was this tested? Cite commands, links to CI runs, or screenshots. -->
+Evidence state:
 
-## Linked issues
+stacking on:
 
-<!-- Closes #..., relates to #..., or "(none)". -->
+## Review
 
-## Engineering checklist
-
-- [ ] Scope is small and bounded
-- [ ] Public interface or boundary is clear
-- [ ] Tests/smoke checks were run
+- [ ] Scope is bounded
+- [ ] Labels and linked issues are correct
+- [ ] Public wording is backed by evidence
 - [ ] No overclaim about production readiness, timing closure, KV260 inference, or stable ABI
-- [ ] No unrelated repo settings, release, tag, or visibility changes
-- [ ] Critical architecture assumptions are stated
-
-## Notes for reviewer
-
-<!-- Optional. Anything subtle that the diff does not show. -->
+- [ ] No unrelated settings, release, tag, or visibility changes