From 53a359d3e17f4183eea4dc1fdefb9efb71564238 Mon Sep 17 00:00:00 2001
From: Ziyang Guo <121015044+RerankerGuo@users.noreply.github.com>
Date: Mon, 21 Sep 2026 15:45:28 +0800
Subject: [PATCH] docs(config): match the frontmatter_read description to the
 new answer
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The job description still advertised "Read a file's frontmatter as a dict",
but the answer is now rendered `key: value` lines — the dict only survives in
metadata. An LLM choosing between `frontmatter_read` and a whole-file `read`
would expect a dict it can index into and get prose instead.

This is the wording-alignment point raised on #397, applied here before
review rather than after.
---
 reme/config/default.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reme/config/default.yaml b/reme/config/default.yaml
index 4b26a2f2..987c3d6e 100644
--- a/reme/config/default.yaml
+++ b/reme/config/default.yaml
@@ -501,7 +501,7 @@ jobs:
 
   frontmatter_read:
     backend: base
-    description: "Read a file's frontmatter as a dict."
+    description: "Read a file's frontmatter, one key: value per line."
     parameters:
       type: object
       properties: