chore: Zephyr-standard issue/PR templates, template chooser config

- Enhanced bug report: environment details, ARB model section, impact checkboxes
- Enhanced feature request: affected components, requirements impact
- Enhanced PR template: type of change, full governance checklist
- Added config.yml to disable blank issues, add contact links

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: tbitcs

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,26 +1,48 @@
 ---
 name: Bug Report
-about: Report a bug in arbiter
+about: Report a bug in Arbiter
 title: "[BUG] "
 labels: bug
 assignees: ''
 ---
 
-## Description
-A clear description of the bug.
+## Describe the Bug
+A clear and concise description of the bug.
 
-## Steps to Reproduce
+## To Reproduce
+Steps to reproduce the behavior:
 1.
 2.
 3.
 
 ## Expected Behavior
+What you expected to happen.
 
 ## Actual Behavior
+What actually happened. Include logs, error output, or screenshots.
 
 ## Environment
-- Zephyr version:
-- Board/target:
-- arbiter version:
-- Python version:
-- OS:
+- **Zephyr version**: (e.g., v4.4.0)
+- **Board/target**: (e.g., native_sim, nrf52840dk)
+- **Arbiter version**: (e.g., v0.1.0 or commit hash)
+- **Python version**: (e.g., 3.12.0)
+- **OS**: (e.g., Windows 11, Ubuntu 24.04)
+- **Toolchain**: (e.g., Zephyr SDK 0.16.8, GCC 12.3)
+
+## ARB Model (if applicable)
+```yaml
+# Paste relevant model snippet
+```
+
+## Logs
+```
+# Paste relevant build or runtime output
+```
+
+## Impact
+- [ ] Build failure
+- [ ] Runtime crash/hang
+- [ ] Incorrect evaluation result
+- [ ] Safety-relevant (wrong mode/action)
+- [ ] Compiler (arbiterc) error
+- [ ] Documentation issue

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Zephyr Project
+    url: https://docs.zephyrproject.org/
+    about: Zephyr RTOS documentation
+  - name: Arbiter Documentation
+    url: https://github.com/BitConcepts/arbiter/tree/main/doc
+    about: Arbiter user documentation and API reference

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,18 +1,31 @@
 ---
 name: Feature Request
-about: Suggest a feature for arbiter
+about: Suggest a feature for Arbiter
 title: "[FEATURE] "
 labels: enhancement
 assignees: ''
 ---
 
 ## Problem Statement
-What problem does this feature solve?
+What problem does this feature solve? What use case is not currently supported?
 
 ## Proposed Solution
-Describe the desired behavior.
+Describe the desired behavior and how it would work.
 
 ## Alternatives Considered
-What other approaches were considered?
+What other approaches were considered and why were they rejected?
+
+## Affected Components
+- [ ] C runtime engine (`lib/`)
+- [ ] Python compiler (`python/arbiter/`)
+- [ ] ARB model format / schema
+- [ ] Zephyr subsystem (`subsys/arbiter/`)
+- [ ] Samples
+- [ ] Documentation
+- [ ] Safety artifacts
+
+## Requirements Impact
+Does this require new REQ-* entries in `docs/REQUIREMENTS.md`?
 
 ## Additional Context
+Any other context, diagrams, or references.

.github/pull_request_template.md

@@ -1,10 +1,27 @@
 ## Description
-Brief description of changes.
+Brief description of changes and motivation.
+
+Fixes # (issue number)
+
+## Type of Change
+- [ ] Bug fix (non-breaking)
+- [ ] New feature (non-breaking)
+- [ ] Breaking change
+- [ ] Documentation update
+- [ ] Safety-relevant change
+
+## Testing
+Describe tests run and results.
 
 ## Checklist
-- [ ] SPDX license headers on all new files
-- [ ] Tests added or updated
-- [ ] Documentation updated
-- [ ] Python tests pass (`pytest tests/python`)
+- [ ] SPDX license headers on all new files (`SPDX-License-Identifier: MIT`)
+- [ ] C code follows Zephyr coding style (tabs, K&R braces)
+- [ ] Python code passes `ruff check python/` and `mypy python/arbiter/`
+- [ ] Tests added or updated and passing (`pytest tests/python -v`)
+- [ ] Documentation updated (README, doc/, safety/ if applicable)
+- [ ] Requirements updated (`docs/REQUIREMENTS.md`) if new functionality
+- [ ] Test coverage updated (`docs/TESTS.md`) for new requirements
+- [ ] ARB models validate (`arbiterc validate --strict`)
 - [ ] No new warnings
-- [ ] Follows Zephyr coding style (C) / PEP 8 (Python)
+- [ ] Commit messages follow conventional commits format
+- [ ] Safety artifacts updated if safety-relevant (`safety/`)