gsinghpal 8eb4b8dc6c fix(fusion_accounting_followup): seeded levels + migration idempotency ...

- test_create_minimal/negative_delay used sequence=1, which now collides
  with the seeded Friendly Reminder level. Use sequences 901/902.
- migration backfill: search by name (not raw seq) for idempotency,
  allocate sequence as max(existing)+1 to avoid both seed clashes and
  within-batch collisions when Enterprise has duplicate sequence values.

Made-with: Cursor

2026-04-19 21:33:26 -04:00

..

__init__.py

feat(fusion_accounting_followup): migration wizard backfill from account_followup

2026-04-19 21:29:38 -04:00

account_move_line.py

feat(fusion_accounting_followup): inherit account.move.line for level tracking

2026-04-19 20:47:37 -04:00

fusion_followup_cron.py

feat(fusion_accounting_followup): 2 cron jobs (daily scan + weekly risk refresh)

2026-04-19 21:04:37 -04:00

fusion_followup_engine.py

test(fusion_accounting_followup): engine integration tests for full lifecycle

2026-04-19 20:54:13 -04:00

fusion_followup_level.py

feat(fusion_accounting_followup): fusion.followup.level definition model

2026-04-19 20:43:51 -04:00

fusion_followup_run.py

feat(fusion_accounting_followup): fusion.followup.run audit model

2026-04-19 20:44:39 -04:00

fusion_followup_text_cache.py

feat(fusion_accounting_followup): LLM text cache model

2026-04-19 20:45:27 -04:00

fusion_migration_wizard.py

fix(fusion_accounting_followup): seeded levels + migration idempotency

2026-04-19 21:33:26 -04:00

res_partner.py

feat(fusion_accounting_followup): inherit res.partner with follow-up state

2026-04-19 20:46:08 -04:00