docs: say that taskcut is silent without the function-hooks flag

README.md

@@ -41,6 +41,17 @@ CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude
 The install notes that options are "not yet set". That is fine: unset, each
 takes its default.
 
+`CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1` is needed on every launch while function
+hooks are in early access. Without it the plugin is listed as installed but never
+runs, and nothing says so. To set it once, put
+`"CLAUDE_CODE_ENABLE_FUNCTION_HOOKS": "1"` under `env` in
+`~/.claude/settings.json`. To check that taskcut loads:
+
+```bash
+CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 claude -p ok --debug-file /tmp/taskcut.log >/dev/null
+grep 'taskcut@taskcut loaded' /tmp/taskcut.log
+```
+
 Then work as usual. Nothing happens until the context passes 35% — the `ctx`
 figure in the status line. From then on, when a piece of work is finished, a
 dim line says so and Claude Code compacts exactly as `/compact` would:

docs/troubleshooting.md

@@ -26,6 +26,17 @@ is not loaded at all — the plugin still appears in `claude plugin list`, and n
 of its hooks run. This is Claude Code's flag, not taskcut's, and it will stop
 being needed when the feature graduates.
 
+Whether the module loaded is in Claude Code's debug log, whatever the context
+fill:
+
+```bash
+claude -p ok --debug-file /tmp/taskcut.log >/dev/null
+grep 'taskcut@taskcut' /tmp/taskcut.log
+```
+
+`hooks module taskcut@taskcut loaded` means it is running. `not loaded:` is
+followed by the reason; without the flag, it says the rollout flag is off.
+
 ### 2. Is the plugin loaded?
 
 ```bash