feat: add learner memory ingestion

.planning/STATE.md

@@ -7,7 +7,7 @@ See: `.planning/PROJECT.md` (updated 2026-04-26)
 **Core value:** The user should feel and prove that they are becoming more
 interview-ready after each short practice loop.
 
-**Current focus:** Phase 3 planning: Learner Memory.
+**Current focus:** Phase 4 planning: Progression.
 
 ## Current Decisions
 
@@ -24,14 +24,17 @@ interview-ready after each short practice loop.
 - Phase 1 Go backend scaffold is implemented and verified.
 - Phase 2 diagnostic interview loop is implemented and verified with in-memory
   sessions.
+- Phase 3 learner memory is implemented and verified with evidence-backed
+  in-memory profiles, mastery, misconceptions, interventions, and review
+  schedules.
 
 ## Next Actions
 
-1. Plan Phase 3 learner memory with GSD.
+1. Plan Phase 4 progression with GSD.
 2. Keep `docs/planning/WORKFLOW_CONTRACTS.md` aligned with Go structs during
    future workflow implementation.
-3. Decide whether Phase 3 learner memory remains in-memory for MVP proof or
-   introduces a small persistence boundary.
+3. Decide whether Phase 4 readiness map reads directly from learner memory or
+   introduces a derived progression projection.
 
 ## Validation Log
 
@@ -45,6 +48,9 @@ interview-ready after each short practice loop.
 - 2026-04-26: Phase 2 implementation verified with `go test ./...`, live
   `/healthz` smoke, live diagnostic create/answer/get smoke, OpenSpec, and Go
   source line-count check.
+- 2026-04-26: Phase 3 implementation verified with `go test ./...`,
+  `openspec validate bootstrap-job-tutor-platform --strict`, live diagnostic
+  answer to learner-memory smoke, and Go source line-count check.
 
 ---
 *State initialized: 2026-04-26.*