Keep security reporting direct without a redundant fragment link

The consuming browser exposed an existing same-fragment navigation limitation while testing the extra lower-page backlink. Keep the existing contact directly in the new reporting section and remove the redundant lower line, rather than introduce a navigation dependency or change the Docs runtime. Preserve both adverse browser results.

Contract-Neutral: Reporting-only documentation and registered test correction; no runtime or security contract change.
Change-source: pulse-maintainer

SECURITY.md

@@ -161,7 +161,6 @@ incident, defer live checks and follow [backup safety](docs/VM_DISK_MONITORING.m
 
 **Documentation:** [Critical security notice for container deployments](#critical-security-notice-for-container-deployments)
 **Issues:** <https://github.com/rcourtman/pulse/issues>
-**Private disclosures:** [Reporting a vulnerability](#reporting-a-vulnerability)
 
 ---
 

frontend-modern/public/docs/SECURITY.md

@@ -161,7 +161,6 @@ incident, defer live checks and follow [backup safety](docs/VM_DISK_MONITORING.m
 
 **Documentation:** [Critical security notice for container deployments](#critical-security-notice-for-container-deployments)
 **Issues:** <https://github.com/rcourtman/pulse/issues>
-**Private disclosures:** [Reporting a vulnerability](#reporting-a-vulnerability)
 
 ---
 

frontend-modern/src/features/docs/__tests__/securityReportingGuide.test.ts

@@ -23,7 +23,6 @@ describe('private vulnerability reporting guidance', () => {
     // Opening the contact must not prefill credentials or diagnostic material.
     expect(contact?.getAttribute('href')).not.toContain('?');
     expect(rendered.querySelectorAll('a[href^="mailto:"]')).toHaveLength(1);
-    expect(rendered.querySelector('a[href="#reporting-a-vulnerability"]')).not.toBeNull();
   });
 
   it('separates sensitive reports from public support without requesting unsafe evidence', () => {