jobtrackingapp/docs/work-programmes/session-handoff.md

JobTracker session handoff

Updated: 2026-08-10

• Exact current task: MAIL-001 — add a server-authorized explicit failed-attempt rotation before implementing compose-new-message; preserve one idempotency identity across ordinary edits/refresh.
• Last completed step: explicit save/resume/delete/conflict UI for reply drafts was committed/pushed as d3d2b67; focused 11/11, frontend 196/196 and production build pass.
• Files currently modified: authoritative MAIL-001 tracking/evidence only; persistence/export/API code is committed.
• Commands already run: dependency/audit/router/full frontend/build; legacy follow-up/export/recovery/provider suites; full backend; Gitea run inspection; Playwright; MAIL context/unlink/provider-state/Free-policy/draft-persistence focused and full suites/build; EF model-current and dual-provider up/down scripts. See V-126–V-146.
• Test results: npm audit 0 vulnerabilities; Gitea pull-request CI PASS in 4m20s at run 609; backend 625/625; frontend 50/50 suites and 194/194 tests; Playwright 4/4; production build passes. Draft isolation/cascade 1/1; EF model current; SQLite/MariaDB draft up/down scripts pass. Full blank-chain SQLite apply fails earlier in AddJobEntityAndProspectStages on missing LastReminderEmailSentAt (JT-019).
• Services currently running: none on task-owned ports 3000/5202. Playwright stopped its disposable API/Next servers. Pre-existing Docker services were not changed.
• Temporary files or processes: no task-owned process is running and the failed disposable migration database was removed. Existing synthetic browser evidence/account and startup-created local backup remain documented. No provider account, real email, private content, paid service or production service was accessed.
• Production changes currently active: none. No deployment, migration, provider connection/sync/send or production payload occurred.
• Rollback status: downgrade 20260810080858_AddEmailDraftClientRequestId, then 20260810075206_AddEmailDrafts, before reverting draft commits; then follow the existing MAIL rollback order (ee5ef7e, 449faeb, 123fc55/e9937ac, ledger downgrade before 653f011). No production migration/deploy/provider grant occurred.
• Uncommitted changes: tracking/evidence for d3d2b67 and V-150 only; commit and push before failed-attempt rotation.
• Known failures: live deployment is not verified because PR deploy is intentionally skipped and the active branch is not approved for merge. Draft export/API/UI, full thread/category actions and non-Gmail review remain; existing accounts need re-consent and IMAP stays read-only. A clean full-chain SQLite apply fails in the pre-existing JT-019 migration before the new draft migration. Browser/provider/MariaDB/production unavailable or unverified; recovery scan performance is unmeasured at large ledger scale; Jest open handles; SEC-006 parser dependency work is still separately gated; parser isolation remains SEC-007.
• Exact next action: add a revisioned new-attempt draft action allowed only after the matching owner ledger attempt is definitively failed; update Prepare new attempt to persist the rotated UUID. Then add compose-new-message job/provider selection.
• Work that can continue independently: remaining MAIL-001 repository work and later UX packages. SEC-006/007 await package-index permission; PROD-001/003/004 await production access.
• Decisions still required from the user: none for synthetic/code-inspected repository work. Any provider connection or send test, internet/package upgrades, private data, external/paid providers and production actions retain explicit approval/safety gates; SEC-009 retention/legal policy remains unresolved.