From c7f5891c123a683f992d967c8f75f75e1589b883 Mon Sep 17 00:00:00 2001 From: Don Syme Date: Sat, 10 Oct 2026 11:18:58 +0100 Subject: [PATCH] Require Repo Assist memory write validation Make JSON parsing and the recoverable push_repo_memory check mandatory after every memory update. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- workflows/repo-assist.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/workflows/repo-assist.md b/workflows/repo-assist.md index 8b964f3..bbbfae8 100644 --- a/workflows/repo-assist.md +++ b/workflows/repo-assist.md @@ -371,6 +371,8 @@ The schema stores only: Keep notes terse and current. Replace superseded entries, remove resolved issue records and closed fix records once they are no longer needed for duplicate prevention, and never store run-by-run narration, exhaustive label histories, stale PR inventories, copied GitHub content, or facts that can be cheaply queried again. Stay within the schema's array and text limits; do not create another memory file. +After every change to `notes.json`, run `jq empty /tmp/gh-aw/repo-memory/default/notes.json`, then call `push_repo_memory`. A successful tool result is required before finishing the run. If either check reports an error, repair `notes.json` and retry both checks. Prefer `jq` with a temporary file and atomic rename over manual partial JSON edits. + **Important**: Memory may not be 100% accurate. Issues may have been created, closed, or commented on; PRs may have been created, merged, commented on, or closed since the last run. Always verify memory against current repository state — reviewing recent activity since your last run is wise before acting on stale assumptions. **Memory backlog tracking**: Records in `issues`, `fixes`, and `priorities` are **action items for you**, not just informational notes. Each run, prioritise applicable work from those fields and remove or replace entries as their state changes.