add mineru server;modify mineru pdf reader

.github/issue_template/bug_report.yml

@@ -0,0 +1,43 @@
+name: 🐞 Bug report
+description: Submit Bug feedback
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for reporting the bug. Please fill in the following information to help us reproduce the issue.
+  - type: input
+    id: env
+    attributes:
+      label: Environment Information
+      description: System version / Browser / Runtime environment
+      placeholder: macOS 14.5, Chrome 118
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: Reproduction Steps
+      description: Write down step by step how to trigger this bug
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: What should happen ideally
+    validations:
+      required: true
+  - type: textarea
+    id: actual
+    attributes:
+      label: Actual Behavior
+      description: What actually happened
+    validations:
+      required: true
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots / Logs
+      description: Provide screenshots or logs (optional)

.github/issue_template/enhancement.yml

@@ -0,0 +1,24 @@
+name: ⚙️ Enhancement
+description: Propose optimization suggestions for existing features
+title: "[Enhancement]: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: current
+    attributes:
+      label: Current Behavior
+      description: How existing features currently work
+    validations:
+      required: true
+  - type: textarea
+    id: improved
+    attributes:
+      label: Improvement Suggestions
+      description: How you would like to improve it
+    validations:
+      required: true
+  - type: textarea
+    id: benefit
+    attributes:
+      label: Benefits of Improvement
+      description: Benefits after improvement

.github/issue_template/feature_request.yml

