Merge pull request #141 from SDNNetSim/feature/surv-v1-phase2-infrastructure

Feature/surv v1 phase2 infrastructure

Author: ryanmccann1024

.github/COMMIT_MESSAGE_GUIDE.md

@@ -1,8 +1,8 @@
-# 📝 Commit Message Guidelines
+# Commit Message Guidelines
 
 This project follows the [Conventional Commits](https://www.conventionalcommits.org/) specification for consistent, readable commit messages.
 
-## 📋 Format
+## Format
 
 ```
 <type>(scope): <description>
@@ -12,7 +12,7 @@ This project follows the [Conventional Commits](https://www.conventionalcommits.
 [optional footer]
 ```
 
-## 🏷️ Commit Types
+## Commit Types
 
 | Type | Purpose | Example |
 |------|---------|---------|
@@ -27,29 +27,29 @@ This project follows the [Conventional Commits](https://www.conventionalcommits.
 | `build` | Build system changes | `build: update webpack configuration` |
 | `ci` | CI/CD changes | `ci: add automated testing workflow` |
 
-## 📏 Rules
+## Rules
 
-### ✅ DO
+### DO
 - **Start with letter** after colon (upper/lowercase both OK): `feat(cli): add new feature` or `feat(api): API integration`
 - **Be descriptive**: What you changed and why
 - **Keep subject line ≤100 characters total**
 - **Use imperative mood**: "add" not "added" or "adds"
 - **Include scope** when possible: `feat(config): ...`
 
-### ❌ DON'T
+### DON'T
 - Start with numbers or symbols after colon: ~~`feat(cli): 3 new features`~~
 - Add trailing period: ~~`feat(cli): add new feature.`~~
 - Be too vague: ~~`fix bug`~~ or ~~`update code`~~
 - Exceed 100 characters in subject line (entire line)
 - Use past tense: ~~`fixed bug`~~ (use `fix bug`)
 
-### 🔀 Special Case: Merge Commits
+### Special Case: Merge Commits
 Merge commits generated by Git are automatically valid and don't need to follow conventional commit format:
 - `Merge branch 'feature/awesome' into main`
 - `Merge pull request #123 from user/branch`
 - `Merge remote-tracking branch 'origin/main'`
 
-## 🎯 Writing Great Commit Messages
+## Writing Great Commit Messages
 
 ### Focus on WHAT and WHY, not HOW
 
@@ -72,7 +72,7 @@ Added some changes           # Not descriptive
 WIP: working on feature      # Not a complete change
 ```
 
-## 🔧 FUSION-Specific Scopes
+## FUSION-Specific Scopes
 
 Use these scopes to match the project architecture:
 
@@ -89,7 +89,7 @@ Use these scopes to match the project architecture:
 - `unity` - HPC integration (`fusion/unity/`)
 - `test` - Testing framework (`tests/`)
 
-## 🚀 Examples for Common Scenarios
+## Examples for Common Scenarios
 
 ### New Features
 ```
@@ -157,7 +157,7 @@ resource cleanup and reduces memory usage by 60% for large networks.
 Fixes #234
 ```
 
-## 🧪 Testing Your Commit Messages
+## Testing Your Commit Messages
 
 Before committing, test your message format:
 
@@ -167,15 +167,15 @@ Before committing, test your message format:
 # Total subject line length: ≤100 characters
 ```
 
-## 🔍 Why These Standards?
+## Why These Standards?
 
 1. **Consistency**: All commits follow the same format
 2. **Automation**: Tools can parse commit types for changelogs
 3. **Clarity**: Clear what changed and where
 4. **History**: Easy to understand project evolution
 5. **Reviews**: Faster PR reviews with structured information
 
-## 🛠️ Tools
+## Tools
 
 Consider using:
 - [Conventional Commits CLI](https://github.com/conventional-commits/cli)
@@ -184,4 +184,4 @@ Consider using:
 
 ---
 
-**Remember**: Great commit messages help future you and your teammates understand the codebase evolution! 🎯
+**Remember**: Great commit messages help future you and your teammates understand the codebase evolution!

.github/issue_template/01_bug_report.yml .github/ISSUE_TEMPLATE/01_bug_report.yml.github/issue_template/01_bug_report.yml renamed to .github/ISSUE_TEMPLATE/01_bug_report.yml

@@ -1,4 +1,4 @@
-name: 🐛 Bug Report
+name: Bug Report
 description: Report a bug to help us improve FUSION simulator
 title: "[BUG] "
 labels: ["bug", "needs-triage"]
@@ -8,8 +8,8 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## 🐛 Bug Report
-        
+        ## Bug Report
+
         Thank you for taking the time to report a bug! Please fill out the form below with as much detail as possible.
 
   - type: textarea

…ub/issue_template/02_feature_request.yml …ub/ISSUE_TEMPLATE/02_feature_request.yml.github/issue_template/02_feature_request.yml renamed to .github/ISSUE_TEMPLATE/02_feature_request.yml .github/issue_template/02_feature_request.yml renamed to .github/ISSUE_TEMPLATE/02_feature_request.yml

@@ -1,4 +1,4 @@
-name: 🚀 Feature Request
+name: Feature Request
 description: Suggest a new feature or enhancement for FUSION simulator
 title: "[FEATURE] "
 labels: ["enhancement", "needs-discussion"]
@@ -8,8 +8,8 @@ body:
   - type: markdown
     attributes:
       value: |
-        ## 🚀 Feature Request
-        
+        ## Feature Request
+
         Thank you for suggesting a new feature! Please provide detailed information to help us understand and evaluate your request.
 
   - type: input

.github/issue_template/config.yml .github/ISSUE_TEMPLATE/config.yml.github/issue_template/config.yml renamed to .github/ISSUE_TEMPLATE/config.yml

@@ -1,20 +1,17 @@
 blank_issues_enabled: false
 contact_links:
-  - name: 📚 Configuration Guide
+  - name: Configuration Guide
     url: https://github.com/SDNNetSim/FUSION/blob/main/fusion/configs/README.md
     about: Comprehensive guide for configuration system, templates, and troubleshooting
-  - name: 🚀 Architecture Documentation  
-    url: https://github.com/SDNNetSim/FUSION/blob/main/Architecture%20Plan.md
-    about: Review the system architecture and migration plan
-  - name: 💬 GitHub Discussions
-    url: https://github.com/SDNNetSim/FUSION/discussions
-    about: Ask questions, share ideas, and discuss FUSION simulator topics
-  - name: 📖 Getting Started Tutorial
+  - name: Architecture Documentation
+    url: https://github.com/SDNNetSim/FUSION/blob/main/ARCHITECTURE.md
+    about: Review the system architecture, components, and design principles
+  - name: Getting Started Tutorial
     url: https://github.com/SDNNetSim/FUSION/blob/main/fusion/configs/README.md#-quick-start-tutorial
     about: Step-by-step guide for new users to get started with FUSION
-  - name: 🔬 Research Papers & Citations  
-    url: https://github.com/SDNNetSim/FUSION#publications
+  - name: Research Papers & Citations
+    url: https://github.com/SDNNetSim/FUSION#-publications
     about: Academic publications and research using FUSION simulator
-  - name: 🧪 Testing & Examples
+  - name: Testing & Examples
     url: https://github.com/SDNNetSim/FUSION/tree/main/tests
     about: View test cases and example configurations for guidance

.github/PULL_REQUEST_TEMPLATE/feature_pr_template.md

@@ -1,14 +1,14 @@
-## ✨ Feature Pull Request
+## Feature Pull Request
 
-**Related Feature Request**: 
+**Related Feature Request**:
 <!-- Link the original feature request: Fixes #123 -->
 
-**Feature Summary**: 
+**Feature Summary**:
 <!-- Brief description of what this feature adds -->
 
 ---
 
-## 🎯 Feature Implementation
+## Implementation Details
 
 **Components Added/Modified**:
 - [ ] CLI Interface (`fusion/cli/`)
@@ -35,7 +35,7 @@ new_parameter = default_value
 
 ---
 
-## 🧪 Feature Testing
+## Testing
 
 **New Test Coverage**:
 - [ ] Unit tests for new functionality
@@ -58,7 +58,7 @@ new_parameter = default_value
 
 ---
 
-## 📊 Performance Impact
+## Performance Impact
 
 **Benchmarks**:
 - **Memory Usage**: [No impact / +X MB / -X MB optimized]
@@ -70,7 +70,7 @@ new_parameter = default_value
 
 ---
 
-## 📚 Documentation Updates
+## Documentation
 
 **Documentation Added/Updated**:
 - [ ] API documentation for new functions/classes
@@ -91,7 +91,7 @@ result = component.process(input_data)
 
 ---
 
-## 🔄 Backward Compatibility
+## Backward Compatibility
 
 **Compatibility Impact**:
 - [ ] Fully backward compatible
@@ -104,7 +104,7 @@ result = component.process(input_data)
 
 ---
 
-## 🚀 Feature Checklist
+## Checklist
 
 **Core Implementation**:
 - [ ] Feature implemented according to specification
@@ -128,7 +128,7 @@ result = component.process(input_data)
 
 ---
 
-## 🎉 Feature Demo
+## Demo
 
 **Before/After Comparison**:
 <!-- Show what users can do now that they couldn't before -->
@@ -138,7 +138,7 @@ result = component.process(input_data)
 
 ---
 
-## 📝 Reviewer Notes
+## Reviewer Notes
 
 **Focus Areas for Review**:
 <!-- Highlight specific areas where you want reviewer attention -->

.github/PULL_REQUEST_TEMPLATE/hotfix_pr_template.md

@@ -1,19 +1,19 @@
-## 🚨 Hotfix Pull Request
+## Hotfix Pull Request
 
-**Related Issue**: 
+**Related Issue**:
 <!-- Link the bug report: Fixes #123 -->
 
-**Hotfix Summary**: 
+**Hotfix Summary**:
 <!-- Brief description of what this hotfix resolves -->
 
 **Urgency Level**:
 - [ ] Critical (production breaking)
-- [ ] High (major functionality impacted)  
+- [ ] High (major functionality impacted)
 - [ ] Medium (important bug fix)
 
 ---
 
-## 🐛 Problem Description
+## Problem Description
 
 **Root Cause Analysis**:
 <!-- Describe the underlying cause of the issue -->
@@ -26,7 +26,7 @@
 
 ---
 
-## 🔧 Hotfix Implementation
+## Implementation
 
 **Files Changed**:
 <!-- List the specific files modified -->
@@ -43,7 +43,7 @@
 
 ---
 
-## ✅ Hotfix Validation
+## Validation
 
 **Testing Performed**:
 - [ ] Reproducer test case created
@@ -66,7 +66,7 @@
 
 ---
 
-## 📊 Risk Assessment
+## Risk Assessment
 
 **Change Risk Level**:
 - [ ] Low (isolated change, well tested)
@@ -81,7 +81,7 @@
 
 ---
 
-## 🚀 Deployment Considerations
+## Deployment Considerations
 
 **Deployment Requirements**:
 - [ ] Safe for immediate deployment
@@ -97,7 +97,7 @@
 
 ---
 
-## 🏁 Hotfix Checklist
+## Checklist
 
 **Code Quality**:
 - [ ] Minimal change to address the specific issue
@@ -125,7 +125,7 @@
 
 ---
 
-## 📝 Additional Notes
+## Additional Notes
 
 **Follow-up Tasks**:
 <!-- Any additional work needed after this hotfix -->