David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

memory: put the fence-vs-command distinction in the description, where recall reads it

Browse Source 
The amendment stated the rule in the body, but the frontmatter description —
which is what recall matches on — still described only the July note. A rule
that only exists below the fold is a note.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T1i5VRfHjD79hfaXjWsBXA
This commit is contained in:
David F Glidden
2026-09-10 19:42:29 +02:00
co-authored by Claude Opus 5
parent fdc3c72081
commit 9c826d1680
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/feedback-governance-drafting-copy-paste-clean.md
+1 -1
View File
@@ -1,6 +1,6 @@
--- ---
name: feedback-governance-drafting-copy-paste-clean name: feedback-governance-drafting-copy-paste-clean
description: "Draft PENDING/REVIEWED entries for steward placement as copy-paste-CLEAN blocks — plain `## REVIEWED-N` headers, no bold-in-blockquote display formatting that leaks into the placed record." description: "Entries go over FENCED; whitespace or line-anchored REPAIRS go over as a COMMAND — a fence renders the whitespace and the whitespace is the payload. Verify by exact-string check with a negative control; the original 'by eye' clause is SUPERSEDED (2026-09-10), because a `##` with two leading spaces renders perfectly and parses as nothing."
metadata: metadata:
node_type: memory node_type: memory
type: feedback type: feedback