Add PDF Dark

[1436941541]

Summary

Adds PDF Dark to resources/p.ts (alphabetical position between pCloudy and pdforge).

• Name: PDF Dark
• URL: https://pdfdark.org
• Categories: Browser, Productivity, Open Source
• What it is: open-source browser-based tool that converts any PDF into a real dark-mode file. The entire conversion runs client-side via WebAssembly — your file never leaves the browser. A saturation-based algorithm preserves photos and charts in their original colors. Output is a standard PDF (not a viewer toggle), so it stays dark on Kindle, iPad, Acrobat, anywhere.
• License: MIT, source on GitHub: https://github.com/1436941541/pdf-dark

Why it belongs in dev-resources

• Open source + WebAssembly stack — same technical profile as other entries under Browser/Productivity categories.
• Useful for developers/researchers who read code-, paper-, or docs-heavy PDFs at night and want a permanent dark-mode file (not just a viewer toggle that resets per app).
• Sits naturally next to existing PDF/document tools in the list (Patterns.dev, pdforge, etc.).

Checklist

• Resource added to the alphabetically correct file (resources/p.ts)
• Entry placed in alphabetical order (between pCloudy and pdforge)
• Required fields filled: name, description, categories (max 3), url
• URL begins with https://
• No duplicate (searched README — no existing PDF Dark entry)
• npm run prettier:format ran (file unchanged — already formatted)
• README.md and /db not edited (auto-generated)

[github-actions]

New resource link: https://pdfdark.org

[github-actions]

🤖 Automated PR Validation

⚠️ Issues Found

The following issues were detected. GitHub Copilot will review this PR and report any additional issues.

Resource Validation Errors

🔤 Alphabetical Order

• a.ts:291: Resource "AntForms" should come before "AnveVoice"
• n.ts:75: Resource "NexTool" should come before "Nextradar"
• o.ts:35: Resource "Odin A" should come before "OrcaSheets"

---

📋 Request for GitHub Copilot

Review this PR and report any issues you find, including:

• Code quality and style issues
• Additional validation errors not caught by automated checks
• Best practices and improvements

---

📚 Resources:

• Contribution Guidelines
• Valid Categories

GitHub Copilot will review this PR and report any issues found.