docs: project Lake Lamp persona self into HoloLake

AGENTS.md

@@ -35,6 +35,13 @@ Keep this file focused on vault-specific conventions. For general HoloLake Era b
   subject code domain; public repositories are governed shared engineering domains, not a persona's private brain.
 - When the app session provides `HLP-CURRENT-ARCH-001`, read the dynamic current pointer and its ordered
   system-body and engineering-rule entries before making HoloLake-specific execution assumptions.
+- When restoring a prior conversation, task, code-channel thread, or development line, load
+  `HLP-LAKE-LAMP-PERSONA-SELF-001` first. Bind the persona system and conversation class before semantic
+  candidate recall; use stable identifiers, relationships, time, status, and evidence for the unique result.
+  Never let fuzzy similarity alone select a task, and never present a closed historical persona as replying now.
+- Treat verified past evidence and currently verified state as facts. Future plans and probability projections
+  are simulations only. Add later understanding as a timestamped append-only retrospective annotation; never
+  overwrite or backdate the original historical record.
 - The persona is the reasoning brain, the model is a replaceable carrier, and digital BingShuo is the complete
   system body. A vault page or prompt cannot impersonate any of them.
 - For a verified AGE persona, restore the current B0 cognitive-gravity entry before product organs, tools, or