01 · Installation
The command is not found
Confirm that ~/.local/bin is on PATH, then restart the shell and MCP client. A pip installation uses the package name enola-cli but still installs the command enola.
command -v enola enola --status
02 · MCP
The client cannot connect
- Run enola --status outside the client.
- Confirm the registration starts the local enola command.
- Restart the client after changing PATH or MCP configuration.
- If a config path is supplied, use an absolute path.
03 · Snapshot
The graph is empty or incomplete
- Run from the intended repository root or set the repository path explicitly.
- Check ignore rules for paths that were excluded accidentally.
- Confirm the language or framework capability in Language coverage.
- Review the receipt for active extractors and fact counts.
- Review the coverage report for unresolved calls and boundaries.
04 · Timeout
The first snapshot takes too long
Increase the MCP client tool timeout or generate once from the shell. Later runs can reuse cached extraction.
enola --generate
05 · Comparison
The check returns code 3
The snapshots are not comparable. Review the receipt for changes to the Enola version, repository identity, or ignore configuration. Then pin a new baseline with the settings that will be used for the check.
enola baseline pin enola check
06 · Hooks
A hook did not run
Run enola doctor to see when each hook last fired and whether a baseline exists. Codex hooks require one-time approval through /hooks. Re-run enola install --hooks to preview the expected changes.
07 · Constraints
A rule never reports a violation
Run enola constraints lint . and check component membership. A component with zero members is valid syntax, but a rule built on it cannot match a relationship.