@@ -0,0 +1,28 @@
+name: ✨ Feature request
+description: Submit new feature requirements
+title: "[Feature]: "
+labels: ["feature"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Please describe the new feature you would like to add and its use cases.
+  - type: textarea
+    id: description
+    attributes:
+      label: Feature Description
+      description: Briefly describe what the feature does
+    validations:
+      required: true
+  - type: textarea
+    id: usecase
+    attributes:
+      label: Use Cases
+      description: How this feature will be used
+    validations:
+      required: true
+  - type: textarea
+    id: design
+    attributes:
+      label: Design Ideas / Technical Details
+      description: (Optional) Your thoughts on implementation approach

.github/issue_template/performance.yml

@@ -0,0 +1,22 @@
+name: 🚀 Performance issue
+description: Submit performance related issues or optimization suggestions
+title: "[Performance]: "
+labels: ["performance"]
+body:
+  - type: textarea
+    id: bottleneck
+    attributes:
+      label: Current Bottleneck
+      description: Describe the performance issue
+    validations:
+      required: true
+  - type: textarea
+    id: metrics
+    attributes:
+      label: Performance Metrics
+      description: Provide test data / benchmarks
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Optimization Suggestions
+      description: Your optimization ideas

.github/pull_request_template.md

@@ -0,0 +1,60 @@
+# Pull Request
+
+## Description
+Brief description of the changes
+
+## Type of Change
+- [ ] Feature addition
+- [ ] Bug fix
+- [ ] Performance optimization
+- [ ] Code refactoring
+- [ ] Documentation update
+- [ ] Testing related
+- [ ] Security fix
+
+## Impact Scope
+- [ ] User interface
+- [ ] API interface
+- [ ] Database
+- [ ] Configuration files
+- [ ] Dependencies
+
+## Priority
+- [ ] High - Release immediately
+- [ ] Medium - Next version
+- [ ] Low - Future version
+
+## Changes Made
+- [ ] Change 1
+- [ ] Change 2
+- [ ] Change 3
+
+## Testing
+- [ ] Unit tests pass
+- [ ] Integration tests pass
+- [ ] Manual testing completed
+- [ ] Performance testing (if applicable)
+
+## Documentation
+- [ ] Code comments added/updated
+- [ ] README updated (if applicable)
+- [ ] API documentation updated (if applicable)
+
+## Breaking Changes
+- [ ] No breaking changes
+- [ ] Breaking changes documented
+- [ ] Migration guide provided
+
+## Related Issues
+Closes #123, Related to #456
+
+## Additional Notes
+Any additional information or context
+
+---
+
+## Release Notes Points
+- User-visible changes
+- Configuration change instructions
+- Migration steps
+- Known issues 

.github/pull_request_template/README.md

@@ -0,0 +1,55 @@
+# Pull Request Templates
+
+This directory contains specialized PR templates for different types of changes. Choose the appropriate template based on your change type.
+
+## Available Templates
+
+### 🚀 [Feature](feature.md)
+Use this template when adding new functionality or features to the project.
+
+### 🐛 [Bug Fix](bugfix.md)
+Use this template when fixing bugs or issues in the existing codebase.
+
+### ⚡ [Performance](performance.md)
+Use this template when optimizing performance or improving efficiency.
+
+### 🔧 [Refactor](refactor.md)
+Use this template when restructuring or improving existing code without changing functionality.
+
+### 📚 [Documentation](documentation.md)
+Use this template when updating documentation, README files, or code comments.
+
+### 🧪 [Testing](testing.md)
+Use this template when adding or improving tests, test coverage, or testing infrastructure.
+
+### 🔒 [Security](security.md)
+Use this template when fixing security vulnerabilities or implementing security improvements.
+
+## How to Use
+
+1. **Choose the appropriate template** based on your change type
+2. **Copy the template content** into your PR description
+3. **Fill in all required sections** with relevant information
+4. **Check the appropriate boxes** for change type, impact scope, and priority
+5. **Provide detailed information** in the release notes points section
+
+## Standardized Fields
+
+All templates include standardized fields to help with:
+- **Automated categorization** of PRs
+- **Release note generation** 
+- **Impact assessment**
+- **Priority determination**
+
+## Benefits
+
+These templates help:
+- **Standardize PR descriptions** across the project
+- **Ensure completeness** of information provided
+- **Facilitate automated release note generation**
+- **Improve code review efficiency**
+- **Maintain consistent documentation**
+
+## Default Template
+
+If none of the specialized templates fit your needs, use the default template at `.github/pull_request_template.md`. 

.github/pull_request_template/bugfix.md

@@ -0,0 +1,61 @@
+# 🐛 Bug Fix
+
+## Problem Description
+Detailed description of the encountered bug phenomenon
+
+## Problem Analysis
+- Root cause of the bug
+- Scope of impact
+- Reproduction steps
+
+## Fix Solution
+- Specific fix method
+- Why this fix approach was chosen
+- Other possible solutions
+
+## Fix Verification
+- [ ] Post-fix testing
+- [ ] Regression testing
+- [ ] Edge case testing
+
+## Impact Assessment
+- Impact of the fix on existing functionality
+- Performance impact
+- Backward compatibility
+
+## Prevention Measures
+- How to avoid similar issues
+- Whether test cases need to be added
+- Code review points
+
+## Related Issues
+Fixes #123, Related to #456
+
+---
+
+## Change Type
+- [ ] Feature addition
+- [x] Bug fix
+- [ ] Performance optimization
+- [ ] Code refactoring
+- [ ] Documentation update
+- [ ] Testing related
+- [ ] Security fix
+
+## Impact Scope
+- [ ] User interface
+- [ ] API interface
+- [ ] Database
+- [ ] Configuration files
+- [ ] Dependencies
+
+## Priority
+- [ ] High - Release immediately
+- [ ] Medium - Next version
+- [ ] Low - Future version
+
+## Release Notes Points
+- User-visible changes
+- Configuration change instructions
+- Migration steps
+- Known issues 

.github/pull_request_template/documentation.md

@@ -0,0 +1,59 @@
+# 📚 Documentation Update
+
+## Update Scope
+- Types of documentation to update
+- Document chapters involved
+- Depth and breadth of updates
+
+## Update Content
+- New documentation content
+- Modified documentation content
+- Outdated content to remove
+
+## Update Reasons
+- Why updates are needed
+- User feedback
+- Feature change synchronization
+
+## Documentation Quality
+- [ ] Content accuracy
+- [ ] Language expression
+- [ ] Format standards
+- [ ] Example completeness
+
+## User Impact
+- Impact on user usage
+- Whether user training is needed
+- Migration guide requirements
+
+## Related Issues
+Updates documentation for #123, Related to #456
+
+---
+
+## Change Type
+- [ ] Feature addition
+- [ ] Bug fix
+- [ ] Performance optimization
+- [ ] Code refactoring
+- [x] Documentation update
+- [ ] Testing related
+- [ ] Security fix
+
+## Impact Scope
+- [ ] User interface
+- [ ] API interface
+- [ ] Database
+- [ ] Configuration files
+- [ ] Dependencies
+
+## Priority
+- [ ] High - Release immediately
+- [ ] Medium - Next version
+- [ ] Low - Future version
+
+## Release Notes Points
+- User-visible changes
+- Configuration change instructions
+- Migration steps
+- Known issues