Claude Code
b4b1cce902
feat(labels): standardize automatic label creation to match ecosystem convention
...
WHOOSH CI / speclint (push) Has been cancelled
WHOOSH CI / contracts (push) Has been cancelled
WHOOSH CI / speclint (pull_request) Has been cancelled
WHOOSH CI / contracts (pull_request) Has been cancelled
@goal: WHOOSH-LABELS-004, WSH-CONSISTENCY - Ecosystem standardization
Replace custom label set with standardized CHORUS ecosystem labels:
- Add all 8 GitHub-standard labels (bug, duplicate, enhancement, etc.)
- Fix bzzz-task color from #ff6b6b to #5319e7 for consistency
- Remove custom priority labels and whoosh-monitored label
- Maintain backward compatibility and error handling
Changes:
- Updated EnsureRequiredLabels() in internal/gitea/client.go
- Added requirement traceability comments throughout
- Updated integration points in internal/server/server.go
- Created comprehensive decision record
Benefits:
- Consistent labeling across WHOOSH, CHORUS, KACHING repositories
- Familiar GitHub-standard labels for better developer experience
- Improved tool integration and issue management
- Preserved bzzz-task automation for CHORUS workflow
Fixes: WHOOSH issue #4
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-09-21 17:35:15 +10:00
Claude Code
131868bdca
feat: Production readiness improvements for WHOOSH council formation
...
Major security, observability, and configuration improvements:
## Security Hardening
- Implemented configurable CORS (no more wildcards)
- Added comprehensive auth middleware for admin endpoints
- Enhanced webhook HMAC validation
- Added input validation and rate limiting
- Security headers and CSP policies
## Configuration Management
- Made N8N webhook URL configurable (WHOOSH_N8N_BASE_URL)
- Replaced all hardcoded endpoints with environment variables
- Added feature flags for LLM vs heuristic composition
- Gitea fetch hardening with EAGER_FILTER and FULL_RESCAN options
## API Completeness
- Implemented GetCouncilComposition function
- Added GET /api/v1/councils/{id} endpoint
- Council artifacts API (POST/GET /api/v1/councils/{id}/artifacts)
- /admin/health/details endpoint with component status
- Database lookup for repository URLs (no hardcoded fallbacks)
## Observability & Performance
- Added OpenTelemetry distributed tracing with goal/pulse correlation
- Performance optimization database indexes
- Comprehensive health monitoring
- Enhanced logging and error handling
## Infrastructure
- Production-ready P2P discovery (replaces mock implementation)
- Removed unused Redis configuration
- Enhanced Docker Swarm integration
- Added migration files for performance indexes
## Code Quality
- Comprehensive input validation
- Graceful error handling and failsafe fallbacks
- Backwards compatibility maintained
- Following security best practices
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-09-12 20:34:17 +10:00
Claude Code
b5c0deb6bc
Fix critical issues in WHOOSH Gitea issue monitoring and task creation
...
This commit resolves multiple blocking issues that were preventing WHOOSH from
properly detecting and converting bzzz-task labeled issues from Gitea:
## Issues Fixed:
1. **JSON Parsing Error**: Gitea API returns repository owner as string in issue
responses, but code expected User object. Added IssueRepository struct to
handle this API response format difference.
2. **Database Error Handling**: Code was using database/sql.ErrNoRows but
system uses pgx driver. Updated imports and error constants to use
pgx.ErrNoRows consistently.
3. **NULL Value Scanning**: Database fields (repository, project_id,
estimated_hours, complexity_score) can be NULL but Go structs used
non-pointer types. Added proper NULL handling with pointer scanning
and safe conversion.
## Results:
- ✅ WHOOSH now successfully detects bzzz-task labeled issues
- ✅ Task creation pipeline working end-to-end
- ✅ Tasks API functioning properly
- ✅ First bzzz-task converted: "Logic around registered agents faulty"
The core issue monitoring workflow is now fully operational and ready for
CHORUS integration.
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-09-10 12:57:11 +10:00
Claude Code
4173c0c8c8
Add automatic Gitea label creation and repository edit functionality
...
- Implement automatic label creation when registering repositories:
• bzzz-task (red) - Issues for CHORUS BZZZ task assignments
• whoosh-monitored (teal) - Repository monitoring indicator
• priority-high/medium/low labels for task prioritization
- Add repository edit modal with full configuration options
- Add manual "Labels" button to ensure labels for existing repos
- Enhance Gitea client with CreateLabel, GetLabels, EnsureRequiredLabels methods
- Add POST /api/v1/repositories/{id}/ensure-labels endpoint
- Fix label creation error handling with graceful degradation
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-09-09 22:00:29 +10:00
Claude Code
33676bae6d
Add WHOOSH search service with BACKBEAT integration
...
Complete implementation:
- Go-based search service with PostgreSQL and Redis backend
- BACKBEAT SDK integration for beat-aware search operations
- Docker containerization with multi-stage builds
- Comprehensive API endpoints for project analysis and search
- Database migrations and schema management
- GITEA integration for repository management
- Team composition analysis and recommendations
Key features:
- Beat-synchronized search operations with timing coordination
- Phase-based operation tracking (started → querying → ranking → completed)
- Docker Swarm deployment configuration
- Health checks and monitoring
- Secure configuration with environment variables
Architecture:
- Microservice design with clean API boundaries
- Background processing for long-running analysis
- Modular internal structure with proper separation of concerns
- Integration with CHORUS ecosystem via BACKBEAT timing
🤖 Generated with [Claude Code](https://claude.ai/code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-09-06 11:16:39 +10:00
