-
Notifications
You must be signed in to change notification settings - Fork 0
background migration context
factory-droid[bot] edited this page Jul 5, 2026
·
1 revision
The current app intentionally does not migrate earlier Electrobun/Bun MVP data. README.md states that existing MVP data, Drizzle artifacts, Bun SQLite migrations, and Electrobun app-data layouts are not migration targets.
This boundary lets the Rust core own a fresh SQLite schema in crates/qa-scribe-core/src/storage/mod.rs. It also keeps attachment storage and generation history aligned with current domain types under crates/qa-scribe-core/src/domain.
| File | Purpose |
|---|---|
README.md |
Current status and migration boundary. |
docs/adr/0009-rebuild-with-rust-tauri.md |
Rebuild decision. |
crates/qa-scribe-core/src/storage/mod.rs |
Fresh schema implementation. |
crates/qa-scribe-core/src/lib.rs |
App status declares migration_required: false. |
See Rust core for the implementation boundary.
- 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