Ziyang Guo 5b2bd3aea9 fix(frontmatter-read): put the frontmatter in the answer, not just a key count ... `frontmatter_read` answered `Read frontmatter from <path> (N key(s))` and left the frontmatter itself in `metadata["frontmatter"]`. MCP returns only `response.answer`, so the LLM that asked for a file's frontmatter learned how many keys exist and nothing else — the same shape of gap #379 describes for `list`, where the caller cannot act on the result. Render each key on its own line in the answer. Values are flattened to one line each so a multi-line description cannot break the line-per-key layout: lists join with commas and nested mappings render as compact JSON. An empty frontmatter says `(no keys)` rather than trailing off after the colon. The answer also names the probed path instead of the raw input, so a suffix-less request reports the `.md` file that was actually read and the caller can follow up with `read` without consulting metadata. Structured `metadata["frontmatter"]` is unchanged, so programmatic consumers see no difference. Towards #379.		2026-09-21 14:35:08 +08:00
..
fixtures/config	fix(ci): support AgentScope 2.0.6 initialization (#457)	2026-08-19 11:33:52 +08:00
integration	feat(proactive): separate proactive refresh from auto dream (#488)	2026-09-07 17:23:37 +08:00
unit	fix(frontmatter-read): put the frontmatter in the answer, not just a key count	2026-09-21 14:35:08 +08:00