Task process patch contract

# Task process patch contract

Task process patches are used by the project AI employee to propose changes to task workflows, board statuses, and transitions.

Patch format:

```text
riders-pulse-task-process-patch-v1
```

## Contract

```json
{
  "format": "riders-pulse-task-process-patch-v1",
  "schema_version": 1,
  "target": {
    "project_id": "uuid",
    "task_workflow_id": "uuid"
  },
  "operations": [
    {
      "op": "add_status",
      "client_key": "review",
      "name": "Review",
      "category": "review",
      "position": 30
    },
    {
      "op": "add_transition",
      "from_client_key": "in_progress",
      "to_client_key": "review",
      "name": "Передать на проверку"
    }
  ]
}
```

## MVP operations

- `add_status`;
- `rename_status`;
- `reorder_status`;
- `archive_status`;
- `add_transition`;
- `update_transition`;
- `delete_transition`.

## Safety rules

Forbidden by default:

- hard delete status;
- hard delete transition with active tasks unless dry-run says safe;
- move active tasks without explicit approval.

Required flow:

1. AI creates proposal.
2. Backend validates patch.
3. UI shows preview and warnings.
4. User approves.
5. Backend applies transactionally.
6. Audit/tool records are stored.

The task process patch contract is separate from `riders-pulse-workflow-patch-v1`; workflow automation patches must keep using the existing workflow patch format.