chore(dev): implement development automation and update docs

Add comprehensive Makefile for development automation and refactor
contributing guide for clarity and completeness.

- Add Makefile with features:
  * Development commands (fmt, clippy, test, audit)
  * Release management with semantic versioning
  * Changelog automation with git-cliff
  * Colored output and helpful messages
  * Development vs release checks separation
  * Package verification and publishing support

- Update CONTRIBUTING.md:
  * Add detailed guide for development workflow
  * Improve release process documentation
  * Add troubleshooting section
  * Include yanking instructions
  * Add best practices
  * Update commands to use Make

The new automation system simplifies development setup, standardizes
quality checks, and provides a clear process for contributors.

Author: d1r1

CONTRIBUTING.md

@@ -1,93 +1,128 @@
 # Contributing Guide
 
-Thank you for considering contributing to this project! This guide will help you understand our workflow, coding standards, and release process. Whether you're fixing a bug, adding a feature, or improving documentation, your contribution is highly appreciated!
+Thank you for considering contributing to this project! This guide will help you understand our workflow, coding standards, and release process.
+
+## Ways to Contribute
+
+1. **Opening Issues**
+   - Report bugs with detailed descriptions
+   - Suggest enhancements
+   - Request features
+   - Create detailed issue descriptions using templates
+   - Use issue templates for bugs and features
+
+2. **Adding Context**
+   - Provide reproduction steps
+   - Share code snippets
+   - Add screenshots
+   - Write use cases
+   - Add examples and scenarios
+   - Link to related issues or PRs
+
+3. **Resolving Issues**
+   - Fix bugs
+   - Implement features
+   - Improve documentation
+   - Enhance performance
+   - Demonstrate that an issue is not a problem
+   - Open pull requests with fixes
+
+4. **Reviewing Pull Requests**
+   - Review code changes
+   - Test proposed features
+   - Suggest improvements
+   - Share domain expertise
+   - Help maintain code quality
+   - Participate in technical discussions
+
+## Development Setup
+
+We use Make to automate development tasks. Start by setting up your environment:
 
-## Ways to contribute
-
-There are fundamentally four ways an individual can contribute:
+```bash
+make setup
+```
 
-1. **By opening an issue:** For example, if you believe that you have uncovered a bug,
-   creating a new issue in the issue tracker is the way to report it.
-2. **By adding context:** Providing additional context to existing issues,
-   such as screenshots and code snippets.
-3. **By resolving issues:** Either demonstrating that the issue is not a problem,
-   or opening a pull request with a fix.
-4. **By reviewing pull requests:** Help review and discuss proposed changes.
+This installs required tools:
 
-**Anybody can participate in any stage of contribution**. We urge you to participate in the discussion around bugs and participate in reviewing PRs.
+- `cargo-audit`: Security vulnerability scanning
+- `cargo-edit`: Dependency management
+- `git-cliff`: Changelog generation
 
 ## Development Workflow
 
-1. **Fork and clone the repository**
+1. **Fork and Clone**
 
    ```bash
    git clone https://github.com/fluentlabs-xyz/gblend.git
    cd gblend
    ```
 
-2. **Create a new branch**
+2. **Setup Environment**
 
    ```bash
-   git checkout -b feat/your-feature
+   make setup
    ```
 
-3. **Sync with the main repository** (if necessary):
+3. **Create Feature Branch**
 
    ```bash
-   git remote add upstream https://github.com/fluentlabs-xyz/gblend.git
-   git pull upstream main
+   git checkout -b feat/your-feature
+   # or
+   git checkout -b fix/your-bugfix
    ```
 
-4. **Make changes following the commit convention**
-
-5. **Test your changes**
+4. **Sync with upstream** (if necessary)
 
    ```bash
-   cargo test
-   cargo fmt -- --check
-   cargo clippy -- -D warnings
+   git remote add upstream https://github.com/fluentlabs-xyz/gblend.git
+   git pull upstream main
    ```
 
