Dashboardbyk.github.io.lore.md must always be staged, never l…

.lore.md must always be staged, never left untracked

Category: preference
Confidence: 1.00
ID: 019f84dc-3599-7c12-920f-66e9eb3e04ca
Project ID: 27022d30-10a9-49e4-8a75-dae8ea101609
Cross-project: No
Recalled in other projects: 1
Source session: 1H6zthdbm2YTrMQ2H
Created: 2026-07-21 13:27:31
Updated: 2026-07-21 13:27:31

Cross-Project Recalls

ProjectHitsLast recalled
opencode-lore 3 2026-08-07

Content

Repo convention (byk.github.io, applies generally to lore-managed repos): whenever .lore.md appears as a new/modified file (typically from a background lore migration process), it must be staged and committed alongside other changes in the same commit — never left untracked or stashed. AGENTS.md changes from the same lore migration (e.g. replacing inline knowledge sections with a pointer sentence to .lore.md) should be committed together with it, since both files are lore-managed and travel as a unit.

Move to: