test: add draft workflow coverage and sqlite migration helpers

deploy/MARIADB.md

@@ -37,15 +37,22 @@ That means the MariaDB schema is created automatically as long as:
 - the backend container can reach `mariadb`
 
 ## 4. SQLite to MariaDB migration notes
-This repo does **not** yet include an automated data migration tool.
-If you already have real data in SQLite, recommended migration path is:
+This repo now includes helper tooling to make migration safer:
+- `deploy/sqlite_export.py` exports the important SQLite tables into JSON
+- `deploy/sqlite_preview.py` lets you inspect the exported payload quickly
+
+Suggested migration path:
 
 1. Stop writes to the app
 2. Back up SQLite DB file
-3. Start MariaDB-backed environment on a staging copy
-4. Export/import the critical tables with a small migration script or one-time tool
-5. Validate users, companies, jobs, correspondence, attachments metadata
-6. Switch production `.env` to MariaDB
+3. Export SQLite data:
+   - `python deploy/sqlite_export.py /path/to/jobtracker.db sqlite-export.json`
+4. Preview the export:
+   - `python deploy/sqlite_preview.py sqlite-export.json`
+5. Start MariaDB-backed environment on a staging copy
+6. Import with a one-time script/manual loader tailored to your production data
+7. Validate users, companies, jobs, correspondence, attachments metadata
+8. Switch production `.env` to MariaDB
 
 ## Tables you would likely want to migrate
 - `AspNetUsers`