Feature/sap phase 4.1 clean

[Cheewye]

📋 Checklist de Seguridad iURi

Protección del Módulo Marino

• NO se modifica ni borra src/components/marine/*
• NO se introduce react-leaflet (usar MapLibre o Leaflet directo)
• Si hay WebSocket :8000 → está detrás de VITE_USE_IURI_WS flag
• NO se renombran vars: VITE_SIGNALK_WS, VITE_MQTT_WS, VITE_VESSEL_ID

Arquitectura General

• Sidebar/rutas: sin cambios (salvo que sea el objetivo del PR)
• i18n actualizado en todos los idiomas (es/pt/en/...)
• No se introducen dependencias de Three.js sin lazy-load y feature flag

Pruebas Locales

• npm run dev abre /dashboard sin errores en consola
• (Si stack marino levantado) scripts/sanity_stack.sh OK
• (Obligatorio) scripts/premerge_guard.sh PASS
• (Obligatorio) scripts/llm_diff_review.sh ejecutado (adjuntar salida)

Capturas

---

🧠 Salida del Guardián IA Local

Ollama LLM Diff Review

<!-- Pegar aquí la salida de: MODEL=llama3.2 bash scripts/llm_diff_review.sh -->

---

📝 Descripción de Cambios

🔗 Relacionado

Fixes #

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
21785279	Triggered	Generic Password	6415b1e	backend/services/auth_service.py	View secret
21806655	Triggered	Generic Password	3b6f2e5	deploy-dual.sh	View secret
22171238	Triggered	Company Email Password	87e0aad	docs/AUTH_ACTIVADO_PRODUCCION.md	View secret
21785330	Triggered	DeepSeek API Key	e8f3fc4	core/swarm/deepseek_integration.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[chatgpt-codex-connector]

💡 Codex Review

iuri-react-codex/swarm_core/api_memoria_viva.py

Lines 208 to 211 in 890e7d7

	"""
	from memoria_viva_db import search_similar
	results = search_similar(q, limit=limit)

Use package-qualified import in Memoria Viva search endpoint

The search route dynamically imports memoria_viva_db without the package prefix (from memoria_viva_db import search_similar). When this endpoint is hit, Python resolves imports relative to the process root, so no module named memoria_viva_db is found and the request fails with ModuleNotFoundError, leaving /iuri/memoria/search broken. Import the helper via a relative or fully qualified path (e.g. from .memoria_viva_db ...) so the module loads correctly.

---

iuri-react-codex/swarm_core/memoria_viva_db.py

Lines 256 to 260 in 890e7d7

	keywords = [w.lower() for w in text.split() if len(w) > 3][:5]
	# Buscar experiencias que contengan alguna keyword
	query = "SELECT id, user_id, text, type, response, resolved, ts FROM experiencias WHERE ("
	query += " OR ".join(["LOWER(text) LIKE ?" for _ in keywords])

Guard search_similar against queries with no keywords

The keyword extraction in search_similar discards words of length ≤3 and then unconditionally builds SQL as WHERE ( … ). For queries like "sol" or any short word, keywords is empty and the generated SQL becomes WHERE (), which SQLite rejects with a syntax error, causing the API /iuri/memoria/search to return 500. Add a fallback when no keywords remain (e.g. return [] or skip the WHERE clause) before constructing the query.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".