Update README and doc review workflow

2 files changed, 2 insertions, 1 deletions

diff --git a/AGENTS.md b/AGENTS.md
index 8cc5ea1..07547f5 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -47,5 +47,6 @@ This repository is for the creation and maintenance of Emacs 30 configuration fi
 - Document non-obvious conventions close to the relevant configuration in `config.org`.
 - Update `README.md` whenever configuration or workflow changes alter package usage, startup behavior, keybindings, directory layout, capture flow, or other documented behavior.
 - `README.md` must describe the current configuration truthfully. Do not leave stale documentation behind and do not document planned behavior as current behavior.
+- Before claiming a change is complete or asking to commit it, review whether `README.md` needs an update; if it does not, say so explicitly in the summary.
 - Update AGENTS.md when the repo workflow, Org layout, or verification expectations materially change.
 - Keep AGENTS.md concise and update it only when the repository structure or working rules actually change.
\ No newline at end of file
diff --git a/README.md b/README.md
index 66c87e4..76bfe16 100644
--- a/README.md
+++ b/README.md
@@ -83,7 +83,7 @@ This keeps daily capture fast without routing everything through Denote.
 
 ### Agenda usage
 
-The agenda is opened through `ss/open-agenda`, bound to `C-c a`. Before running `org-agenda`, the config refreshes `org-agenda-files` from the PARA directories and explicitly loads `org-agenda` so agenda-specific variables are available.
+The agenda is opened through `ss/open-agenda`, bound to `C-c a`. That command explicitly loads `org-agenda`, and the config refreshes `org-agenda-files` immediately before each `org-agenda` invocation so the agenda sees the current PARA files without relying on a fixed file list.
 
 This means the agenda reflects the current project, area, and resource files at runtime instead of relying on a fixed file list.