Add Priority Matrix tool

[02karthik]

What is this tool?

Priority Matrix — a productivity tool that helps you triage your to-dos with the classic Eisenhower method. Add a task, drop it into one of four quadrants by urgency and importance — Do First, Schedule, Delegate, or Eliminate — drag tasks between quadrants as priorities shift, check them off, and watch a completion bar fill up. It's aimed at anyone doing knowledge work in Hillnote who wants to decide what to actually work on now instead of just keeping a flat to-do list. Everything runs locally and persists in localStorage (priority-matrix:v1).

Why this one: the catalog has trackers, timers, and writing/reading helpers, but nothing for task triage / prioritisation — a core knowledge-work need that fits Hillnote's markdown-native workspace. The 2×2 grid also reads beautifully in the 800×500 card. It follows the Hillnote design system (azure primary #4d63ff, cool-mist canvas, near-black ink, 24px card radius, Manrope display + Inter body).

Checklist

• It's a single file: priority-matrix/index.html with all CSS + JS inline.
• It is fully self-contained / offline — no remote fonts, scripts, styles, images, fetch, or import.
• No analytics, trackers, or phone-home behavior.
• Added a screenshot at screenshots/priority-matrix.webp (via npm run screenshot priority-matrix).
• Registered the tool in tools.json (dir matches the folder name).
• Bumped the top-level catalogVersion (21 → 22).
• New tool, so per-tool version is 1.
• npm run validate passes locally (✓ catalog valid — 28 tool(s), catalogVersion 22).

Notes for reviewers

• Interaction: tasks are placed via the "Add to:" quadrant picker (works everywhere, no drag required) and can be reassigned by HTML5 drag-and-drop between quadrants on desktop. Checking a task strikes it through; the footer shows a live "N of M done" progress bar with a Clear completed action.
• Robustness: load() validates persisted state — it drops any task whose quad isn't a known quadrant and coerces types, so a corrupted localStorage entry can't break the render.
• No obfuscation / no network: plain vanilla JS, no eval/new Function/timers-with-strings, no fetch/import — clean against the validator's security scan.
• Heads-up on branch scope: this feature branch also still carries two earlier, not-yet-merged-to-main tools (Metronome, Unit Converter), so the diff against main shows all three. Only the Priority Matrix files are new in this change; the other two went through their own earlier reviews.

---

Generated by Claude Code