[mileo]

Standard migration from 19.0 (history kept with git format-patch/git am), pre-commit auto fixes in a separate commit.

Changes for 20.0:

• ir.model.access.csv replaced by ir.access.csv;
• age computed with fields.Date.today() (ruff DTZ005);
• USAGE with the 20.0 path and a screenshot.

Installs and passes its tests on Odoo 20.0 with no warnings in the log.

[mav-adhoc]

Tested on Odoo 20.0: installs clean on a fresh database and the 4 tests pass. The ir.access.csv conversion matches the core 20.0 format and keeps the same permissions as 19.0.

Two minor notes:

• The [MIG] commit also adds readme/USAGE.md and a new screenshot that were not in 19.0. Those are improvements and usually go in a separate commit.
• Pre-existing, not from this migration: base.group_user gets read access on hr.employee.relative with no domain, so any internal user can read the relatives of every employee over RPC (the form page is restricted to hr.group_hr_user, so the UI does not show it). Worth a follow-up issue.

[mav-adhoc]

Reviewed against 19.0 and the 20.0 core. Installs clean on a fresh 20.0 database and the 4 tests pass. The 19.0 history is complete in the branch, the ir.access.csv conversion keeps the same groups and operations, and the three core fields the module hides (spouse_complete_name, spouse_birthdate, children) are still in the same form view in 20.0. Nothing blocking.

Two non-blocking notes, both already mentioned above: the [MIG] commit also adds readme/USAGE.md and a screenshot that did not exist in 19.0, and it changes _compute_age from datetime.now() to fields.Date.today() — asked for by the linter, not by the version jump; the resulting years/months/days do not change.

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