Add links to discovery methods in documentation

[JensTimmerman]

Updated discovery methods with links to integration manifest documentation.

Proposed change

In the discovery documentation, link to the specifics the dev needs to implement for each specific method (Currently it's a bit hard to find since there are no direct links that the discovery needs to be put in the manifest and what functions to add for this)

Possibly something similar should be done to https://developers.home-assistant.io/docs/network_discovery ?
Or the pages/docs should be rearanged a bit so everyhthing fits better togheter? Since network_discovery perhaps could contain the part of the docs that are in the manifest doc now?

Type of change

• Document existing features within Home Assistant
• Document new or changing features for which there is an existing pull request elsewhere
• Spelling or grammatical corrections, or rewording for improved clarity
• Changes to the backend of this documentation
• Remove stale or deprecated documentation

Checklist

• I have read and followed the documentation guidelines.
• I have verified that my changes render correctly in the documentation.:
  I have not, How do I do this? The documentation states: When you create a pull request (PR), you can see a preview of the proposed changes by clicking the Deploy Preview link in the Netlify comment. But I can't find the netlify comment here.

Additional information

• This PR fixes or closes issue: fixes
• Link to relevant existing code or pull request: Added guntamatic heater integration core#167419 In this pr I was told to look into auto discovery, I initially missed the dhcp discovery option because there was no direct links to how to set this up an how it works.

Summary by CodeRabbit

• Documentation
  • Updated discovery method docs to turn protocol names into direct links to their integration configuration sections for easier navigation.
  • Corrected the mDNS/ZeroConf link and added a sentence under "Additional resources" pointing to integration manifest guidance for discovery methods.
  • Minor formatting fix at the end of the document.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4e2b1c62-e955-40c9-8146-1a66f878c2e0

📥 Commits

Reviewing files that changed from the base of the PR and between a226761 and d716fa0.

📒 Files selected for processing (1)

• docs/core/integration-quality-scale/rules/discovery.md

✅ Files skipped from review due to trivial changes (1)

• docs/core/integration-quality-scale/rules/discovery.md

---

📝 Walkthrough

Walkthrough

Converted protocol names (Bluetooth, DHCP, HomeKit, mDNS, MQTT, SSDP, USB) to links pointing at specific sections of the integration manifest docs, changed the mDNS entry to use the #Zeroconf anchor, added a manifest-docs reference under "Additional resources", and fixed EOF newline.

Changes

Cohort / File(s)	Summary
Documentation Links docs/core/integration-quality-scale/rules/discovery.md	Converted plain protocol names into documentation links targeting integration manifest sections (updated mDNS to #Zeroconf), added a sentence in "Additional resources" linking to the integration manifest docs, and fixed missing newline at EOF.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: adding links to discovery methods in documentation.
Description check	✅ Passed	The description includes proposed change, type of change with checkbox, and additional information with relevant links. However, the author did not verify documentation rendering as required by the template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/core/integration-quality-scale/rules/discovery.md`:
- Around line 16-22: The listed discovery links (Bluetooth, DHCP, HomeKit, mDNS,
MQTT, SSDP, USB) use relative paths like "docs/..." which can break in nested
docs; update each link target to use root-relative paths ("/docs/...") including
the similar occurrence around the Home Assistant docs reference at the later
section (the mention at line ~118) so all entries point to
"/docs/creating_integration_manifest#Bluetooth",
"/docs/creating_integration_manifest#DHCP",
"/docs/creating_integration_manifest#HomeKit",
"/docs/creating_integration_manifest#Zeroconf",
"/docs/creating_integration_manifest#MQTT",
"/docs/creating_integration_manifest#SSDP", and
"/docs/creating_integration_manifest#USB" respectively.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8a6e4bde-c1f9-45c9-91bc-62615e71fb40

📥 Commits

Reviewing files that changed from the base of the PR and between bdf53bc and a226761.

📒 Files selected for processing (1)

• docs/core/integration-quality-scale/rules/discovery.md