fix: add embedding_api.base_url to /health response (closes #36)

[mfethe1]

Closes #36

Main already has graceful embedding degradation in all paths (embeddings_client.py returns None on any failure, create_memory and /search both handle None embedding). This PR adds the one missing piece: the embedding_api.base_url field in GET /health so operators can see the configured embedding endpoint at a glance.

Before:

{"status": "healthy", "version": "0.1.0"}

After:

{"status": "healthy", "version": "0.1.0", "embedding_api": {"base_url": "http://..."}}

Supersedes #39 (which targeted a diverged branch).

[chatgpt-codex-connector]

💡 Codex Review

fumemory/memu/api.py

Line 848 in 6bdf46d

"embedding_api": {"base_url": resolve_embedding_api_base()},

Redact the health endpoint base URL

Because /health is unauthenticated and intended for external probes, returning the raw EMBEDDING_API_BASE/EMBEDDING_BASE_URL value here can expose deployment details, and it can leak credentials if a custom embedding endpoint is configured with URL userinfo such as https://user:pass@host. Consider redacting credentials (or exposing only host/scheme) before including this operator-facing field.

ℹ️ 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".