Ziyang Guo 0024d3a8de fix(stat): put mtime in the answer where the job description promises it ... The ``stat`` job is advertised to agents as "Stat path (size, mtime, exists, is_dir, is_file)", but the answer only ever carried the path, type and size — ``mtime`` lived solely in metadata, and MCP returns only ``response.answer``. So an agent asking how fresh a file is got no answer, even though the tool description told it the field was there. Render mtime in both branches of the answer: stat: topics/n.md (file, 20 bytes, mtime 2026-09-21T15:50:52.880316) stat: topics (dir, mtime 2026-09-21T15:50:52.880316) The value is hoisted into a local so the answer and ``metadata["mtime"]`` are guaranteed to come from the same ``stat()`` call rather than two reads. The module docstring claimed the agent receives "size, mtime, mime type, and ... frontmatter"; it now states that size and mtime are in the answer while mime and frontmatter stay in metadata, matching reality. Metadata is unchanged, so programmatic consumers see no difference. This is the same answer-completeness class as #564, found while auditing which advertised job fields actually reach the LLM.		2026-09-21 15:53:43 +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(stat): put mtime in the answer where the job description promises it	2026-09-21 15:53:43 +08:00