@@ -95,17 +95,23 @@ The skill preserves three evidence levels:
 
 ### Skills and hooks
 
-`install` may place CLI-first skills, durable instructions, and compatible lifecycle/context hooks for detected coding agents. New installs do **not** create MCP registrations or MCP-bound tier profiles/extensions.
+`install` may place CLI-first skills and durable instructions for detected coding agents. It **never installs hooks** and does not create, migrate, or remove `codebase-memory-mcp` registrations or MCP-owned assets.
+
+Hooks are a separate, explicit opt-in surface. Install only `codebase-memory-cli`-owned lifecycle/context hooks with:
+
+```sh
+codebase-memory-cli install-hooks
+```
 
 Hooks are an optimization and guidance surface, not the only route to the graph. If a warm runtime is absent or a hook cannot augment context, it fails open and the ordinary CLI still works.
 
-To configure detected agent integrations without replacing an externally managed binary:
+To configure detected agent assets without replacing an externally managed binary:
 
 ```sh
 codebase-memory-cli install --skip-binary
 ```
 
-Use `install --plan` when you want to inspect planned writes before applying them.
+Use `install --plan` to inspect asset writes and `install-hooks --plan` to inspect hook writes before applying either surface. `--clients=<list>` is supported independently by both commands.
 
 ## Installation
 
@@ -132,7 +138,7 @@ Windows PowerShell:
 irm https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/scripts/setup-windows.ps1 | iex
 ```
 
-The setup scripts install the executable. They do not write MCP client configuration. Afterward, run `codebase-memory-cli install --skip-binary` if you want Codebase Memory to install its CLI-first skills/instructions/hooks for detected agents.
+The setup scripts install the executable. They do not install hooks or write MCP client configuration. Afterward, run `codebase-memory-cli install --skip-binary` for CLI-first skills/instructions. Run `codebase-memory-cli install-hooks` separately only if you explicitly want CLI-owned agent hooks.
 
 ## Human and machine output
 
 
@@ -342,3 +342,13 @@ Status: **IMPLEMENTED / REQUIRES EXTERNAL RERUN**
 - **VERIFIED LOCALLY:** changed production/test objects compile under the repository's strict production and ASan/UBSan warning policies. Full incremental execution still requires the externally cached FastAPI fixture unavailable in this sandbox.
 - **PENDING EXTERNAL GATE:** run `scripts/test.sh` once on CP77. No separate memory-analysis rerun is required unless new memory evidence appears.
 
+
+### CP78 — Explicit CLI hook-install boundary and MCP coexistence
+
+- **COMPLETE (implementation):** ordinary `codebase-memory-cli install` is an asset-only surface. CLI-owned agent hooks require the separate, explicit `codebase-memory-cli install-hooks` command; `--plan`, `--dry-run`, and `--clients` are independently supported on that hook surface.
+- **COMPLETE:** CLI-owned durable-context assets and hook identities use `codebase-memory-cli` namespaces rather than MCP-era names. The CLI no longer adopts MCP-era Claude/Gemini hook identities as upgrade ownership.
+- **COMPLETE:** install, hook installation, and uninstall treat `codebase-memory-mcp` registrations, MCP-era hook files, legacy MCP compaction labels, and MCP-owned skill namespaces as foreign. Side-by-side installation therefore does not use MCP cleanup as a migration mechanism.
+- **COMPLETE:** setup scripts no longer activate repository Git hooks implicitly. Post-install guidance makes agent-hook installation explicitly opt-in.
+- **REGRESSION COVERAGE ADDED:** CP78 plan tests assert that asset and hook plans are disjoint, and a Claude coexistence test asserts that explicit CLI hook installation preserves a pre-existing MCP hook command/file while installing separate CLI hook identities.
+- **VERIFIED LOCALLY:** changed production CLI and CLI-test translation units compile with the repository's strict `-Wall -Wextra -Werror` production/test policies and ASan/UBSan test instrumentation.
+- **PENDING EXTERNAL GATE:** the full sanitizer runner could not be linked within the bounded local compiler windows because the repository-wide grammar/dependency build repeatedly exhausted the command window. No CP78 compile failure surfaced. Run the canonical Jenkins/`scripts/test.sh` gate on the CP78 candidate; reconcile any stale pre-CP78 ownership assertions rather than weakening the MCP/CLI separation contract.
@@ -22,9 +22,13 @@ function Write-Warn($msg)  { Write-Host "  $msg" -ForegroundColor Yellow }
 function Write-AgentIntegrationGuidance($Command) {
     Write-Host ""
     Write-Host "  Codebase Memory is CLI-first; this setup script does not write MCP client configuration." -ForegroundColor White
-    Write-Host "  To install CLI-first skills/instructions/hooks for detected agents, run:" -ForegroundColor White
+    Write-Host "  To install CLI-first skills/instructions for detected agents, run:" -ForegroundColor White
     Write-Host ""
     Write-Host "    $Command install --skip-binary" -ForegroundColor Yellow
+    Write-Host ""
+    Write-Host "  Hooks are never installed by setup or install. To opt in separately, run:" -ForegroundColor White
+    Write-Host ""
+    Write-Host "    $Command install-hooks" -ForegroundColor Yellow
 }
 
 
 
@@ -209,9 +209,13 @@ build_from_source() {
 print_agent_integration_guidance() {
     echo ""
     info "Codebase Memory is CLI-first; this setup script does not write MCP client configuration."
-    info "To install CLI-first skills/instructions/hooks for detected agents, run:"
+    info "To install CLI-first skills/instructions for detected agents, run:"
     echo ""
     echo "  ${INSTALL_DIR}/${BINARY_NAME} install --skip-binary"
+    echo ""
+    info "Hooks are never installed by setup or install. To opt in separately, run:"
+    echo ""
+    echo "  ${INSTALL_DIR}/${BINARY_NAME} install-hooks"
 }
 
 # --- PATH check ---
@@ -257,12 +261,8 @@ fi
 print_agent_integration_guidance
 check_path
 
-# --- Git hooks ---
-# If run from inside the repo, activate tracked hooks
-if [ -d "scripts/hooks" ] && git rev-parse --git-dir &>/dev/null; then
-    git config core.hooksPath scripts/hooks
-    ok "Git hooks activated (scripts/hooks/)"
-fi
+# Hook installation is intentionally never implicit. Repository contributors may
+# opt into tracked Git hooks separately with: git config core.hooksPath scripts/hooks
 
 echo ""
 ok "Done! Try: ${BINARY_NAME} --help"