docs(pnpm): update notelett migration tracker

docs/pnpm/PNPM_MIGRATION.md

@@ -86,7 +86,7 @@ Equivalent readiness checks should include, at minimum, the repo's canonical ins
 
 - **Ready for sequential rollout:** yes
 - **Ready for parallel or one-shot migration:** no
-- **Current next repo:** `learning_ai_notes`
+- **Current next repo:** `learning_ai_local_memory_gpt`
 - **Completed pilot:** `learning_ai_flowmonk`
 
 ## Pilot Evidence
@@ -112,7 +112,7 @@ Do not change the order below unless a later repo becomes a hard dependency bloc
 
 ### Wave 1 — Best next repos
 
-- [ ] `learning_ai_notes`
+- [x] `learning_ai_notes`
 - [ ] `learning_ai_local_memory_gpt`
 - [ ] `learning_ai_trails`
 
@@ -137,17 +137,17 @@ Update each repo section immediately after work lands.
 
 ### 1. `learning_ai_notes`
 
-- [ ] migration started
-- [ ] migration completed
-- [ ] repo verification passed
-- [ ] post-completion audit passed
-- [ ] `/production-readiness` or equivalent readiness checks passed
-- [ ] docs/tracker updated
+- [x] migration started
+- [x] migration completed
+- [x] repo verification passed
+- [x] post-completion audit passed
+- [x] `/production-readiness` or equivalent readiness checks passed
+- [x] docs/tracker updated
 - [ ] commits pushed
-- migration commit: `TBD`
-- fix/audit commit: `TBD`
+- migration commit: `90dd2d3`
+- fix/audit commit: `17a117f`
 - docs/tracker commit: `TBD`
-- notes: next recommended repo after the FlowMonk pilot
+- notes: `pnpm run verify` passed in `learning_ai_notes`; backend and web Docker builds passed after aligning NoteLett to the shared `.docker-deps` consumer flow and fixing `prep-consumer.sh` to pack the transitive `@bytelyst/*` closure
 
 ### 2. `learning_ai_local_memory_gpt`
 
@@ -280,5 +280,5 @@ The old product-level roadmap location now exists only as a pointer:
 
 - canonical tracker: this file
 - completed pilot: `learning_ai_flowmonk`
-- next repo in sequence: `learning_ai_notes`
+- next repo in sequence: `learning_ai_local_memory_gpt`
 - rule: do not move to the next repo until the current repo passes verification, audit, readiness, commit, push, and tracker update