release: 1.6.0

[reqsai-release-bot]

Release 1.6.0

Candidate v1.6.0-rc.1: commit e336d6d0ec955a155f493d6bf96b0c55334a4373, tree b7fe661dd1d8d435cbc1f34d2df985b612509641, build 5.

• Image: ghcr.io/kntro-soft/reqsai-api@sha256:044f55ed61efa0849e814166f965b010e0eebebef0a80e1803c51640d590001f (tag 1.6.0-rc.1, linux/arm64, version label 1.6.0)
• Verified automatically: https://github.com/Kntro-Soft/reqsai-api/actions/runs/38514021788 (prod profile on PostgreSQL + pgvector, every Flyway migration, sign-up → e-mail → sign-in → organization)

Merging into main runs Produccion (produccion.yml): it finds this candidate by tree hash, waits for approval in produccion, ships this same digest to the MVP host through reqsai-infra (database backup first), then tags v1.6.0 and opens the back-merge into develop.
A new push to release/1.6.0 builds the next candidate and updates this description.