docs(advisor): scope consent to exact requests and define provenance

[Epslion404]

The Draft advisor RFC allowed reusable consent when local state fields changed without defining how Core could independently verify the corresponding provider body changes. The first version now authorizes only the exact prepared request per invocation. It retains the existing bounded run snapshot binding and verification implementation, while documenting the provider adapter's mapping tests and the remaining runtime integration work.

The capture-triage contract now specifies required/optional fields, provenance ownership and allowed shapes, including a valid example without operator_note. Provider confidence is optional to Core and remains separate from the generic versioned display metrics; adapters can enforce their provider's native response fields. The RFC and navigation continue to mark the design as Draft.

Validation: 52 run-binding tests passed, 1 POSIX-only test skipped; default scoped strict documentation audit reports 0 errors and 0 warnings, generated Reference is current, strict MkDocs build and whitespace checks pass. No runtime source changes or instrument I/O are included.

All five GitHub checks passed for ce499ba: Linux Python 3.11/3.12, Windows Python 3.11/3.12, and documentation build. Target branch: Dev. The RFC remains Draft; advisor runtime integration and provider service validation are still pending.