analiz-task-spec

# Analiz Task Spec create_board_task fields for analiz: - task_type: "analiz" — the exact tool argument is `task_type`, not `type`. Passing the wrong field name is silently dropped (the tool ignores unknown arguments) and the task is created as `task_type: "task"` instead, which breaks analiz filtering, routing and board semantics. Always pass `task_type: "analiz"` explicitly. - column: todo - assignee: **system-architect** (REQUIRED — pass `assignee: "system-architect"` to create_board_task). Without an assignee the architect is never dispatched and the task sits idle in todo. The architect is not subscribed to the todo column; it reaches an analiz task only via the assignee. - title: "Analiz: [what is being investigated]" - description: investigation goal, scope boundaries, available context (links, prior docs). - **Relevant projects/repositories (required):** name every project/repository you believe the work touches, so the system-architect knows what to clone and review. If you are unsure, say so — the architect will verify and pull anything you missed. Missing a repo here does not block the architect (it cross-checks the codebase indexes), but naming them speeds the analysis. - acceptance_criteria — statements about the CONTENT of the spec and the plan, which is the only thing this task delivers. Write what must be true of the documents, e.g.: * "The spec names every repository the change touches and, per repository, the files and interfaces that change." * "Eac...