fix(health): drop stale ollama check, add rerank/embed-mem checks - #15
Open
SabaTech-dev wants to merge 2 commits into
Open
fix(health): drop stale ollama check, add rerank/embed-mem checks#15SabaTech-dev wants to merge 2 commits into
SabaTech-dev wants to merge 2 commits into
Conversation
Docker/GHCR require lowercase repository names. github.repository (SabaTech-dev/Alfred-Mission-Control) broke 'docker buildx build' with 'invalid tag: repository name must be lowercase', failing the SLSA Build & Attest job on every push to main. Introduce workflow-level env.IMAGE_NAME (canonical lowercase artifact name) and use it consistently for: build tags, attestation subject-name and the verification summary (which also referenced a never-pushed 'sha-' prefixed tag).
…memory TCP checks Ollama was retired on 2026-08-28; the running build still probed it and kept the dashboard permanently degraded. This adds TCP checks for the llama.cpp reranker (:8005) and memory embeddings (:8006) that replaced it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Qué
/api/healthendegradedpermanente.Por qué
El build desplegado seguía sondeando ollama muerto. Este cambio ya está corriendo en prod (build 2026-09-04 16:45, reinicio verificado:
healthy, 14 checks up) — este PR sincroniza el repo con lo desplegado.Verificación
npx vitest run src/lib/stack-health.test.ts→ 8/8npm run buildOK (build en prod 04-sep)curl localhost:3000/api/health→"status":"healthy"Nota:
tsc --noEmittiene errores pre-existentes en archivos ajenos a este cambio (agent-os/tasks,agents/statustests); el build pasa porignoreBuildErrors.