bytelyst/learning_ai_common_plat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(ecosystem): record MindLyst Phase 1 web verification (49796b1)

Browse Source 
Update tracker and execution plan with test:phase1 command, npm env
requirements, and Vitest pass evidence for note-to-memory path.

Made-with: Cursor
This commit is contained in:
Saravana Achu Mac 2026-04-03 18:13:41 -07:00
parent 8cb7043424
commit 75960d9acb
2 changed files with 12 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ecosystem/ECOSYSTEM_IMPLEMENTATION_TRACKER.md
View File

@ -120,7 +120,8 @@ Example:
- `0f469a9`
Status note:
- artifact flow is implemented end-to-end and downstream event lineage is now hardened with persisted latest-event indexes
- final end-to-end walkthrough remains open because `learning_ai_notes` and `learning_multimodal_memory_agents` still have local dependency/tooling gaps in this clone
- MindLyst web Phase 1 memory-import path is verified with focused Vitest (`npm run test:phase1` in `mindlyst-native/web` after `npm install` with `GITEA_NPM_HOST` / token); see `49796b1` in `learning_multimodal_memory_agents`
- final end-to-end walkthrough remains open while `learning_ai_notes` still has local dependency gaps in some clones
- [ ] FlowMonk plan -> ChronoMind routine -> EffoRise habit
Repos:
- `learning_ai_flowmonk`
@ -167,4 +168,5 @@ Execution status:
- NoteLett imports the latest transcript artifact into a note, emits `artifact.created` + `artifact.linked`, and now preserves upstream capture event lineage (`9ecc7c6`)
- MindLyst imports the latest note artifact into a memory proposal, emits `memory.entry.created`, and now preserves upstream note-link lineage (`0f469a9`)
- end-to-end runtime walkthrough is still pending
- repo-local verification is partially blocked in `learning_ai_notes` and `learning_multimodal_memory_agents` by incomplete local package/tooling setup
- repo-local verification for MindLyst web Phase 1 path is unblocked when private registry env vars are set (`49796b1`)
- repo-local verification in `learning_ai_notes` can still be blocked by incomplete local package/tooling setup in some clones

14
docs/ecosystem/PHASE1_TRANSCRIPT_NOTE_MEMORY_EXECUTION_PLAN.md
View File

@ -213,15 +213,17 @@ The exact commands may evolve by repo, but the evidence should include at least:
### learning_multimodal_memory_agents
- [ ] relevant backend tests covering memory creation/proposal path
- [x] relevant backend tests covering memory creation/proposal path
- [x] fixture conformance evidence recorded
Current evidence:
commit `0f469a9` added `src/lib/ecosystem-phase1.test.ts` to assert note-linked
event causation propagation and persisted latest memory event index
Blocker:
focused Vitest execution and clean typecheck are still blocked in this clone by
missing local dev dependencies (`vitest`, `@playwright/test`, and several
`@bytelyst/*` packages are not installed in the current web environment)
event causation propagation and persisted latest memory event index; commit `49796b1`
adds `mindlyst-native/web/.npmrc` (project-local registry), `test:phase1`, and
fixes the test fixture setup so Vitest can run that path reliably.
Verified (2026-04-03):
`cd mindlyst-native/web && npm install && npm run test:phase1`
(requires `GITEA_NPM_HOST` and `GITEA_NPM_TOKEN` for `@bytelyst/*`)
Result: 2 files passed, 10 tests passed (`ecosystem-phase1.test.ts`, `api-memory.test.ts`).
### Cross-repo