feat: add progression readiness api

.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 4 planning: Progression.
+**Current focus:** Phase 5 planning: Ontology and Learning Materials.
 
 ## Current Decisions
 
@@ -27,14 +27,16 @@ interview-ready after each short practice loop.
 - Phase 3 learner memory is implemented and verified with evidence-backed
   in-memory profiles, mastery, misconceptions, interventions, and review
   schedules.
+- Phase 4 progression is implemented and verified with readiness map and next
+  challenge APIs derived from learner memory evidence.
 
 ## Next Actions
 
-1. Plan Phase 4 progression with GSD.
+1. Plan Phase 5 ontology and learning material ingestion with GSD.
 2. Keep `docs/planning/WORKFLOW_CONTRACTS.md` aligned with Go structs during
    future workflow implementation.
-3. Decide whether Phase 4 readiness map reads directly from learner memory or
-   introduces a derived progression projection.
+3. Decide the MVP ontology storage boundary before accepting uploaded source
+   materials.
 
 ## Validation Log
 
@@ -51,6 +53,9 @@ interview-ready after each short practice loop.
 - 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.
+- 2026-04-26: Phase 4 implementation verified with `go test ./...`,
+  `openspec validate bootstrap-job-tutor-platform --strict`, live readiness and
+  next-challenge smoke, and Go source line-count check.
 
 ---
 *State initialized: 2026-04-26.*