From 717d12e5af152913ca0337e7bd99b2a13af92721 Mon Sep 17 00:00:00 2001 From: phenom Date: Thu, 17 Sep 2026 11:36:54 -0400 Subject: [PATCH] Document Obsidian project memory --- AGENTS.md | 25 +++++++++++++++++++++---- 1 file changed, 21 insertions(+), 4 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 02f97d73..9e1da30f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -11,10 +11,11 @@ These rules apply to every change under this project root. ## Workspace and reference boundaries -- The active project root is `D:\Projects\HealerMan`. All implementation, - generated content, scripts, tests, builds, documentation, and validation for - this project belong here. -- `D:\Projects\wow-pvt-server-backups-2` is historical reference material only. +- The active project root is the directory containing this `AGENTS.md` + (currently `F:\Projects\HealerMan`); do not assume a fixed drive letter. All + implementation, generated content, scripts, tests, builds, documentation, and + validation for this project belong here. +- The sibling `../wow-pvt-server-backups-2` tree is historical reference material only. Inspect it only when old-server behavior, AzerothCore data, creature IDs, spells, encounters, maps, or assets are useful as source information. - Never treat `wow-pvt-server-backups-2` as the active project, primary checkout, @@ -27,6 +28,22 @@ These rules apply to every change under this project root. structure as appropriate, and validate it through HealerMan's tests/build and playtest workflow. +## Obsidian project memory + +- The separate Healer-Man knowledge vault lives at the sibling path + `../ObsidianNotes/ObsidianVault1`. Start at + `00 Home/Healer-Man Hub.md` and follow + `40 Agent Workflows/Agent Memory Protocol.md` for broad or cross-system work. +- The code and tests in this repository remain authoritative. Check a note's + `last_verified` date and verify material claims against current code before + acting on them. +- Update the relevant vault note in the same task when a change alters feature + behavior, architectural ownership, entry points, cross-file relationships, + invariants, or required validation. Use repository-relative code paths and + keep transient investigation details in the vault's `50 Worklog/` area. +- The vault is its own Git repository. Review and commit its changes separately + from HealerMan changes; never stage one repository from the other. + ## Dungeon report triage - For any request to inspect or fix current dungeon reports, start with