fix: remove dead parentId logic; clarify scope model in comments and README (v0.11.3)

- scanner.mjs: remove unused nested parentId derivation loop; replace with
  comment explaining Claude Code's actual Global→Project-only scope model
- README: tighten two misleading sentences about scope hierarchy and grouping

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: ithiria894

README.md

@@ -93,7 +93,7 @@ Global                    ← loads into EVERY session on your machine
   └─ Project              ← loads only when you're in this directory
 ```
 
-Projects inherit from Global only. Sibling projects do not inherit from each other, and nested directory structures do not create extra inheritance layers — the sidebar groups them visually, but every project's parent is Global.
+Projects inherit from Global only. Sibling projects do not inherit from each other — filesystem nesting does not create extra inheritance layers. CCO may group projects by path for navigation, but Claude Code scope inheritance is always Global → Project only.
 
 Here's the problem: **Claude creates memories and skills in whatever directory you're currently in.** You tell Claude "always use ESM imports" while working in `~/myapp` — that memory is trapped in that project scope. Open a different project, Claude doesn't know it. You tell it again. Now you have the same memory in two places, both eating context tokens.
 
@@ -143,7 +143,7 @@ CCO connects to every MCP server, retrieves actual tool definitions, and runs th
 ## How It Works
 
 1. **Scans** `~/.claude/` — discovers all 11 categories across every scope
-2. **Resolves the scope hierarchy** — determines parent-child relationships from filesystem paths
+2. **Resolves project scopes** — scans projects from filesystem paths, maps them to Claude Code's Global/Project scope model
 3. **Renders a three-panel dashboard** — scope tree, category items, detail panel with content preview
 
 ## Platform Support

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcpware/claude-code-organizer",
-  "version": "0.11.2",
+  "version": "0.11.3",
   "description": "Organize all your Claude Code memories, skills, MCP servers, commands, agents, rules, and hooks — view by scope hierarchy, move between scopes via drag-and-drop",
   "type": "module",
   "files": [

package.json

@@ -281,16 +281,12 @@ async function discoverScopes() {
     return a.realPath.localeCompare(b.realPath);
   });
 
-  // Build parent-child relationships based on path nesting
+  // Claude Code has two scopes: User (global) and Project.
+  // Every project's parent is always global — there is no intermediate workspace scope.
+  // Filesystem nesting (e.g. CompanyRepo/api inside CompanyRepo/) does NOT create
+  // inheritance between projects; the sidebar may group them visually but Claude Code
+  // loads each project's .claude/ independently alongside ~/.claude/.
   for (const entry of projectEntries) {
-    // Find parent: the deepest existing scope whose realPath is a prefix of this one
-    let parentId = "global";
-    for (const existing of scopes) {
-      if (existing.repoDir && entry.realPath.startsWith(existing.repoDir + "/")) {
-        parentId = existing.id;
-      }
-    }
-
     scopes.push({
       id: entry.encodedName,
       name: entry.shortName,