Delete column

This irreversible action removes one column definition and its stored values. Resolve the exact table and column and obtain explicit user authorization before calling it. Developer keys require columns:write; the actor must have access to the current organization's table, and the column must belong to that table. System columns cannot be deleted.

The existing API remains a bodyless DELETE with the synchronous {"deleted":true} receipt. The definition is removed immediately, then active work is cancelled. Stored-cell and row-view cleanup can continue in the background; the response includes no polling-job or operation-run ID and does not establish that cleanup finished. If an error follows an uncertain request, inspect the current table schema before retrying.

Native Command Center operation research_table.delete_column uses delete_table_column under the existing sensitive-action approval policy: ordinary Approve for me asks for confirmation, while explicit Run without asking retains its existing global authority. The host binds a semantic target fingerprint and rejects a changed column before deletion; a stale approval cannot cancel newer work. This native approval flow does not add an approval-token or fingerprint field to the public DELETE API. Backend publication and deployment are separate; inspect the selected server's capabilities for availability.

The existing CLI command is autotouch columns delete --table-id <TABLE_ID> --column-id <COLUMN_ID> --yes. Its destructive --yes flag is required; supply it only after the user approves this exact target. To hide a column while retaining values, use autotouch columns hide instead.