docs: add open source community health files, issue templates, and contributing guide

Author: Rowrow620

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,28 @@
+---
+name: Bug Report
+about: Create a report to help us reproduce and fix an issue
+title: 'bug: '
+labels: 'bug'
+assignees: ''
+---
+
+## Description
+A clear and concise description of the bug.
+
+## Steps to Reproduce
+1. Launch AlgoBuddy (Native desktop or WASM web build).
+2. Select problem `#XX: [Problem Title]`.
+3. Input parameters: `...`
+4. Click 'Play' or scrub timeline to step `X`.
+5. Observe error behavior.
+
+## Expected Behavior
+A clear description of what you expected to happen.
+
+## Platform Environment
+- OS: [e.g. Windows 11, macOS Sonoma, Ubuntu 22.04, WASM / Browser]
+- Browser (if WASM): [e.g. Chrome 125, Firefox 126, Safari 17]
+- Application Version: [e.g. v0.5.0]
+
+## Screenshots / Console Output
+If applicable, attach screenshots or terminal logs to help explain the issue.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature Request
+about: Suggest an idea or enhancement for AlgoBuddy
+title: 'feat: '
+labels: 'enhancement'
+assignees: ''
+---
+
+## Feature Description
+A clear and concise description of the proposed feature or visualizer enhancement.
+
+## Motivation / Problem Statement
+What problem does this feature solve, or how does it improve the visual learning experience?
+
+## Proposed Implementation Details
+If applicable, describe how the proposed feature would interact with the UI, step generator engine, or canvas state renderers.
+
+## Alternative Solutions
+Describe any alternative solutions or features considered.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+## Description
+Summary of the changes made in this pull request and the rationale behind them.
+
+## Related Issues
+Closes #[issue_number]
+
+## Type of Change
+- [ ] Bug fix (non-breaking change fixing an issue)
+- [ ] New problem visualizer audit / promotion (`AuditStatus::Audited`)
+- [ ] New feature (non-breaking change adding functionality)
+- [ ] Documentation update
+- [ ] Refactoring / performance optimization
+
+## Verification Checklist
+- [ ] Code compiles cleanly without errors
+- [ ] `cargo test` passes 100% of unit tests
+- [ ] `cargo fmt --all -- --check` complies with standard Rust formatting
+- [ ] `cargo clippy --all-targets -- -D warnings` produces zero warnings
+- [ ] Step visualizer tested locally in desktop mode (`cargo run`) and/or WebAssembly mode (`trunk serve`)

CODE_OF_CONDUCT.md

@@ -0,0 +1,55 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+---
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our project include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+---
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for enforcement decisions when appropriate.
+
+---
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and also applies when an individual is officially representing the project in public spaces. Examples of representing a project or community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+---
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project maintainers. All complaints will be reviewed and investigated promptly and fairly.
+
+All project leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+---
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.

CONTRIBUTING.md

@@ -0,0 +1,80 @@
+# Contributing to AlgoBuddy
+
+Thank you for your interest in contributing to AlgoBuddy. This document outlines the development workflow, project architecture, testing requirements, and submission process for pull requests.
+
+---
+
+## Development Setup
+
+### Prerequisites
+- Rust 1.75 or later (`rustup update stable`)
+- Cargo (included with standard Rust installation)
+- Trunk (for WebAssembly builds): `cargo install trunk`
+- WASM target: `rustup target add wasm32-unknown-unknown`
+
+### Local Execution
+
+To run the native desktop application:
+```bash
+cargo run
+```
+
+To run the WebAssembly application locally in a browser:
+```bash
+trunk serve
+```
+Then navigate to `http://127.0.0.1:8080`.
+
+---
+
+## Running Tests
+
+All algorithm step generators and parsing logic are validated using automated Rust unit tests. Run the full test suite with:
+
+```bash
+cargo test
+```
+
+Ensure all tests pass before submitting a pull request.
+
+---
+
+## Architecture Overview
+
+AlgoBuddy is structured into four core areas:
+
+1. `src/main.rs`: Application entry points for native execution (`eframe::run_native`) and WASM execution (`eframe::WebRunner`).
+2. `src/model.rs`: Problem definitions (`Problem`), category taxonomy (`Category`), difficulty levels (`Difficulty`), metadata specs (`ProblemDetails`), and visual state snapshots (`VisualState`).
+3. `src/app.rs`: Main GUI application state (`VisualizerApp`), UI view modes, navigation, playback controls, canvas renderers, and theme palettes.
+4. `src/algorithms/`: Step snapshot generator functions (`generate_*_steps`) for each algorithm.
+
+### Deterministic State Engine
+Algorithms in AlgoBuddy do not execute asynchronously during playback. Instead, generator functions in `src/algorithms/` execute synchronously upfront and produce a `Vec<Step>` snapshot vector. The GUI renders state snapshots based on the active timeline index (`current_step_idx`), allowing forward and backward scrubbing.
+
+### Release Mode and Audit Gating
+Problems in AlgoBuddy carry an audit status (`AuditStatus::Audited` or `AuditStatus::Unaudited`).
+- By default (Public Release Mode), the UI presents only audited problems.
+- Developer Mode (toggleable in Settings) displays all implemented problems, flagging unaudited implementations with an `[EXP]` tag.
+
+---
+
+## How to Audit or Promote a Problem
+
+To audit an existing problem visualizer and promote it to Public Release status:
+
+1. Open the application in Developer Mode (`show_unaudited: true`).
+2. Verify that the algorithm step generator produces accurate state snapshots for standard and edge-case inputs.
+3. Ensure active line highlighting (`code_line`) matches the associated source code snippet.
+4. Add a unit test in `src/app.rs` under `#[cfg(test)] mod tests` asserting expected output values.
+5. In `src/model.rs`, update the `audit_status` match arm for the target problem to return `AuditStatus::Audited`.
+6. Run `cargo test` to verify build and test compliance.
+
+---
+
+## Pull Request Guidelines
+
+1. **Branch Naming**: Use descriptive branch names such as `feat/audit-two-sum` or `fix/canvas-render-bounds`.
+2. **Code Formatting**: Format code using `cargo fmt` before committing.
+3. **Clippy Compliance**: Ensure `cargo clippy --all-targets -- -D warnings` reports zero warnings.
+4. **Test Coverage**: Include unit tests for any new algorithm step generators or parser utilities.
+5. **Commit Messages**: Write concise commit messages following standard conventions (e.g., `feat: add visualizer for problem #X`, `fix: resolve bounds checking on timeline scrubber`).

SECURITY.md

@@ -0,0 +1,25 @@
+# Security Policy
+
+## Supported Versions
+
+Security updates are applied to the `main` branch and released via the latest tagged GitHub releases and WebAssembly live build.
+
+| Version | Supported          |
+| ------- | ------------------ |
+| latest  | Yes                |
+| < 0.5.0 | No                 |
+
+---
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability within AlgoBuddy, please report it responsibly rather than opening a public issue.
+
+### Disclosure Process
+
+1. Email security reports directly to the project maintainers or submit a private security advisory via GitHub Security Advisories.
+2. Provide a detailed description of the vulnerability, including steps to reproduce, impacted components, and potential risk assessment.
+3. The maintainers will acknowledge receipt of your vulnerability report within 48 hours and provide status updates as investigation progresses.
+4. Once a fix is developed and verified, a patched release will be published.
+
+We appreciate your assistance in keeping AlgoBuddy secure for all users and contributors.