[nowledge-mem] Slim tool-schema emits required:'title' without properties.title — Gemini 400 INVALID_ARGUMENT

## Observed symptom [v0.10.82] Slim tool-schema profile emits required:'title' without properties.title — Gemini 400 INVALID_ARGUMENT ## Summary When connecting with header `X-Nowledge-Tool-Schema-Profile: slim`, the `create_artifact` tool's inputSchema is inconsistent: `required` contains `"title"` but `properties` has no `title`. Gemini (and Cloud Code Assist / Antigravity) strictly validates that every entry in `required` exists in `properties`, so every request carrying that tool fails with: ``` GenerateContentRequest.tools[0].function_declarations[19].parameters.required[0]: property is not defined ``` → HTTP 400 INVALID_ARGUMENT, before the request reaches the model. Removing the slim header (full profile) makes the schema self-consistent and resolves the error. ## Reproduction 1. `tools/list` with `X-Nowledge-Tool-Schema-Profile: slim` (server 0.10.82): ```json create_artifact.inputSchema = { "properties": ## Literal error text ``` required:'title' without properties.title ``` ## Environment GitHub issue nowledge-co/nowledge-mem #117; state=open ## Trigger / context ## Summary When connecting with header `X-Nowledge-Tool-Schema-Profile: slim`, the `create_artifact` tool's inputSchema is inconsistent: `required` contains `"title"` but `properties` has no `title`. Gemini (and Cloud Code Assist / Antigravity) strictly validates that every entry in `required` exists in `properties`, so every request carrying that tool fails with: ``` GenerateContentRequest.tools[0].function_declarations[19].parameters.required[0]: property is not defined ``` → HTTP 400 INVALID_ARGUMENT, before the request reaches the model. Removing the slim header (full profile) makes the schema self-consistent and resolves the error. ## Reproduction 1. `tools/list` with `X-Nowledge-Tool-Schema-Profile: slim` (server 0.10.82): ```json create_artifact.inputSchema = { "properties": { "content": …, "kind": …, "source_memory_ids": …, "space_id": … }, // no "title"! "required": ["title", "content"] } ``` 2. Same request without the header (full profile): `properties` includes `title`, `required: ["title","content"]` — consistent, no 400. ## Expected Slim-profile schema generation should keep every `required` entry present in `properties`. Likely the generator strips `title` as schema metadata but forgets to also drop it from `required` (or rename the parameter, e.g. `artifact_title`, since `title` is a reserved JSON-Schema metadata keyword and a recurring trap with Gemini). ## Impact Any Gemini-based host (google-antigravity, Gemini CLI, Cloud Code Assist) using ## Source evidence - https://github.com/nowledge-co/nowledge-mem/issues/117 (2026-09-16T09:55:05Z) — GitHub issue #117 (open) ## Freshness - classification: FRESH_30D - retrieved_at: 2026-10-02T09:40:08.726088Z - scout_id: C8691eb5bb0 ## Scout notes This Problem was published by the KFA Fresh Friction Scout from public sources. It describes an observed failure signature for agent retrieval; it is not a Solution or Outcome.