[eli32-vlc]

Summary

Sort all 105 notes in docs/.vitepress/notes/ into critical (must-read) vs non-critical (tips/enhancements). 18 notes that involve safety, malware, bootloops, account bans, data loss, fake download buttons, adware, or broken installers are now *-critical.md with their first heading ending in "Critical"; the remaining 87 keep their current names.

Critical notes render a red ⚠ Critical badge in place of the note link:

• Clicking the badge opens the same anchored popover as normal notes (FloatingVue, click-only) with title + note body + Source footer + Close only (no dismissal side-effects).
• Clicking the main entry link (e.g. Foxit) is intercepted in Layout.vue and opens a centered modal dialog (réka-ui, modeled on Base64Dialog) with a Don't show again checkbox + Cancel/Continue. Continue opens the real link in a new tab; dismissed clicks pass through. Dismissals are stored per-note in localStorage (fmhy-critical-notes-dismissed) as {noteId: contentHash} — sha256 (truncated to 12 chars) computed in utils/tooltips.ts; editing a critical note changes its hash and re-prompts all users.

Non-critical notes are untouched (existing hover/click tooltip via Tooltip.vue). 34 link occurrences across 13 docs pages updated, including 3 previously misleading [Note] labels (sanet, liteapk-modyolo, yts-yify) fixed to [Critical].

Files changed

Content (59 files)

• 18 docs/.vitepress/notes/*.md renamed to *-critical.md (content-sorted; heading updated to "… Critical")
• 13 docs pages (file-tools, mobile, gaming, privacy, reading, system-tools, video-tools, video, internet-tools, downloading, beginners-guide, sandbox, …) — link URLs + labels updated
• .github/CONTRIBUTING.md — documents *-critical.md vs *-note.md + critical: true/false frontmatter

New (5 files)

• docs/.vitepress/theme/components/CriticalBadge.vue — inline red badge + popover
• docs/.vitepress/theme/components/CriticalDialog.vue — modal dialog with targetUrl (Continue opens the link)
• docs/.vitepress/theme/composables/criticalNotes.ts — per-note localStorage ({noteId: hash}, fail-open, SSR-guarded)
• docs/.vitepress/theme/composables/criticalRegistry.ts — runtime registry so Layout.vue can populate the dialog
• docs/public/critical.svg — badge icon (same artwork as note.svg)

Modified (7 files)

• docs/.vitepress/theme/Layout.vue — capture-phase click interceptor + CriticalDialog hosting, criticalTargetUrl tracking; fallback to .critical-badge-hidden-body
• docs/.vitepress/utils/markdown.ts — critical → <CriticalBadge>, non-critical → <Tooltip> (unchanged)
• docs/.vitepress/utils/tooltips.ts — critical flag (filename convention + frontmatter override) and contentHash
• docs/.vitepress/theme/index.ts + docs/.vitepress/theme/components/VPLocalSearchBox.vue — CriticalBadge registered (global + search stub)

Test plan

• pnpm eslint clean, pnpm prettier -w ., node scripts/lint-markdown.js passes
• pnpm docs:dev --port 5173, then in preview:
  • /sandbox (has both a Critical and a non-critical example) and /file-tools / /reading:
    • Click Pangu7/Foxit (main link) → modal appears with full warning text; check Don't show again + Continue → link opens; click again → navigates directly
    • Click the Critical badge → popover appears next to the badge with same text; Close only; verify badge is unchanged after closing
    • Buster / Note icon → normal tooltip, unchanged (no red badge, no modal)
  • Search for a critical note's text → no leaked results (same as normal notes)
  • Mobile/touch, keyboard (Tab → Enter, Esc), light/dark/monolith themes, prefers-reduced-motion, forced-colors

Notes

• The repo requires Issues to be created before opening a PR (contributing guide: don't spam un-tested links). This PR is large (content + theme). Happy to discuss the critical set — I classified by content: safety/security, bans, data loss, fake buttons, adware, broken versions.