Khalim Conn-Kowlessar 0b52a28808 Read the property selection from task.inputs; route takes only task_id 🟩 ... Per PR review: the FE writes the selection config ({portfolio_id, property_ids?, select_all?}) into the FE-owned task.inputs and passes only task_id, so a large hand-picked selection never travels in an HTTP body. The route reads task.inputs, resolves to landlord_property_ids, caps, and pins the recipe onto sub_task.inputs as before. Declares the FE-owned inputs column on the TaskRow mirror so the backend can read it and the test schema builds it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-08 10:41:14 +00:00
..
documents	Read the property selection from task.inputs; route takes only task_id 🟩	2026-07-08 10:41:14 +00:00
modelling	Legacy property columns no longer resolve type or built form 🟥	2026-07-07 12:49:19 +00:00
__init__.py	No filters resolves the whole portfolio minus deletions 🟥	2026-07-07 11:32:10 +00:00