tony/hive

Files

anthonyrawlins 268214d971 Major WHOOSH system refactoring and feature enhancements

- Migrated from HIVE branding to WHOOSH across all components
- Enhanced backend API with new services: AI models, BZZZ integration, templates, members
- Added comprehensive testing suite with security, performance, and integration tests
- Improved frontend with new components for project setup, AI models, and team management
- Updated MCP server implementation with WHOOSH-specific tools and resources
- Enhanced deployment configurations with production-ready Docker setups
- Added comprehensive documentation and setup guides
- Implemented age encryption service and UCXL integration

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-08-27 08:34:48 +10:00

2.0 KiB

Raw Blame History

🐛 WHOOSH Bug Reporting Process

This document outlines the process for reporting bugs discovered during WHOOSH development.

🎯 Bug Reporting Criteria

Report bugs when you find:

Reproducible errors in existing functionality
Performance regressions compared to expected behavior
Security vulnerabilities or authentication issues
Data corruption or inconsistent state
API endpoint failures returning incorrect responses
UI/UX issues preventing normal operation
Docker/deployment issues affecting system stability

📋 Bug Report Template

## Bug Description
Brief description of the issue

## Steps to Reproduce
1. Step one
2. Step two
3. Step three

## Expected Behavior
What should happen

## Actual Behavior
What actually happens

## Environment
- WHOOSH Version: [commit hash]
- Component: [backend/frontend/mcp-server/docker]
- Browser: [if applicable]
- OS: Linux

## Error Logs

[error logs here]


## Additional Context
Any additional information that might be helpful

🔧 Bug Reporting Commands

Create Bug Report

gh issue create \
  --title "Bug: [Short description]" \
  --body-file bug-report.md \
  --label "bug" \
  --assignee @me

List Open Bugs

gh issue list --label "bug" --state open

Update Bug Status

gh issue edit [issue-number] --add-label "in-progress"
gh issue close [issue-number] --comment "Fixed in commit [hash]"

🏷️ Bug Labels

bug - Confirmed bug
critical - System-breaking issue
security - Security vulnerability
performance - Performance issue
ui/ux - Frontend/user interface bug
api - Backend API issue
docker - Container/deployment issue
mcp - MCP server issue

📊 Bug Tracking

All bugs discovered during CCLI development will be tracked in GitHub Issues with:

Clear reproduction steps
Error logs and screenshots
Component tags
Priority labels
Fix verification process

This ensures systematic tracking and resolution of all issues found during development.

2.0 KiB Raw Blame History