docs: fix ECC setup reference drift

Author: affaan-m

.claude/rules/node.md

@@ -27,10 +27,10 @@
 
 ## Hook Development
 
-- Hook scripts receive JSON on stdin — always `const input = JSON.parse(fs.readFileSync(0, 'utf8'))`
+- Hook scripts normally receive JSON on stdin, but hooks routed through `scripts/hooks/run-with-flags.js` can export `run(rawInput)` and let the wrapper handle parsing/gating
 - Async hooks: mark `"async": true` in `settings.json` with a timeout ≤30s
 - Blocking hooks (PreToolUse, stop): keep fast (<200ms) — no network calls
-- Use `run-with-flags.js` wrapper for all hooks so `CLAUDE_ECC_MODE` gating works
+- Use `run-with-flags.js` wrapper for all hooks so `ECC_HOOK_PROFILE` and `ECC_DISABLED_HOOKS` runtime gating works
 - Always exit 0 on parse errors; log to stderr with `[HookName]` prefix
 
 ## Testing Requirements

COMMANDS-QUICK-REF.md

@@ -76,9 +76,9 @@
 
 | Command | What it does |
 |---------|-------------|
-| `/save-session` | Save current session state to `~/.claude/sessions/` |
-| `/resume-session` | Load most recent session and resume from where you left off |
-| `/sessions` | Browse, search, and manage session history with aliases |
+| `/save-session` | Save current session state to `~/.claude/session-data/` |
+| `/resume-session` | Load the most recent saved session from the canonical session store and resume from where you left off |
+| `/sessions` | Browse, search, and manage session history with aliases from `~/.claude/session-data/` (with legacy reads from `~/.claude/sessions/`) |
 | `/checkpoint` | Mark a checkpoint in the current session |
 | `/aside` | Answer a quick side question without losing current task context |
 | `/context-budget` | Analyse context window usage — find token overhead, optimise |

EVALUATION.md

@@ -41,7 +41,7 @@ The active Claude Code installation is near-minimal:
 | Schemas | 9 JSON validators |
 | Scripts/CLI | 46+ Node.js modules + multiple CLIs |
 | Tests | 58 test files |
-| Install profiles | minimal, standard, full, enterprise |
+| Install profiles | core, developer, security, research, full |
 | Supported harnesses | Claude Code, Codex, Cursor, OpenCode |
 
 ---
@@ -88,8 +88,8 @@ TypeScript, Python, Go, Java, Kotlin, Rust, C++, C#, Swift, Perl, PHP, and commo
 
 ## Recommendations
 
-### Immediate value (minimal install)
-Run `ecc install --profile minimal` to get:
+### Immediate value (core install)
+Run `ecc install --profile core` to get:
 - Core agents (code-reviewer, planner, tdd-guide, security-reviewer)
 - Essential skills (tdd-workflow, coding-standards, security-review)
 - Key commands (/tdd, /plan, /code-review, /build-fix)

REPO-ASSESSMENT.md

@@ -100,6 +100,7 @@ node scripts/install-apply.js
 Regardless of profile, these components add immediate value:
 
 ### 1. Core Agents (highest ROI)
+
 | Agent | Why it matters |
 |-------|----------------|
 | `planner.md` | Breaks complex tasks into implementation plans |
@@ -109,6 +110,7 @@ Regardless of profile, these components add immediate value:
 | `architect.md` | System design & scalability decisions |
 
 ### 2. Key Commands
+
 | Command | Why it matters |
 |---------|----------------|
 | `/plan` | Implementation planning before coding |
@@ -168,7 +170,7 @@ No need to clone the repo. This is the recommended install method for most users
 1. **Keep the existing Stop hook** — it's doing its job
 2. **Run the developer profile install** from the local fork:
    ```bash
-   cd /home/user/everything-claude-code
+   cd /path/to/everything-claude-code
    node scripts/install-plan.js --profile developer
    node scripts/install-apply.js
    ```