search: Pfad und Titel vollstaendig in der Trefferzeile, Trunkierung wird benannt (schliesst #100)

Files changed:
- AGENTS.md
- CHANGES.md
- VERSION
- instructions/wiki-query/SKILL.md
- tools/CONTRACT.md
- tools/chemenu/api.py
- tools/chemenu/commands/search.py
- tools/chemenu/mcp/server.py
- tools/chemenu/search/service.py
- tools/chemenu/search/types.py
- tools/chemenu/tests/test_api.py
- tools/chemenu/tests/test_mcp_server.py
- tools/chemenu/tests/test_search.py

instructions/wiki-query/SKILL.md

@@ -34,15 +34,18 @@ invariant - rather than synthesizing a plausible-sounding answer from general kn
    ```bash
    tools/wikitool search "backup" --kind entity --subtype system
    tools/wikitool search --field entity_type=system --field '!sources' --sort -modified
-   tools/wikitool search --field tags=k8s --limit 30
-   tools/wikitool search "Longhorn" --matches      # show the matching lines
+   tools/wikitool search --field tags=k8s --limit 0   # a sweep: every match, not the first 50
+   tools/wikitool search "Longhorn" --matches         # show the matching lines
    ```
 
    `search` is read-only and exempt from the iteration budget, so searching again is always
-   cheaper than reading more.
+   cheaper than reading more. A result that hit `--limit` says so and names the total, so read
+   the last line before treating a list as the whole answer - and do not grep `kb/` yourself,
+   per AGENTS.md § Routing.
 
-3. **Read only the pages the search points at**, then follow their `related:` and `sources:`
-   entries. Check `kb/sources/` when the question is about what a specific source said.
+3. **Read only the pages the search points at** - each hit carries its full path - then follow
+   their `related:` and `sources:` entries. Check `kb/sources/` when the question is about what
+   a specific source said.
 
 4. **Answer and cite.** Name the wiki pages the answer came from, and the sources behind them.
    Hedge to what those sources carry, not to a number - see