itd-44 says the planner's `_choose_candidate_kind` reads `suggested_kind`; the intent chapter says no shipped code reads that field and planning never consults it.

itd-44 says the planner's _choose_candidate_kind reads suggested_kind; the intent chapter says no shipped code reads that field and planning never consults it.

A premise contradiction (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/intents/drafts/itd-44-fourth-intent-kind-decision.md:142 — "_choose_candidate_kind reads suggested_kind but only routes values in"
• End B: .abcd/development/brief/04-surfaces/05-intent.md:93 — "no shipped code reads the field at all. Planning never consults it, defaulting a null kind to standalone."

itd-44's guard against planning a decision draft assumes the planner reads suggested_kind and could plan such a draft as standalone through an interactive prompt. 05-intent.md says no shipped code reads the field, and planning sets a null kind to standalone without consulting it. The guard is designed against a code path that, according to the intent chapter, does not exist.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 486.