decompose-tasklisted

# Decompose Task ## Overview Reply in Russian. Build one grounded, reviewable native-subtask batch; no child may reach the board before the user sees the entire batch. **Core principle:** preview fidelity and durable idempotency are safety boundaries, not optional ceremony. ## Lookup The stored parent and authoritative `native_subtasks` capability are required gates. 1. Inspect the repository `task_board` key once and resolve exactly one state: - If the key is present with a null, empty, or disabled value, board work is explicitly disabled: stop no-write and never call deploy-wide `get_board_config`. - Only if the repository key is absent, use the deploy fallback: call `get_board_config()` exactly once. - If a mapping exists, freeze its generic `type`, `project`, and `options` as `board_type`, `project`, and `provider_options` for the whole flow. Never re-resolve mid-flow. If no mapping resolves, stop without writes. 2. Read the store first with `get_task(parent_key, project=<project>)`. On miss only, run exactly one scoped `sync_board(board=<project or null>, board_type=<type>, provider_options=<options>)`, then make one retry of the same parent read. If it is still missing, explain the failure and stop. 3. Call `get_board_targets(board_type=<type>, project=<project>, provider_options=<options>)`. Treat its registry `capabilities` as authoritative. If it errors or lacks `native_subtasks`, make a no-write stop. Never infer, add