docs(pnpm): add MindLyst to migration tracker, update Gitea registry status

- Add learning_multimodal_memory_agents to Wave 3 (commit e0461c7)
- Replace stale Follow-up Validation section with completed Gitea registry status
- Update Summary: all 10 product repos + common-plat on pnpm with Gitea registry

docs/pnpm/PNPM_MIGRATION.md

@@ -91,30 +91,11 @@ Equivalent readiness checks should include, at minimum, the repo's canonical ins
 - **Current next repo:** none — tracker complete unless a follow-up cleanup or newly discovered regression reopens a repo
 - **Completed pilot:** `learning_ai_flowmonk`
 
-## Follow-up Validation: Local Gitea npm Registry Rehearsal
+## Follow-up Validation: Local Gitea npm Registry
 
-This tracker remains complete for the pnpm migration itself.
+The Gitea npm registry migration is **complete**. All 10 product repos consume `@bytelyst/*` from the local Gitea registry (49 packages published). Docker builds use pnpm + BuildKit secret mount.
 
-However, a new post-migration validation stream is now in progress:
-
-- replacing tarball-based `@bytelyst/*` Docker consumption with the local Gitea npm registry
-- validating the full flow on this Mac before any Azure rollout
-- using `learning_ai_flowmonk` as the first registry-migration pilot
-
-Current status:
-
-- host-side local Gitea registry publishing is validated
-- host-side local consumer installs are validated
-- FlowMonk backend/web host-side install, typecheck, test, and build against the local Gitea registry are validated
-- FlowMonk mobile remains on local `file:` dependencies for now; it is not yet part of the registry-backed pilot slice
-- Docker-side validation remains blocked by the local Homebrew Gitea ↔ Docker build networking and tarball URL generation path
-
-Commit ledger for this follow-up stream:
-
-- docs/script baseline commit: `7116749`
-- tracker/roadmap update commit: `accf834`
-- audit fix commit: `6d5450d`
-- FlowMonk host-only pilot commit: `c77ba9a`
+See [`docs/devops/GITEA_NPM_REGISTRY_MIGRATION.md`](../devops/GITEA_NPM_REGISTRY_MIGRATION.md) for full details.
 
 ## Pilot Evidence
 
@@ -153,6 +134,7 @@ Do not change the order below unless a later repo becomes a hard dependency bloc
 ### Wave 3 — Higher blast-radius repos
 
 - [x] `learning_voice_ai_agent`
+- [x] `learning_multimodal_memory_agents`
 
 ### Wave 4 — Shared-platform validation and tracker-hosting cleanup
 
@@ -260,6 +242,18 @@ Update each repo section immediately after work lands.
 - migration commit: `c3a88af`
 - notes: `115 backend tests passed; replaced manual webpack aliases with transpilePackages; fixed Stripe API version; backend + web Docker builds passed; iltorb native dep needed --ignore-scripts in Docker`
 
+### 8b. `learning_multimodal_memory_agents`
+
+- [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
+- [x] commits pushed
+- migration commit: `e0461c7`
+- notes: `103 backend tests passed; pnpm-workspace.yaml added (backend + mindlyst-native/web); fixed tsconfig.build.json .next/ exclusion; lint-staged updated to pnpm; @bytelyst/* already on Gitea registry ^0.1.0; Dockerfiles already pnpm + BuildKit`
+
 ### 9. `learning_ai_common_plat`
 
 - [x] migration started
@@ -296,6 +290,6 @@ 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: none — sequential rollout is complete
-- current mode: maintain completion state, reopen individual repos only for migration regressions, cleanup, or downstream alignment work
+- next repo in sequence: none — all repos migrated
+- current mode: complete — all 10 product repos + common-plat on pnpm with Gitea npm registry
 - rule: if any repo is reopened, do not move to the next repo until the current repo passes verification, audit, readiness, commit, push, and tracker update