feat: build Learning Planner evidence project

docs/project/overview.md

@@ -0,0 +1,31 @@
+# Project overview
+
+## Product
+
+Learning Planner helps one person define learning outcomes, break them into tasks and see progress without creating an account. Its primary audience is an engineer or knowledge worker who wants a lightweight plan that remains private in the browser.
+
+## Problem and outcome
+
+Learning plans often become disconnected notes. The application provides one coherent workspace containing goals, actionable tasks, deadlines, priorities and derived progress. A successful version must survive reloads, offer portable backups, recover safely from bad data and remain usable across the agreed displays and browsers.
+
+## Core user journeys
+
+1. Review the dashboard and identify the next useful task.
+2. Create, edit and delete a goal with clear validation and confirmation.
+3. Create and update tasks connected to a goal.
+4. Search, filter, sort and mark tasks complete.
+5. Export a JSON backup, validate an import and restore sample data.
+6. Use all principal workflows with keyboard and visible focus.
+
+## Acceptance criteria
+
+- A clean clone installs, checks, builds and runs using documented commands.
+- Goal/task changes persist after reload and dashboard progress is derived correctly.
+- Valid backup export/import round-trips; malformed data fails safely.
+- No page-level horizontal overflow exists at the three required viewports.
+- The same seeded core journey passes in Chromium and Firefox.
+- Edge and two physical devices have a repeatable manual protocol and cannot be marked complete without real device metadata.
+
+## Scope boundary
+
+Included: single-user browser storage, CRUD, dashboard, search/filter/sort, backup/recovery, responsive/accessibility behaviours and automated tests. Excluded: authentication, multi-user sync, cloud services, notifications and a server-side database.