docs: examples/chat/python dead-code audit (Task #3) (#457)

* docs: spec for examples/chat/python dead-code audit

Task #3 in the post-PR-#432 cleanup arc. Two-pass methodology
(static reference + recorded-trace coverage) producing an audit
report; removal deferred to follow-up PRs (one per cluster).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: plan for examples/chat/python dead-code audit

7-task plan: scope inventory, static reference pass, coverage
instrumentation (with static-fixture-analysis fallback), merge into
findings table, write report, open PR. Ships only the audit report;
removals deferred to per-cluster follow-up PRs.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: audit report for examples/chat/python dead code

Static-reference + trace-coverage analysis of examples/chat/python/src/.
Zero symbols recommended for removal; two LLM-exported tools flagged
"keep-with-note" because no recorded fixture invokes them
(search_documents, generate_json_render_spec). Recommends no follow-up
removal PRs; suggests follow-up fixture-coverage work instead.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: blove