fix(templates): replace tf-kernel refs with TeleFuser, add roadmap template and config.yml

Author: lzx1413

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: Bug Report
-description: Create a report to help us improve tf-kernel
+description: Create a report to help us improve TeleFuser
 title: "[BUG] "
 labels: ["bug", "triage"]
 body:
@@ -24,10 +24,10 @@ body:
       label: To Reproduce
       description: Steps to reproduce the behavior
       placeholder: |
-        1. Install tf-kernel with 'pip install tf-kernel'
+        1. Install TeleFuser with 'pip install -e ".[dev]"'
         2. Run the following code:
         ```python
-        import tf_kernel
+        import telefuser
         # your code here
         ```
         3. See error
@@ -55,7 +55,7 @@ body:
         - PyTorch version: [e.g. 2.9.1]
         - CUDA version: [e.g. 12.4]
         - GPU: [e.g. NVIDIA A100, RTX 4090]
-        - tf-kernel version: [e.g. 0.1.0]
+        - TeleFuser version: [e.g. 0.1.0]
     validations:
       required: true
 

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: 📖 Documentation
+    url: https://github.com/lzx1413/TeleFuser/tree/main/docs/en
+    about: Check the documentation before opening an issue
+  - name: 💬 Discussions
+    url: https://github.com/lzx1413/TeleFuser/discussions
+    about: Ask questions, share ideas, and discuss with the community
+  - name: 🔒 Security Vulnerability
+    url: https://github.com/lzx1413/TeleFuser/security/advisories/new
+    about: Report security vulnerabilities privately through GitHub Security Advisories

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,5 +1,5 @@
 name: Feature Request
-description: Suggest an idea for tf-kernel
+description: Suggest an idea for TeleFuser
 title: "[FEATURE] "
 labels: ["enhancement", "triage"]
 body:
@@ -24,7 +24,7 @@ body:
       label: Describe the solution you'd like
       description: A clear and concise description of what you want to happen
       placeholder: |
-        I would like to see a new kernel that implements...
+        I would like to see a new pipeline/op that implements...
     validations:
       required: true
 
@@ -34,7 +34,7 @@ body:
       label: Describe alternatives you've considered
       description: A clear and concise description of any alternative solutions or features you've considered
       placeholder: |
-        I've considered using the existing XXX kernel, but it doesn't support...
+        I've considered using the existing XXX pipeline/op, but it doesn't support...
 
   - type: textarea
     id: context

.github/ISSUE_TEMPLATE/roadmap.yml

@@ -0,0 +1,91 @@
+name: Roadmap Item
+description: Propose a milestone or roadmap item for TeleFuser development
+title: "[ROADMAP] "
+labels: ["roadmap", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for contributing to the TeleFuser roadmap!
+        Use this template to propose major milestones, new model integrations,
+        or strategic development items.
+
+  - type: dropdown
+    id: category
+    attributes:
+      label: Category
+      description: Which area does this roadmap item belong to?
+      options:
+        - New Model Integration
+        - Performance Optimization
+        - Distributed Inference
+        - Kernel / Ops
+        - API & Service
+        - Documentation & Tooling
+        - Infrastructure & CI
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: goal
+    attributes:
+      label: Goal / Objective
+      description: What is the high-level goal of this roadmap item?
+      placeholder: |
+        Support Wan2.2 video generation with full pipeline integration,
+        including T2V, I2V, and FL2V modes with multi-GPU inference support.
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope & Deliverables
+      description: List the concrete deliverables and scope of work
+      placeholder: |
+        - Implement WanVideo pipeline for Wan2.2 (T2V, I2V, FL2V)
+        - Add Ulysses/Ring SP support for Wan2.2
+        - Add AdaTaylorCache integration
+        - Write unit tests and benchmarks
+        - Update documentation
+    validations:
+      required: true
+
+  - type: textarea
+    id: timeline
+    attributes:
+      label: Target Timeline
+      description: When should this be completed? (approximate milestone or date)
+      placeholder: |
+        Target: Q3 2026 / v0.2.0 release
+
+  - type: textarea
+    id: dependencies
+    attributes:
+      label: Dependencies & Prerequisites
+      description: What needs to be done first, or what external dependencies exist?
+      placeholder: |
+        - Requires PyTorch 2.6+ with CUDA 12.8+
+        - Depends on #XXX (Ulysses SP refactor)
+        - Blocked by upstream model release
+
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact & Priority
+      description: Why is this important? What is the expected impact?
+      placeholder: |
+        High priority — Wan2.2 is a widely requested model.
+        Expected throughput improvement: 2x over current Wan2.1 pipeline.
+        Enables long-video generation (>60s) with Ring Attention.
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: References, links, or other information
+      placeholder: |
+        - Related paper: https://arxiv.org/abs/XXXX
+        - Reference implementation: https://github.com/XXX
+        - Internal discussion thread: #XXX

.github/PULL_REQUEST_TEMPLATE.md

@@ -22,22 +22,23 @@
 
 ## Testing
 <!-- Describe the tests you ran and how to reproduce them -->
-- [ ] Unit tests pass (`make test`)
+- [ ] Unit tests pass (`pytest tests/`)
 - [ ] Manual testing performed
 - [ ] Benchmarks added/updated (if applicable)
 
 Test commands:
 ```bash
 # Add the commands used to test your changes
+pytest tests/
 ```
 
 ## Checklist
 <!-- Mark completed items with [x] -->
-- [ ] Code follows the project's coding standards (`make format`)
+- [ ] Code follows the project's coding standards (`ruff`)
 - [ ] Pre-commit hooks pass (`pre-commit run --all-files`)
-- [ ] All tests pass (`make test`)
+- [ ] All tests pass (`pytest tests/`)
 - [ ] New tests added for new functionality
-- [ ] Documentation updated (README, AGENTS.md, docstrings)
+- [ ] Documentation updated (README, CLAUDE.md, docstrings)
 - [ ] Commit messages are clear and descriptive
 - [ ] PR title follows the convention: `[TYPE] Brief description`