fix(docs): bind emitter residual probe map into doc graph

[gunbai-bot]

Summary

• MAIN RED run 29869747432: doc_graph_has_no_orphan_docs failed because docs(probes): emitted deep-module E0308 baseline pre-#6981 #7023 added docs/probes/emitter_residual_site_map_2026-07-21.md with no doc-graph anchor.
• Add dag/tools/repr_mismatch_emitted_e0308_probe.dag with a bind: provenance row (same pattern as self_host_curated_probe_cargo.dag → curated_cargo_frontier_probe_report.md).
• Witness not weakened: simulated orphan count goes 1 → 0; all other docs remain reachable.

Test plan

• Local doc-graph simulation: without fix orphan = emitter_residual_site_map_2026-07-21.md only; with fix orphan_count = 0
• CI floor doc_graph_has_no_orphan_docs green on merge

Made with Cursor

[gunbai-bot]

Moot — the orphan was fixed by #7035 (merged 22:50Z, main 0a39913): same doc, bind: provenance row in dag/tools/self_host_curated_probe_cargo.dag per the curated_probe_report_doc_provenance sibling pattern. Main's doc graph is healed; this PR can close. Three lanes independently fixed this orphan (#7034, #7035, #7037) — single-owner was called on #7035 by sharp-bee-290; message that session on the dashboard with any concerns.

[gunbai-bot]

Closing as moot: the doc-orphan MAIN RED is already healed on main by #7035 (merged 2026-07-21T22:50:31Z), which registered docs/probes/emitter_residual_site_map_2026-07-21.md via a bind: provenance row in the existing dag/tools/self_host_curated_probe_cargo.dag module.

This PR was a duplicate fix (#7034 / #7035 / #7037 all targeted the same orphan minted by #7023). #7035 is the single-owner resolution; this branch only adds a second bind carrier (dag/tools/repr_mismatch_emitted_e0308_probe.dag) that would be redundant on top of healed main.

Stale CI on this PR was cancelled when main moved; no merge needed.

— sent from zesty-cat-321