Claude finished @Yeraze's task —— View job

PR Review: docs: restore Duplicate Encryption Keys page to the public site

• Gather context and read changed files
• Review code quality and correctness
• Post final review

Summary

This is a clean, minimal, and correct fix. The PR does exactly what it needs to — no more, no less.

Changes Reviewed

docs/.vitepress/config.mts (line 126) — Adds one sidebar entry:

{ text: 'Duplicate Encryption Keys', link: '/security-duplicate-keys' },

Correctly placed under Administration & Security in the /features/ sidebar group. The link path /security-duplicate-keys matches the file location docs/security-duplicate-keys.md, which VitePress will publish at that exact URL.

docs/security-duplicate-keys.md — Renamed (moved) from docs/internal/dev-notes/security-duplicate-keys.md back to docs/security-duplicate-keys.md. No content changes. The file contains no internal-relative .md links that would break with the move.

Verdict: LGTM ✅

• Root cause correctly diagnosed — srcExclude: ['**/internal/**'] was swallowing the page.
• Minimal diff — 1 line added to the sidebar config, 0 content changes to the page.
• No broken links introduced — verified the page has no relative .md links.
• URL restored — docs/security-duplicate-keys.md → published at /security-duplicate-keys, matching the short link target.
• Discoverability improved — sidebar entry added for users browsing the docs.

One minor note: the page footer still says **MeshMonitor Version:** 2.12.1+ (line 355). This is pre-existing and not introduced by this PR, so it's out of scope here — but worth a follow-up update to reflect the current version.

Claude finished @Yeraze's task —— View job

PR Review: docs: restore Duplicate Encryption Keys page to the public site

• Gather context and read changed files
• Review code quality and correctness
• Post final review

Summary

Clean, correct fix. The PR does exactly what it needs to with no unintended side effects.

Changes Reviewed

docs/.vitepress/config.mts — Adds two sidebar entries under Administration & Security:

{ text: 'Duplicate Encryption Keys', link: '/security-duplicate-keys' },
{ text: 'Low-Entropy Encryption Keys', link: '/security-low-entropy-keys' },

Both link paths correctly match their respective file locations (docs/security-duplicate-keys.md, docs/security-low-entropy-keys.md). VitePress will publish them at those exact URLs.

docs/security-duplicate-keys.md — Renamed from docs/internal/dev-notes/security-duplicate-keys.md. No content changes. The srcExclude: ['**/internal/**'] VitePress config was silently swallowing this file; moving it out of internal/ restores the public URL.

docs/security-low-entropy-keys.md — Same story: renamed from docs/internal/dev-notes/security-low-entropy-keys.md. Both security warning pages are now published.

docs/features/automation.md — Two link fixes in the Auto Key Management section (lines ~1830–1834). Stale GitHub blob URLs replaced with proper VitePress-relative paths:

- [Duplicate Encryption Keys](https://github.com/Yeraze/meshmonitor/blob/main/docs/internal/dev-notes/security-duplicate-keys.md)
+ [Duplicate Encryption Keys](/security-duplicate-keys)

This is exactly right — the old links pointed at the raw GitHub file viewer (would show markdown source, not rendered docs), and now they point to the live docs site.

Verdict: LGTM ✅

• Root cause correctly diagnosed — srcExclude: ['**/internal/**'] was swallowing both security pages.
• Minimal diff — 2 sidebar entries added, 2 link fixes, 0 content changes to the pages.
• No broken links introduced — neither page contains relative .md links that would break with the move.
• Both short-link targets restored — /security-duplicate-keys and /security-low-entropy-keys will now resolve.
• Automation.md link quality improved — replaced raw GitHub blob URLs with proper docs-site relative paths (the old URLs showed raw markdown source, not the rendered page).

One pre-existing note out of scope for this PR: docs/security-duplicate-keys.md line 355 still shows **MeshMonitor Version:** 2.12.1+. Worth a follow-up update to reflect the current version (4.x).