Expose incomplete DELETE outcomes in SDK results #10

Priority

p0 — Existing DELETE response models discard returned failure/omission information.

Gap

DeleteResponse omits released failed_files and main unreachable_files, unflushed_nodes, cold_deleted_files, cold_files, cold_rows_not_deleted, and cold_not_examined. Route presence alone therefore overstates DELETE result fidelity. SDK model, main contract. None of the pending PRs adds these fields.

Acceptance

• Preserve server-returned partial/failure diagnostics in sync/async results.
• Test hot-only, cold omission, unflushed/unreachable cluster responses and older responses lacking fields.
• Never describe omitted/deferred rows as deleted.
• Assess explicit allow_unreachable support separately; keep existing confirmation/dry-run defaults and do not weaken safety.
• Exercise public SDK decoding against real server response fixtures before live destructive tests on isolated data.

Tracking: https://github.com/Basekick-Labs/ops/issues/40. Analysis baselines: SDK main 46d3b66 and pending PRs #2/#3/#5/#6; Arc release e83bb1e (v26.09.3) and main a63f4a8. Implementation is unscheduled; the parent analysis deadline is 2026-10-30. No owner or delivery commitment is implied.

Verification must record exact versions/commands/results and separate Manual Test from IA Test. Require sync/async cases, negative authorization/validation cases, and existing-regression preservation. Local Docker is appropriate for end-to-end server checks; inventory and clean up only test resources.