feat: visualiser, optimisation and agent restrictions pass

AGENTS.md

@@ -13,8 +13,10 @@ to pick the new one up.
 - bash/grep shouldn't be used for understanding the project
     - IF `ccc` tool calls are unable to find a term your are searching for; stop the session and respond with `CCC: unable to find <term> in ccc using calls: [calls]`
 - Every interaction: use `ccc` tool calls to gather information about the source of this project.
-- All thinking, navigation, and questions about the codebase go through the MCP server tools: (index, find, references, dependencies, vulnerabilities, deps, security, file, notes, changes, prompts, pr_summary, test_triggers, test_targets, lints, hot, services, refresh)
-- When I ask to *see* the analysis, call `insights` - it opens the insights UI in my browser
+- All thinking, navigation, and questions about the codebase go through the MCP server tools: (index, find, references, dependencies, vulnerabilities, deps, security, file, notes, changes, prompts, pr_summary, test_triggers, test_targets, lints, hot, services, search, violations, refresh)
+- The web, internal docs and portals included, goes through `search`: `query` to search the configured endpoints,
+  `url` to fetch one https page. Never WebFetch, WebSearch, another MCP server's fetch or browser tool, or
+  `curl`/`wget` - ccc can't track those, and `violations` reports each one. If `search` refuses a URL, leave it unreached.
 - ccc is the only writer in this project. Every change goes through its edit tools, never through your own
   Edit/Write/MultiEdit/NotebookEdit tools, `sed -i`, or shell redirection:
     - a symbol: take the handle a `find` / `references` answer ends with and pass it to `edit_rename`,

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "codecache"
-version = "1.7.0"
+version = "1.8.0"
 edition = "2021"
 rust-version = "1.77"
 description = "Code Change Capture (ccc) generates an agent friendly local source map"