DOCA structured-tools contract

Where to start: Reach for this skill whenever a workflow in another skill says "prefer the structured tool per doca-structured-tools-contract". Read ## The agent behavior contract first; then drill into the matching schema in ## Schemas. If the host has the structured tool, prefer its output. If it does not, fall back to the manual command chain in the same schema section. Always report which path was taken so the user can fix the gap (or so a future bundle update can detect that the structured path was never tried).

Scope boundary. Writing library code ("write packet-steering code with the DOCA Flow API") is not a structured-tools question: name the library skill and stop. Checking a spec before commit ("is my DOCA Flow pipe spec valid before I commit it?") IS in scope: apply the validate-before-commit schema below.