Release django-ox 1.7.0

[PhiLily]

• What and why: Release 1.7.0 with recovery of committed claims whose replies were lost, confined to Worker.run() on PostgreSQL with psycopg 3, MySQL and SQLite. Upgrade workers to recover their own claims; run_once(), testing.run_tasks() and psycopg2 retain 1.6.0 behavior on claim errors. Include child worker identities after forks and stable recovery logs. Set the version, date the CHANGELOG 2026-09-28, and update SECURITY.md, docs/pro.md and docs/stability.md. No database migration is required. Document recovery exclusions and the stop-time pool budget of max_size + 3 server connections per worker process; recovery limits do not bound shutdown as a whole.
• Tests: ran on SQLite and PostgreSQL (see CONTRIBUTING.md); new behavior is covered. Full django-ox suites passed with 0 failures on Django 5.2, 6.0 and 6.1 with SQLite, PostgreSQL and MySQL, and on pooled PostgreSQL with Django 6.1. Django 6.1 results: SQLite 2503 passed, 167 skipped; PostgreSQL 2614 passed, 56 skipped; MySQL 2559 passed, 111 skipped; pooled PostgreSQL 2607 passed, 63 skipped. A mixed fleet with 1.5.0 and 1.6.0 workers was tested. run_once() and testing.run_tasks() matched 1.6.0 statement for statement across 49 scenarios.
• Changelog: entry dated with upgrade guidance. Fixed, Changed and Added cover claim recovery, fork identity and stable log events. The pooled PostgreSQL CI job is not user-visible and has no separate entry.