py-v1.13.5

Fixed

• blast-radius had no target for a RemoveField once the field was gone
  from models.py (#140). That is the normal state after makemigrations,
  and exactly when code still reading the column breaks, but migration-risk
  emitted nothing for it, so blast-radius never scanned. It now emits an
  info risk, remove_field, which blast-radius --severity info (or all)
  turns into a target listing the remaining references. migration-risk --severity info shows one more line per dropped column. The MCP
  blast_radius tool also rejects an unknown severity with an
  INVALID_SEVERITY error instead of silently treating it as critical.

• DBML ER export noted model line numbers 0-based (#139). The
  Note: 'line N of app/models.py' in er --format dbml pointed one line
  above the class, while every other formatter prints 1-based lines. The
  note now uses the same 1-based number.