-6. **Push changes**
+5. **Make Changes**
+   - Write code
+   - Add tests
+   - Update documentation
+
+6. **Verify Changes**
 
    ```bash
-   git push origin feat/your-feature
+   # During development - run individual checks
+   make fmt           # Check formatting
+   make clippy        # Check lints
+   make test          # Run tests
+   make audit         # Check dependencies
+
+   # Before creating PR - run all checks
+   make check         # Full verification
    ```
 
-7. **Open a Pull Request**
-   - Go to your fork on GitHub
-   - Click "New Pull Request"
-   - Choose the appropriate template:
-     - Use the default template for general changes
-     - Use the feature template for new features
-     - Use the bugfix template for bug fixes
-   - Fill in all required sections of the template
-   - Link any related issues using the `Closes #issue-number` syntax
-   - Request reviews from maintainers
-   - Ensure all checks are passing
+7. **Create Pull Request**
+   - Use conventional commits
+   - Link related issues
+   - Fill PR template
+   - Request reviews
 
 ## Commit Convention
 
-We use [Conventional Commits](https://www.conventionalcommits.org/):
+We follow [Conventional Commits](https://www.conventionalcommits.org/):
 
-```bash
-# Format
+```
 <type>[optional scope]: <description>
 
-# Types
+Types:
 feat:     New features
 fix:      Bug fixes
-docs:     Documentation changes
-style:    Code style changes
-refactor: Code changes without features/fixes
-test:     Tests changes
-chore:    Build process changes
-
-# Examples
-feat(auth): add OAuth support
-fix(ui): resolve button alignment issue
+docs:     Documentation only
+style:    Style/formatting changes
+refactor: Code refactoring
+test:     Testing changes
+chore:    Maintenance tasks
+
+Examples:
+feat(api): add user authentication
+fix(ui): correct button alignment
 docs: update installation guide
-test: add unit tests for auth module
 ```
 
 ## Release Process
@@ -102,87 +137,55 @@ We follow [Semantic Versioning](https://semver.org/) (MAJOR.MINOR.PATCH):
 
 ### Creating a Release
 
-1. **Install cargo-edit**
-
-   ```bash
-   cargo install cargo-edit
-   ```
-
-2. **Update version**
-
-   For incremental version updates:
-
-   ```bash
-   # For MAJOR version bump (breaking changes)
-   cargo set-version --bump major
-
-   # For MINOR version bump (new features)
-   cargo set-version --bump minor
-
-   # For PATCH version bump (bug fixes, small changes)
-   cargo set-version --bump patch
-   ```
-
-   For setting a specific version:
+1. **Verify Release Readiness**
 
    ```bash
-   cargo set-version 1.2.3
+   make check-release
    ```
 
-   For pre-release versions:
+2. **Prepare Release**
 
    ```bash
-   # For alpha releases
-   cargo set-version 1.2.3-alpha.1
-
-   # For beta releases
-   cargo set-version 1.2.3-beta.1
-
-   # For release candidate versions
-   cargo set-version 1.2.3-rc.1
-   ```
-
-3. **Generate changelog using git-cliff**
+   # Using semantic versioning
+   make release VERSION=major  # Breaking changes
+   make release VERSION=minor  # New features
+   make release VERSION=patch  # Bug fixes
 
-   ```bash
-   # Update changelog
-   git cliff --tag v1.2.3 -o CHANGELOG.md
+   # Or specific version
+   make release VERSION=1.2.3
 
-   # Or append unreleased changes
-   git cliff --unreleased --tag v1.2.3 --prepend CHANGELOG.md
+   # Pre-release versions
+   make release VERSION=1.2.3-alpha.1  # Alpha releases
+   make release VERSION=1.2.3-beta.1   # Beta releases
+   make release VERSION=1.2.3-rc.1     # Release candidates
    ```
 
-4. **Commit version and changelog**
+3. **Review Changes**
+   - Check generated changelog
+   - Review version updates
+   - Verify all changes are included
+
+4. **Commit Release**
 
    ```bash
-   git add Cargo.toml CHANGELOG.md
-   git commit -m "chore: release version 1.2.3"
+   make commit-version
    ```
 
-5. **Create and push a release tag**
+5. **Push Release**
 
    ```bash
-   git tag -a v1.2.3 -m "Release v1.2.3"
-   git push origin v1.2.3
+   git push origin main v1.2.3
    ```
 
-6. **Automated Publishing**
-   - Pushing the tag `v*.*.*` will automatically trigger the GitHub Action workflow
-   - The workflow will:
-     1. Check code formatting
-     2. Run clippy lints
-     3. Run tests
-     4. Publish to crates.io using the `CARGO_REGISTRY_TOKEN`
+### Managing the Changelog
 
-7. **Create GitHub Release**
-   - Go to Releases page
-   - Click "Draft a new release"
-   - Select the tag
-   - Use git-cliff to generate release notes:
+```bash
+# Preview upcoming changes
+make changelog-preview
 
-     ```bash
-     git cliff --current --strip header
-     ```
+# Update changelog
+make changelog
+```
 
 ### Managing Published Versions
 
@@ -207,20 +210,6 @@ Important notes about yanking:
   - Has backwards compatibility issues
   - Was accidentally published
 
-### Release Checklist
-
-| Checkpoint                       | Command/Action                        | Status |
-|---------------------------------|--------------------------------------|--------|
-| Install cargo-edit             | `cargo install cargo-edit`           | [ ]    |
-| Version bump                   | `cargo set-version 1.2.3`            | [ ]    |
-| Changelog generated           | `git cliff`                          | [ ]    |
-| Tests passing                   | `cargo test`                         | [ ]    |
-| Formatting checked              | `cargo fmt -- --check`               | [ ]    |
-| Linting checked                 | `cargo clippy -- -D warnings`        | [ ]    |
-| Dependencies reviewed           | Check `Cargo.toml`                   | [ ]    |
-| Breaking changes documented     | Update CHANGELOG.md                  | [ ]    |
-| `CARGO_REGISTRY_TOKEN` present  | Check GitHub Secrets                 | [ ]    |
-
 ### Troubleshooting Releases
 
 If the automated publishing fails:
@@ -242,16 +231,50 @@ After yanking a version:
 3. Notify users through GitHub Issues
 4. Update release notes to indicate the version is yanked
 
-## Code of Conduct
+## Development Commands
+
+Run `make help` to see all available commands. Common tasks:
+
+```bash
+# Main commands
+make check           # Run all development checks
+make check-release   # Full release verification
+make clean           # Clean build artifacts
+
+# Individual checks
+make fmt            # Check formatting
+make clippy         # Run linter
+make test          # Run tests
+make audit         # Security audit
+```
 
-We follow the [Contributor Covenant](https://www.contributor-covenant.org/). Please be respectful and inclusive while contributing to the project.
+## Best Practices
+
+1. **Code Quality**
+   - Write tests for new features
+   - Maintain code coverage
+   - Follow project style guide
+   - Add documentation
+
+2. **Pull Requests**
+   - Keep changes focused
+   - Update tests
+   - Add documentation
+   - Respond to reviews
+
+3. **Communication**
+   - Be respectful
+   - Provide context
+   - Ask questions
+   - Stay engaged
 
 ## Getting Help
 
-If you need help with your contribution:
+- Issues: Report bugs and request features
+- Pull Requests: Get feedback on changes
 
-- Open a discussion in the GitHub Discussions tab
-- Ask in the project's communication channels
-- Check existing documentation and issues
+Every contributor was once a beginner - don't hesitate to ask for help!
+
+## Code of Conduct
 
-Remember: every contributor was once a beginner. Don't hesitate to ask for help or clarification.
+We follow the [Contributor Covenant](https://www.contributor-covenant.org/). Be respectful and inclusive in all interactions.