sync: record tip blogllm runtime correction

This commit is contained in:
Rene Fichtmueller 2026-05-09 20:32:47 +02:00
parent a43e572946
commit 62eafa7574
2 changed files with 11 additions and 0 deletions

View File

@ -100,6 +100,12 @@ Updated: 2026-05-09 18:16 UTC
- `collectedExamples=17322`, `evalExamples=1926`, `totalExamples=19267`
- `newSinceLastTraining=0`
- `tip_llm` remains healthy with `tip-llm-v1-r1`, `activeRun=null`, `newSinceLastTraining=0`
- TIP runtime correction:
- TIP UI already referenced `fo-blog-v7`, but `/opt/tip/blog-llm-settings.json` still forced `provider=claude-code`
- old adapter bridge port `192.168.178.213:11435` was not reachable
- switched runtime and PM2 env to `BLOG_LLM_PROVIDER=ollama`, `OLLAMA_URL=http://192.168.178.213:11434`, `OLLAMA_LLM_MODEL=fo-blog-v7`
- restarted `tip-api` and `tip-scraper-daemon`
- verified from Erik that `fo-blog-v7` answers through the TIP path with exact `TIP-FO-BLOG-V7-READY`
- open:
- run the same end-to-end custom-worker/adoption path for `magatamallm`
- complete dual-Gitea mirroring as separate infrastructure closure item

View File

@ -39,6 +39,11 @@ Date: 2026-05-09 18:07 UTC
- `modelVersion=tip-llm-v1-r1`
- `activeRun=null`
- `newSinceLastTraining=0`
- TIP runtime was corrected after adoption:
- `/opt/tip/blog-llm-settings.json` now uses `provider=ollama`, `ollamaModel=fo-blog-v7`
- PM2 process env now uses `OLLAMA_URL=http://192.168.178.213:11434`
- PM2 process env now uses `BLOG_LLM_PROVIDER=ollama`
- Erik-to-Mac smoke against `fo-blog-v7` returned exact `TIP-FO-BLOG-V7-READY`
## Decisions