# FinanceManager Sprint 6 deployment rollback readiness

- Deployment commit: `46d689c3afac4a0f0e5190787bb870ef2662724c`
- Verified remote branch: `origin/sprint6/portfolio-data-ingestion-reconciliation`
- Code rollback target: Sprint 5 commit `480d7a1b72a950e864c4bb021d3f58af8f8c15f9`
- Clean rollback worktree: `/home/agent/.hermes/worktrees/FinanceManager-sprint5-portfolio-performance-foundation`
- Pre-deployment DB backup: `/home/agent/jarvis_runtime/finance-system/backups/sprint6-deployment/finance-pre-sprint6-20260724T082102Z.sqlite3`
- Backup SHA-256: `f48e27f64e3ce367e4d44ec3d3bb7ee7aa0c4c03b2bb65efc7f4b89a4040a402`
- Backup schema/integrity: `40` / `ok`
- Migration probe: schema `40 → 41`, integrity `ok`, business-data digest unchanged, new ingestion tables empty.

## Rollback policy

1. Stop only the Sprint-6 backend/frontend processes and retain their logs.
2. Start the clean Sprint-5 worktree on the same Tailscale-only endpoints.
3. Leave additive schema-41 objects in place: Sprint 5 ignores them. Do **not** rerun `/tmp/financemanager-schema41-to40-rollback.py`.
4. Do not restore the database backup unless an actual data rollback is required and separately authorized.
5. After a code rollback, verify API health, portfolio endpoint, DB integrity, and Tailscale frontend access.