fix(docs): Convert mailto links to plain text in overview.md

[doublegate]

Summary

This PR fixes broken mailto links in docs/src/security/overview.md that were causing the GitHub Actions 'Check Markdown Links' workflow to fail.

Problem

The workflow failed with:

FILE: docs/src/security/overview.md
  [✖] mailto:security@prtip.example.com → Status: 400
 
ERROR: 1 dead link found!

Root Cause

Email addresses in plain text format are automatically detected by markdown-link-check as mailto: links, which fail validation in automated CI/CD checks with Status 400.

Affected Lines:

• Line 949: Vulnerability disclosure contact
• Line 1133: General security inquiries contact

1. **Email:** security@prtip.example.com (replace with actual contact)
...
- **Email:** security@prtip.example.com

Solution

Converted 2 occurrences of email address from link-detectable format to plain text using the established obfuscation pattern:

Before:

1. **Email:** security@prtip.example.com (replace with actual contact)
...
- **Email:** security@prtip.example.com

After:

1. **Email:** security[at]prtip.example.com (replace with actual contact)
...
- **Email:** security[at]prtip.example.com

Pattern Applied: user@domain.ext → user[at]domain.ext

Verification

✅ Validated with markdown-link-check:

markdown-link-check docs/src/security/overview.md --config mlc_config.json
All links OK ✓

✅ All 13 links in file verified:

• 2 emails (converted to plain text) ✓
• 11 external/internal links ✓

Impact

• ✅ GitHub Actions 'Check Markdown Links' workflow will pass
• ✅ Security contact information remains clearly visible and human-readable
• ✅ Prevents automated mailto: link detection
• ✅ No functional changes to security reporting process
• ✅ Minimal change: 1 file, 2 lines

Historical Context

This fix follows the established project pattern for handling mailto links - this is the 4th consecutive fix in the series:

Previous mailto fixes:

1. Commit 78c92f2: "fix(docs): Convert mailto link to plain text in audit-log.md"
2. Commit edaac3a: "fix(docs): Convert mailto link to plain text in security-model.md"
3. Commit 85525e0: "fix: Remove invalid mailto"
4. This PR: "fix(docs): Convert mailto links to plain text in overview.md"

Consistency: All security-related email addresses now use the same [at] obfuscation pattern across:

• docs/src/security/overview.md (this PR - 2 occurrences)
• docs/src/security/security-model.md (previously fixed)
• docs/src/security/audit-log.md (previously fixed)

Quality Assurance

• ✅ Email addresses remain human-readable
• ✅ Security reporting instructions unchanged
• ✅ No other mailto links remaining in file
• ✅ Follows project documentation standards
• ✅ Consistent with established mailto link handling pattern
• ✅ Used replace_all for consistency across both occurrences
• ✅ Comprehensive commit message with analysis

Files Changed

Total: 1 file modified

• docs/src/security/overview.md (2 lines changed)

Commit

b2f2d11 - fix(docs): Convert mailto links to plain text in overview.md

---

Ready for Review ✅

[github-actions]

🤖 Hi @doublegate, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[gemini-code-assist]

Summary of Changes

Hello @doublegate, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a recurring issue where email addresses in markdown files are incorrectly interpreted as mailto: links by the CI/CD link checker, causing workflow failures. By converting the email addresses in docs/src/security/overview.md to a plain text, obfuscated format (user[at]domain.ext), the PR ensures the link validation passes, maintains human readability for contact information, and upholds consistency with the project's established documentation standards for handling such cases.

Highlights

• CI/CD Workflow Fix: Resolved a failing GitHub Actions 'Check Markdown Links' workflow by preventing automatic detection of email addresses as mailto: links, which previously caused a Status 400 error.
• Documentation Update: Converted two instances of security@prtip.example.com to security[at]prtip.example.com in docs/src/security/overview.md to ensure the markdown link validation passes.
• Consistency with Project Standards: Applied an established project pattern for email obfuscation, aligning this document with previous fixes in other security-related markdown files and maintaining human readability.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively resolves the failing 'Check Markdown Links' workflow by converting mailto: links into plain text, which is a good approach. The change is consistent with the project's established pattern for handling email addresses in documentation. I have one suggestion to improve the consistency of placeholder notations.

[Copilot]

Pull Request Overview

This PR fixes broken mailto links in the security documentation by converting email addresses from security@prtip.example.com to security[at]prtip.example.com, preventing markdown link checkers from treating them as mailto: links that fail validation.

Key Changes:

• Converted 2 email addresses in overview.md to use [at] obfuscation pattern
• Maintains human readability while preventing automated link detection
• Follows the established pattern from previous security documentation fixes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

There's an inconsistency in the email domain used across security documentation. This file uses security[at]prtip.example.com, while other security documentation files (audit-log.md, security-model.md, and vulnerability-disclosure.md) consistently use security[at]prtip.dev.

Consider updating both occurrences in this file to use security[at]prtip.dev for consistency across all security documentation, or document why prtip.example.com is used specifically in this file.

[doublegate]

@copilot open a new pull request to apply changes based on this feedback

[Copilot]

@doublegate I've opened a new pull request, #9, to work on those changes. Once the pull request is ready, I'll request review from you.