-
Notifications
You must be signed in to change notification settings - Fork 0
cleanup opportunities complexity hotspots
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
Large and churn-heavy files are good places to look when planning refactors or targeted tests.
| Path | Why it matters |
|---|---|
src-tauri/src/commands/ai/streaming_exec.rs |
Process execution, streaming, cancellation, and watchdog behavior changed often recently. |
frontend/src/app/useAppController.test.ts |
Central workflow tests changed often as app state behavior evolved. |
crates/qa-scribe-core/src/generation/html.rs |
Backend HTML handling is sensitive because it touches generated rich content. |
.github/workflows/release.yml |
Release automation has many packaging paths and platform cases. |
| Path | Notes |
|---|---|
scripts/build_apt_repository.py |
Largest script by line count. |
scripts/validate_linux_package_metadata.py |
Package metadata validation logic. |
.github/workflows/release.yml |
Largest CI workflow. |
Before changing these areas, read Testing and run a focused check followed by bun run verify:fast or bun run verify depending on scope.
- QA Scribe
- Download overview video (MP4)
- Architecture
- Getting started
- Glossary
- By the numbers
- Lore
- Fun facts
- Video overview
- How to contribute
- Development workflow
- Testing
- Debugging
- Patterns and conventions
- Tooling
- Applications
- Desktop app
- Smoke harness
- Systems
- Rust core
- Tauri command bridge
- Frontend shell
- Generation jobs
- Provider detection
- Release tooling
- Features
- Session capture
- Rich record editing
- Managed attachments
- AI-assisted Testware
- Settings and provider setup
- Crates
- qa-scribe-core
- qa-scribe-app
- Primitives
- Session
- Entry
- Finding
- Draft
- Evidence
- API
- Tauri commands
- Deployment
- Security
- Background
- Architecture decisions
- Migration context
- Cleanup opportunities
- TODOs and FIXMEs
- Complexity hotspots
- Reference
- Configuration
- Data models
- Dependencies