Resolve worktree-aware Mnemosyne collection names

Add resolveProjectCollectionName which uses git rev-parse --git-common-dir to find the durable project directory from any linked worktree, preventing memory loss across worktree switches.\n\n- Replace naive basename(cwd) lookup with git-common-dir resolution\n- Add normalizedProjectCollectionName helper\n\nDocs:\n- Document Attached Workflow persistence and Verified Plan semantics in CONTEXT\n- Update TODO memory bug description from stale install.sh entry\n- Reset 05-phone-ideation plan to ready_for_work with abandoned worktree\n- Add attached-mode-prd.md

Author: gandazgul

CONTEXT.md

@@ -474,6 +474,12 @@ command definition, prompt command
 - During an **Attached Workflow**, the **External Agent Host** supplies every model call while RunWield remains the
   authority for durable Plans, Plan Lifecycle, review, validation outcomes, recovery evidence, Work Records, and
   organizational memory.
+- An **Attached Workflow** persists structured workflow evidence and durable artifacts without copying the **External
+  Agent Host** conversation transcript; ordinary host conversations remain outside RunWield entirely.
+- Planned implementation in an **Attached Workflow** uses a RunWield-owned worktree by default and may use an **External
+  Agent Host** worker while preserving the invoking host conversation.
+- A **Verified Plan** has the same meaning in Attached, Managed, and Native experiences; host limitations cannot weaken
+  Workflow Validation semantics.
 - **Attached Mode** is a durable first-class product mode; movement to Managed or Native experiences is an optional
   progression rather than a prerequisite for complete Attached workflows.
 - An **External Work Source** owns demand management, while RunWield owns planning, execution, Plan Lifecycle, and

TODO.md

@@ -2,7 +2,8 @@
 
 ## Bugs
 
-- [ ] Install.sh should init mnemosyne global collection with `mnemosyne init --name global`
+- [ ] Memories are being stored and then lost in worktrees, mnemosyne is full of collections named after work trees. the
+      memory_* tools should be worktree aware and store in the projects;s collection not a worktree's collection
 - [ ] CONTEXT-FORMAT file is not extracted on a fresh install.
 
 - [ ] P0 before marking a plan as verified we need to check that: all changes in the worktree were actually committed,