BLITZ - Windsurf/Cursor Integration with Configurable Scanning and Comprehensive Testing #28
Labels
No labels
auth
blocked
bug
bug
changelog-extraction
chore
ci/cd
ci/cd
completed
component:blitz
component:chatter
component:entertainment
component:foodchain
component:forgejo-client
component:gatekeeper
component:mappy
component:monads
component:spiffy
critical
dependencies
dependencies
dependency-management
documentation
documentation
enhancement
enhancement
enhancement
feature
feature
fix
graphics
high
high-priority
in-progress
integration
integration
investigation
lang:go
lang:python
lang:rust
lang:shell
lang:toml
lang:typescript
low
medium
pending
performance
performance
priority:critical
priority:high
priority:low
priority:medium
process
ready
research
review
security
security
shell-pool
technical-debt
technical-debt
testing
tracking
tracking
ui
vendor
vendor-cleanup
workgroup
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kade/blitz#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Blitz (Zed fork at ./services/blitz) needs Windsurf/Cursor integration with:
Current State
Blitz Structure Analysis
Directory Structure:
services/blitz/crates/denoise/models/- ONNX model files (model_1_converted_simplified.onnx, model_2_converted_simplified.onnx)services/blitz/crates/project_panel/benches/- Large benchmark snapshot (linux_repo_snapshot.txt, 3.9MB)services/blitz/target/- Build artifacts (20,116 files)Historical Context (from CHANGELOG):
Assessment
Blitz appears to be in an incomplete state:
Solution Architecture
Phase 1: Codebase Restoration (Week 1)
Tasks:
Phase 2: Configurable Scanning Strategy (Week 2)
Configuration File (blitz-scan.toml):
Scanner Implementation:
Phase 3: Comprehensive Testing (Week 3-4)
Test Structure:
Test Configuration (blitz-test.toml):
Phase 4: Mermaid Documentation (Week 5)
Documentation Structure:
Mermaid Diagrams to Generate:
Phase 5: Windsurf/Cursor Integration (Week 6)
Integration Files:
services/blitz/.codeiumignore:
services/blitz/AGENTS.md:
Implementation Plan
Week 1: Codebase Restoration
Week 2: Scanning Strategy
Week 3: Testing Infrastructure
Week 4: Test Coverage
Week 5: Documentation
Week 6: Windsurf Integration
Verification
Acceptance Criteria
Testing Checklist
Progress Tracking
This issue will be updated weekly with:
References
Migrated from reynard/reynard#1059