Interface CapabilityRequestBase

Optional playbook naming the stated intent this generation runs under — a goal, tone and mention rules the generated copy respects. It sits beside config rather than inside it because a playbook is not capability configuration: the same playbook steers whichever capability names it.

Naming one never fails the request. A playbook that is missing, inactive or not enabled for experience surfaces simply does not steer, and the capability answers exactly as it otherwise would.