memgraph-context-graph 0.5.0__tar.gz → 0.6.0__tar.gz

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: memgraph-context-graph
-Version: 0.5.0
+Version: 0.6.0
 Summary: Connect agent SDKs to context-graph components (actions-graph, skills-graph, etc.)
 License: MIT
 License-File: LICENSE
@@ -10,6 +10,7 @@ Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.10
 Requires-Dist: memgraph-toolbox>=0.1.11
+Requires-Dist: textual<9,>=8.2
 Requires-Dist: tomlkit<1,>=0.13
 Provides-Extra: claude
 Requires-Dist: claude-agent-sdk>=0.1.0; extra == 'claude'
@@ -49,7 +50,7 @@ uv tool install "memgraph-context-graph[mcp]" --with "skills-graph[memgraph-cont
 
 The `mcp` extra is what `memgraph-context-graph mcp` serves [recall](#recall-memory-for-the-harnesss-model) with.
 
-Or use the plugin bootstrap scripts; they fall back to `uvx` if the tool is not installed yet.
+Or run `memgraph-context-graph setup`, which installs whatever connectors are missing (see [Setup](#setup)).
 
 For SDK usage inside an application:
 
@@ -178,7 +179,8 @@ Implemented:
 | Grok Build | `GrokHooksAdapter` | Command receives one JSON object on `stdin` |
 
 Codex and Claude Code have distributable Runtime Plugins. Copilot CLI, Cursor,
-OpenCode, Antigravity CLI, and Grok Build use project-local wiring generated by `hook init`:
+OpenCode, Antigravity CLI, and Grok Build use project-local wiring, which `setup`
+writes (or, one runtime at a time, `hook init`):
 
 ```bash
 memgraph-context-graph hook init copilot-cli
@@ -191,44 +193,32 @@ memgraph-context-graph hook init grok
 See the [command-hook reference](docs/command-hooks.md) for generated paths,
 payload differences, and current upstream hook documentation.
 
-### First-Time Plugin Setup
+### Setup
 
-For Codex and Claude Code plugins, the recommended first-run path is the bootstrap command. It installs the runtime package (with the connector extras), checks Memgraph, and runs `doctor`.
-
-Prerequisites:
-
-- `uv` on `PATH`. (`uv` manages Python for the tool; if uv-managed Python downloads are blocked, install Python 3.10+ and rerun bootstrap.)
-- Memgraph running and reachable over Bolt. Defaults are `bolt://localhost:7687`, empty user/password, database `memgraph`. If it isn't running locally:
-
-  ```bash
-  docker run --rm -p 7687:7687 memgraph/memgraph-mage
-  ```
-
-**1. Bootstrap all three connectors** (this is what the installed plugin wires into its hooks):
+`memgraph-context-graph setup` installs Context Graph for every agent on the machine; the
+[family README](../README.md#getting-started) walks through it. In short:
 
 ```bash
-# Codex
-memgraph-context-graph bootstrap --runtime codex \
-  --connector skills-graph --connector actions-graph --connector sessions-graph
-
-# Claude Code
-memgraph-context-graph bootstrap --runtime claude-code \
-  --connector skills-graph --connector actions-graph --connector sessions-graph
+memgraph-context-graph setup                     # interactive on a terminal; plain otherwise
+memgraph-context-graph setup claude-code codex   # just these agents
+memgraph-context-graph setup cursor --project-dir ~/work/billing
+memgraph-context-graph setup --plan              # print the plan, change nothing
+memgraph-context-graph uninstall [runtime ...]   # remove the wiring; the graph and config stay
 ```
 
-The plugin wrapper script runs the same command (and falls back to `uvx` if the tool isn't installed yet):
-
-```bash
-./scripts/bootstrap.sh
-```
+It finds or starts Memgraph (a `memgraph-mage` container with a volume, on a free port when 7687 is taken),
+writes `memgraph.url` and `identity.user_id`, installs missing connectors and the viewer into the uv tool,
+wires each agent, and runs `doctor`'s checks. Every step checks before it acts, so rerunning only does what's
+missing. The TUI starts only when stdin and stdout are both terminals; the plugins' `scripts/bootstrap.sh`
+runs `setup <runtime> --no-tui`.
 
-**2. Configure identity and connection.** Bootstrap writes `~/.config/context-graph/config.toml`; hooks read their configuration from that file at runtime (see [Configuration](#configuration) — env vars are **not** read at hook time). Set your identity, which sessions-graph requires:
+**Identity and connection.** setup writes `~/.config/context-graph/config.toml`; hooks read their configuration from that file at runtime (see [Configuration](#configuration) — env vars are **not** read at hook time). To change your identity later:
 
 ```bash
 memgraph-context-graph config set identity.user_id "your-name"
 ```
 
-The Memgraph connection defaults to `bolt://localhost:7687`. For a remote or HA instance:
+For a remote or HA instance, pass `setup --memgraph-url`, or set it with credentials afterwards:
 
 ```bash
 memgraph-context-graph config set memgraph.url "neo4j://<coordinator-host>:7687"
@@ -237,7 +227,7 @@ memgraph-context-graph config set memgraph.password        # prompts; stored 060
 memgraph-context-graph config set memgraph.database "memgraph"
 ```
 
-**3. Verify:**
+**Verify** (setup runs the same checks):
 
 ```bash
 memgraph-context-graph config show
@@ -292,7 +282,7 @@ turns_k = "8"
 [sessions-graph § reconciliation](../sessions-graph/README.md#session-reconciliation)),
 which needs no LLM. `[llm]` is optional: a key only lets reconciliation learn
 the user's own ontology (`sessions-graph derive`).
-`[reconcile]` is omitted entirely from a freshly-bootstrapped file — absent
+`[reconcile]` is omitted entirely from a file setup wrote — absent
 means "never configured," distinct from an explicit `auto_reconcile = false`.
 `[recall]` is optional too: without it, recall runs with the widths the
 benchmark measured; see [Recall](#recall-memory-for-the-harnesss-model).
@@ -311,14 +301,9 @@ memgraph-context-graph config set <key> <value>
 #       recall.embedding_model, ontology.{path,derive}, memory.backend
 ```
 
-Environment variables (`MEMGRAPH_URL`, `MEMGRAPH_USER`, `MEMGRAPH_PASSWORD`, `MEMGRAPH_DATABASE`, `MEMGRAPH_CONTEXT_GRAPH_USER_ID`, `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`) are consulted **only at bootstrap time** — if set, `bootstrap` persists them into the config file. Exporting them later has no effect on running hooks; use `config set` instead.
-
-`reconcile.auto_reconcile` is the one exception: `bootstrap` never captures
-`SESSIONS_GRAPH_AUTO_RECONCILE` from the environment, and re-running
-`bootstrap` preserves whatever it's currently set to rather than resetting it.
-Unlike the keys above, nobody has that env var exported for an unrelated
-reason — it's only ever set via `memgraph-context-graph config set
-reconcile.auto_reconcile true`.
+Hooks never read environment variables for these values, and neither does setup: it writes only
+`memgraph.url` and `identity.user_id`, from its flags or what it found. Everything else is set with
+`config set`, and setup leaves it alone when it rewrites the file.
 
 ### Recall: memory for the harness's model
 
@@ -383,6 +368,9 @@ memgraph-context-graph setup claude-code --memory-backend context-graph
 memgraph-context-graph setup claude-code --memory-backend native   # hand it back
 ```
 
+(The interactive `setup` offers the same switch as a checkbox. `uninstall` turns the harness's own memory
+back on, since without the plugin it would have none.)
+
 Opting in does three things, in this order:
 1. Imports the existing auto-memory files from every project once:
    - `user`/`feedback` memories go to `/memories/<type>/`;
@@ -477,7 +465,7 @@ Check the installed hook environment with:
 memgraph-context-graph doctor --runtime codex --connector skills-graph --connector actions-graph --connector sessions-graph
 ```
 
-Graph credentials live in `~/.config/context-graph/config.toml` (written by `bootstrap`/`config set`), not in plugin hook files or the process environment — hooks read that file at runtime. See [Configuration](#configuration).
+Graph credentials live in `~/.config/context-graph/config.toml` (written by `setup`/`config set`), not in plugin hook files or the process environment — hooks read that file at runtime. See [Configuration](#configuration).
 
 ### Claude Code Plugin
 
@@ -512,7 +500,7 @@ memgraph-context-graph doctor --runtime claude-code --connector skills-graph --c
 For source development and per-project experiments, you can generate local Codex hook files:
 
 ```bash
-memgraph-context-graph setup codex --project-dir "$PWD" --setup-schema
+memgraph-context-graph hook init codex --project-dir "$PWD" --setup-schema
 ```
 
 This writes local, ignored files:
@@ -693,7 +681,7 @@ Then register it in your own package's `pyproject.toml` — this is the entire i
 my-runtime = "my_package.adapter:PLUGIN"
 ```
 
-Once installed, `memgraph-context-graph bootstrap --runtime my-runtime`, `doctor --runtime my-runtime`, `hook run my-runtime`, and `hook init my-runtime` (if `init` is implemented) work like the built-in registrations. See `runtime_plugin.py` for the full protocol and `pyproject.toml`'s own `[project.entry-points."memgraph_context_graph.runtimes"]` for registration examples.
+Once installed, `doctor --runtime my-runtime`, `hook run my-runtime`, and `hook init my-runtime` (if `init` is implemented) work like the built-in registrations. See `runtime_plugin.py` for the full protocol and `pyproject.toml`'s own `[project.entry-points."memgraph_context_graph.runtimes"]` for registration examples.
 
 ### Adding a New Graph Component
 

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/README.md

@@ -24,7 +24,7 @@ uv tool install "memgraph-context-graph[mcp]" --with "skills-graph[memgraph-cont
 
 The `mcp` extra is what `memgraph-context-graph mcp` serves [recall](#recall-memory-for-the-harnesss-model) with.
 
-Or use the plugin bootstrap scripts; they fall back to `uvx` if the tool is not installed yet.
+Or run `memgraph-context-graph setup`, which installs whatever connectors are missing (see [Setup](#setup)).
 
 For SDK usage inside an application:
 
@@ -153,7 +153,8 @@ Implemented:
 | Grok Build | `GrokHooksAdapter` | Command receives one JSON object on `stdin` |
 
 Codex and Claude Code have distributable Runtime Plugins. Copilot CLI, Cursor,
-OpenCode, Antigravity CLI, and Grok Build use project-local wiring generated by `hook init`:
+OpenCode, Antigravity CLI, and Grok Build use project-local wiring, which `setup`
+writes (or, one runtime at a time, `hook init`):
 
 ```bash
 memgraph-context-graph hook init copilot-cli
@@ -166,44 +167,32 @@ memgraph-context-graph hook init grok
 See the [command-hook reference](docs/command-hooks.md) for generated paths,
 payload differences, and current upstream hook documentation.
 
-### First-Time Plugin Setup
+### Setup
 
-For Codex and Claude Code plugins, the recommended first-run path is the bootstrap command. It installs the runtime package (with the connector extras), checks Memgraph, and runs `doctor`.
-
-Prerequisites:
-
-- `uv` on `PATH`. (`uv` manages Python for the tool; if uv-managed Python downloads are blocked, install Python 3.10+ and rerun bootstrap.)
-- Memgraph running and reachable over Bolt. Defaults are `bolt://localhost:7687`, empty user/password, database `memgraph`. If it isn't running locally:
-
-  ```bash
-  docker run --rm -p 7687:7687 memgraph/memgraph-mage
-  ```
-
-**1. Bootstrap all three connectors** (this is what the installed plugin wires into its hooks):
+`memgraph-context-graph setup` installs Context Graph for every agent on the machine; the
+[family README](../README.md#getting-started) walks through it. In short:
 
 ```bash
-# Codex
-memgraph-context-graph bootstrap --runtime codex \
-  --connector skills-graph --connector actions-graph --connector sessions-graph
-
-# Claude Code
-memgraph-context-graph bootstrap --runtime claude-code \
-  --connector skills-graph --connector actions-graph --connector sessions-graph
+memgraph-context-graph setup                     # interactive on a terminal; plain otherwise
+memgraph-context-graph setup claude-code codex   # just these agents
+memgraph-context-graph setup cursor --project-dir ~/work/billing
+memgraph-context-graph setup --plan              # print the plan, change nothing
+memgraph-context-graph uninstall [runtime ...]   # remove the wiring; the graph and config stay
 ```
 
-The plugin wrapper script runs the same command (and falls back to `uvx` if the tool isn't installed yet):
-
-```bash
-./scripts/bootstrap.sh
-```
+It finds or starts Memgraph (a `memgraph-mage` container with a volume, on a free port when 7687 is taken),
+writes `memgraph.url` and `identity.user_id`, installs missing connectors and the viewer into the uv tool,
+wires each agent, and runs `doctor`'s checks. Every step checks before it acts, so rerunning only does what's
+missing. The TUI starts only when stdin and stdout are both terminals; the plugins' `scripts/bootstrap.sh`
+runs `setup <runtime> --no-tui`.
 
-**2. Configure identity and connection.** Bootstrap writes `~/.config/context-graph/config.toml`; hooks read their configuration from that file at runtime (see [Configuration](#configuration) — env vars are **not** read at hook time). Set your identity, which sessions-graph requires:
+**Identity and connection.** setup writes `~/.config/context-graph/config.toml`; hooks read their configuration from that file at runtime (see [Configuration](#configuration) — env vars are **not** read at hook time). To change your identity later:
 
 ```bash
 memgraph-context-graph config set identity.user_id "your-name"
 ```
 
-The Memgraph connection defaults to `bolt://localhost:7687`. For a remote or HA instance:
+For a remote or HA instance, pass `setup --memgraph-url`, or set it with credentials afterwards:
 
 ```bash
 memgraph-context-graph config set memgraph.url "neo4j://<coordinator-host>:7687"
@@ -212,7 +201,7 @@ memgraph-context-graph config set memgraph.password        # prompts; stored 060
 memgraph-context-graph config set memgraph.database "memgraph"
 ```
 
-**3. Verify:**
+**Verify** (setup runs the same checks):
 
 ```bash
 memgraph-context-graph config show
@@ -267,7 +256,7 @@ turns_k = "8"
 [sessions-graph § reconciliation](../sessions-graph/README.md#session-reconciliation)),
 which needs no LLM. `[llm]` is optional: a key only lets reconciliation learn
 the user's own ontology (`sessions-graph derive`).
-`[reconcile]` is omitted entirely from a freshly-bootstrapped file — absent
+`[reconcile]` is omitted entirely from a file setup wrote — absent
 means "never configured," distinct from an explicit `auto_reconcile = false`.
 `[recall]` is optional too: without it, recall runs with the widths the
 benchmark measured; see [Recall](#recall-memory-for-the-harnesss-model).
@@ -286,14 +275,9 @@ memgraph-context-graph config set <key> <value>
 #       recall.embedding_model, ontology.{path,derive}, memory.backend
 ```
 
-Environment variables (`MEMGRAPH_URL`, `MEMGRAPH_USER`, `MEMGRAPH_PASSWORD`, `MEMGRAPH_DATABASE`, `MEMGRAPH_CONTEXT_GRAPH_USER_ID`, `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`) are consulted **only at bootstrap time** — if set, `bootstrap` persists them into the config file. Exporting them later has no effect on running hooks; use `config set` instead.
-
-`reconcile.auto_reconcile` is the one exception: `bootstrap` never captures
-`SESSIONS_GRAPH_AUTO_RECONCILE` from the environment, and re-running
-`bootstrap` preserves whatever it's currently set to rather than resetting it.
-Unlike the keys above, nobody has that env var exported for an unrelated
-reason — it's only ever set via `memgraph-context-graph config set
-reconcile.auto_reconcile true`.
+Hooks never read environment variables for these values, and neither does setup: it writes only
+`memgraph.url` and `identity.user_id`, from its flags or what it found. Everything else is set with
+`config set`, and setup leaves it alone when it rewrites the file.
 
 ### Recall: memory for the harness's model
 
@@ -358,6 +342,9 @@ memgraph-context-graph setup claude-code --memory-backend context-graph
 memgraph-context-graph setup claude-code --memory-backend native   # hand it back
 ```
 
+(The interactive `setup` offers the same switch as a checkbox. `uninstall` turns the harness's own memory
+back on, since without the plugin it would have none.)
+
 Opting in does three things, in this order:
 1. Imports the existing auto-memory files from every project once:
    - `user`/`feedback` memories go to `/memories/<type>/`;
@@ -452,7 +439,7 @@ Check the installed hook environment with:
 memgraph-context-graph doctor --runtime codex --connector skills-graph --connector actions-graph --connector sessions-graph
 ```
 
-Graph credentials live in `~/.config/context-graph/config.toml` (written by `bootstrap`/`config set`), not in plugin hook files or the process environment — hooks read that file at runtime. See [Configuration](#configuration).
+Graph credentials live in `~/.config/context-graph/config.toml` (written by `setup`/`config set`), not in plugin hook files or the process environment — hooks read that file at runtime. See [Configuration](#configuration).
 
 ### Claude Code Plugin
 
@@ -487,7 +474,7 @@ memgraph-context-graph doctor --runtime claude-code --connector skills-graph --c
 For source development and per-project experiments, you can generate local Codex hook files:
 
 ```bash
-memgraph-context-graph setup codex --project-dir "$PWD" --setup-schema
+memgraph-context-graph hook init codex --project-dir "$PWD" --setup-schema
 ```
 
 This writes local, ignored files:
@@ -668,7 +655,7 @@ Then register it in your own package's `pyproject.toml` — this is the entire i
 my-runtime = "my_package.adapter:PLUGIN"
 ```
 
-Once installed, `memgraph-context-graph bootstrap --runtime my-runtime`, `doctor --runtime my-runtime`, `hook run my-runtime`, and `hook init my-runtime` (if `init` is implemented) work like the built-in registrations. See `runtime_plugin.py` for the full protocol and `pyproject.toml`'s own `[project.entry-points."memgraph_context_graph.runtimes"]` for registration examples.
+Once installed, `doctor --runtime my-runtime`, `hook run my-runtime`, and `hook init my-runtime` (if `init` is implemented) work like the built-in registrations. See `runtime_plugin.py` for the full protocol and `pyproject.toml`'s own `[project.entry-points."memgraph_context_graph.runtimes"]` for registration examples.
 
 ### Adding a New Graph Component
 

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/docs/command-hooks.md

@@ -234,14 +234,11 @@ memgraph-context-graph config set memgraph.url "bolt://localhost:7687"
 memgraph-context-graph config show
 ```
 
-Bootstrap captures supported environment variables into that file as a
-write-time convenience:
+`memgraph-context-graph setup` writes `memgraph.url` and `identity.user_id` there,
+and wires the project in one go:
 
 ```bash
-memgraph-context-graph bootstrap --runtime antigravity-cli \
-  --connector skills-graph \
-  --connector actions-graph \
-  --connector sessions-graph
+memgraph-context-graph setup antigravity-cli --project-dir "$PWD"
 ```
 
 ## Verification

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "memgraph-context-graph"
-version = "0.5.0"
+version = "0.6.0"
 description = "Connect agent SDKs to context-graph components (actions-graph, skills-graph, etc.)"
 readme = "README.md"
 license = { text = "MIT" }
@@ -15,6 +15,9 @@ dependencies = [
     "memgraph-toolbox>=0.1.11",
     # Edits ~/.codex/config.toml when switching Codex's memory, keeping the user's comments and layout.
     "tomlkit>=0.13,<1",
+    # setup's interactive installer. Imported only when it runs, so hooks never load it; pinned to the
+    # major the viewer uses, since Textual's API moves between majors.
+    "textual>=8.2,<9",
 ]
 
 [project.scripts]
@@ -45,6 +48,11 @@ test = [
     "pytest-asyncio>=0.24.0",
 ]
 
+[tool.pytest.ini_options]
+markers = [
+  "docker: starts real Memgraph containers, so it needs Docker; CI runs these in their own job",
+]
+
 [build-system]
 requires = ["hatchling"]
 build-backend = "hatchling.build"

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/src/memgraph_context_graph/adapters/_identity.py

@@ -49,7 +49,12 @@ _DEFAULT_CONFIG_DIR = Path.home() / ".config" / "context-graph"
 def config_file() -> Path:
     """The config file hooks read, honouring :data:`CONFIG_PATH_ENV`."""
     override = os.environ.get(CONFIG_PATH_ENV)
-    return Path(override) if override else _DEFAULT_CONFIG_DIR / "config.toml"
+    return Path(override) if override else default_config_file()
+
+
+def default_config_file() -> Path:
+    """The config file used when :data:`CONFIG_PATH_ENV` is unset."""
+    return _DEFAULT_CONFIG_DIR / "config.toml"
 
 
 # Defaults matching memgraph-toolbox's MEMGRAPH_ENV_DEFAULTS.
@@ -116,6 +121,10 @@ class HookConfig:
     #: "left at the default" from "written": Enterprise refuses an explicit ``identity.user_id`` or
     #: ``memgraph.database``, which would quietly override what the login decides.
     present: frozenset[str] = frozenset()
+    #: Why the file could not be read as written: unreadable, or lines that are not ``key = value``.
+    #: Values those lines meant to set fell back to defaults, which can point hooks at the wrong
+    #: Memgraph, so hooks log these to the capture-failure log and ``doctor`` fails on them.
+    problems: tuple[str, ...] = ()
 
     @property
     def graph_memory(self) -> bool:
@@ -321,18 +330,11 @@ def write_full_config(
     anthropic_api_key: str = _LLM_DEFAULTS["anthropic_api_key"],
     auto_reconcile: bool | None = _RECONCILE_DEFAULTS["auto_reconcile"],
 ) -> Path:
-    """Write a complete config file with all sections (used by bootstrap).
-
-    Overwrites every section except ``[reconcile]``, ``[recall]``, ``[ontology]``, ``[github]`` and ``[memory]``: unlike identity/Memgraph/LLM
-    settings, ``auto_reconcile`` has no legitimate ambient-env source for
-    ``bootstrap`` to capture (nobody has ``SESSIONS_GRAPH_AUTO_RECONCILE``
-    exported for an unrelated reason the way they might already have
-    ``OPENAI_API_KEY``/`MEMGRAPH_PASSWORD` set) — it is only ever set via
-    ``config set reconcile.auto_reconcile``. Re-running bootstrap must not
-    silently revert it to off, so ``auto_reconcile`` is preserved from the
-    existing file unless explicitly given here. ``[recall]``, ``[ontology]`` and
-    ``[github]`` are preserved the same way: they are only ever set via ``config set`` or by
-    editing the file. ``[memory]`` is set by ``setup --memory-backend`` and kept likewise.
+    """Write a complete config file, resetting identity, Memgraph and LLM settings to what is given.
+
+    Every other section (``[reconcile]``, ``[recall]``, ``[ontology]``, ``[github]``, ``[memory]``) and the
+    edition are kept from the existing file, since only ``config set`` or a hand edit ever sets them.
+    ``auto_reconcile`` is kept likewise unless given here. :func:`write_config` is the partial update.
     """
     global _cached_config
 
@@ -380,14 +382,19 @@ def config_dir_path() -> Path:
 
 
 def _read_config_file() -> HookConfig:
-    """Parse the config file. Returns defaults if file is missing or malformed."""
-    if not config_file().is_file():
-        return HookConfig()
+    """Parse the config file.
 
+    A missing file gives defaults. An unreadable or partly unparsable one also
+    gives defaults for whatever it failed to set, never an exception (a hook
+    must not crash on its config), and says so in :attr:`HookConfig.problems`.
+    """
+    problems: list[str] = []
     try:
-        sections = _parse_toml(config_file())
-    except Exception:
-        return HookConfig()
+        if not config_file().is_file():
+            return HookConfig()
+        sections = _parse_toml(config_file(), problems)
+    except Exception as exc:
+        return HookConfig(problems=(f"unreadable: {type(exc).__name__}: {exc}",))
 
     identity = sections.get("identity", {})
     memgraph = sections.get("memgraph", {})
@@ -421,19 +428,21 @@ def _read_config_file() -> HookConfig:
             for key, value in keys.items()
             if value
         ),
+        problems=tuple(problems),
     )
 
 
-def _parse_toml(path: Path) -> dict[str, dict[str, str]]:
+def _parse_toml(path: Path, problems: list[str] | None = None) -> dict[str, dict[str, str]]:
     """Minimal TOML parser — handles [section] and key = "value" pairs.
 
     Only supports string values (quoted or bare). Sufficient for our config shape.
-    Keys before the first section header land in the ``""`` section.
+    Keys before the first section header land in the ``""`` section. A line that
+    is none of these is skipped and, when *problems* is given, reported there.
     """
     sections: dict[str, dict[str, str]] = {"": {}}
     current_section = ""
 
-    for line in path.read_text(encoding="utf-8").splitlines():
+    for number, line in enumerate(path.read_text(encoding="utf-8").splitlines(), start=1):
         stripped = line.strip()
         if not stripped or stripped.startswith("#"):
             continue
@@ -441,15 +450,18 @@ def _parse_toml(path: Path) -> dict[str, dict[str, str]]:
             current_section = stripped[1:-1].strip()
             sections.setdefault(current_section, {})
             continue
-        if "=" in stripped:
-            key, _, value = stripped.partition("=")
-            key = key.strip()
-            value = value.strip()
-            if value[:1] not in {'"', "'"} and "#" in value:
-                # Bare (unquoted) value with a trailing comment, e.g. `auto_reconcile = true  # off for now`.
-                value = value.partition("#")[0].strip()
-            value = value.strip('"').strip("'")
-            sections[current_section][key] = value
+        if "=" not in stripped or not stripped.partition("=")[0].strip():
+            if problems is not None:
+                problems.append(f"line {number} is not `key = value` and was ignored")
+            continue
+        key, _, value = stripped.partition("=")
+        key = key.strip()
+        value = value.strip()
+        if value[:1] not in {'"', "'"} and "#" in value:
+            # Bare (unquoted) value with a trailing comment, e.g. `auto_reconcile = true  # off for now`.
+            value = value.partition("#")[0].strip()
+        value = value.strip('"').strip("'")
+        sections[current_section][key] = value
 
     return sections
 

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/src/memgraph_context_graph/adapters/_spec.py

@@ -298,7 +298,9 @@ def write_hook_config(
     """Write a runtime's project-local JSON hook configuration.
 
     Existing settings files are merged only when the runtime declares
-    ``merge=True``. Otherwise callers must pass ``force=True`` to replace one.
+    ``merge=True``: every hook entry this runtime's command didn't write is
+    kept, and this runtime's own entries are replaced, so writing twice leaves
+    one copy. Otherwise callers must pass ``force=True`` to replace the file.
 
     Raises:
         ValueError: if *spec* declares no config path, or an existing file to
@@ -326,13 +328,82 @@ def write_hook_config(
     existing_hooks = document.get(spec.config.root_key, {})
     if not isinstance(existing_hooks, dict):
         raise ValueError(f"Expected {spec.config.root_key!r} to be an object in {config_path}")
-    document[spec.config.root_key] = {**existing_hooks, **hooks}
+    merged = _without_own_entries(spec, existing_hooks)
+    for event, entries in hooks.items():
+        merged[event] = [*merged.get(event, []), *entries]
+    document[spec.config.root_key] = merged
 
     config_path.parent.mkdir(parents=True, exist_ok=True)
     config_path.write_text(json.dumps(document, indent=2) + "\n", encoding="utf-8")
     return config_path
 
 
+def has_hook_config(spec: RuntimeSpec, project_dir: Path) -> bool:
+    """Whether *project_dir*'s hook file for *spec* holds an entry this runtime's command wrote."""
+    hooks = _read_hooks(spec, project_dir)
+    return hooks is not None and any(_is_own_entry(spec, entry) for entries in hooks.values() for entry in entries)
+
+
+def remove_hook_config(spec: RuntimeSpec, project_dir: Path) -> bool:
+    """Remove this runtime's entries from *project_dir*'s hook file, keeping everything else.
+
+    A file left with nothing but an empty hook map (and ``version``) is deleted. Returns whether anything
+    was removed.
+
+    Raises:
+        ValueError: if the file exists but isn't a JSON object with an object-valued hook map.
+    """
+    if not has_hook_config(spec, project_dir):
+        return False
+    config_path = project_dir / str(spec.config.path)
+    document = json.loads(config_path.read_text(encoding="utf-8"))
+    remaining = _without_own_entries(spec, document[spec.config.root_key])
+    if remaining:
+        document[spec.config.root_key] = remaining
+    else:
+        del document[spec.config.root_key]
+    if set(document) <= {"version"}:
+        config_path.unlink()
+    else:
+        config_path.write_text(json.dumps(document, indent=2) + "\n", encoding="utf-8")
+    return True
+
+
+def _read_hooks(spec: RuntimeSpec, project_dir: Path) -> dict[str, list[Any]] | None:
+    if spec.config.path is None:
+        return None
+    config_path = project_dir / spec.config.path
+    if not config_path.is_file():
+        return None
+    document = json.loads(config_path.read_text(encoding="utf-8"))
+    if not isinstance(document, dict) or not isinstance(document.get(spec.config.root_key, {}), dict):
+        raise ValueError(f"Expected a JSON object with an object {spec.config.root_key!r} in {config_path}")
+    return {
+        event: entries for event, entries in document.get(spec.config.root_key, {}).items() if isinstance(entries, list)
+    }
+
+
+def _without_own_entries(spec: RuntimeSpec, hooks: dict[str, Any]) -> dict[str, Any]:
+    """*hooks* minus this runtime's own entries; events left empty are dropped."""
+    kept: dict[str, Any] = {}
+    for event, entries in hooks.items():
+        if not isinstance(entries, list):
+            kept[event] = entries
+            continue
+        others = [entry for entry in entries if not _is_own_entry(spec, entry)]
+        if others:
+            kept[event] = others
+    return kept
+
+
+def _is_own_entry(spec: RuntimeSpec, entry: Any) -> bool:
+    """Whether a hook entry (flat, or a matcher group holding ``hooks``) runs this runtime's capture command."""
+    marker = f"hook run {spec.name}"
+    if isinstance(entry, dict) and isinstance(entry.get("hooks"), list):
+        return any(_is_own_entry(spec, inner) for inner in entry["hooks"])
+    return isinstance(entry, dict) and marker in str(entry.get(spec.config.command_key, ""))
+
+
 def hook_command_argv(runtime: str, connectors: list[str]) -> list[str]:
     """Build the installed hook command for *runtime* and *connectors* as argv."""
     executable = shutil.which("memgraph-context-graph")

{memgraph_context_graph-0.5.0 → memgraph_context_graph-0.6.0}/src/memgraph_context_graph/adapters/opencode.py

@@ -131,7 +131,7 @@ class OpenCodeHooksAdapter(SpecAdapter):
     SPEC = SPEC
 
 
-_PLUGIN_PATH = ".opencode/plugins/memgraph-context-graph/index.js"
+PLUGIN_PATH = ".opencode/plugins/memgraph-context-graph/index.js"
 
 
 def init(
@@ -151,7 +151,7 @@ def init(
     Raises:
         FileExistsError: if the plugin file exists and *force* is false.
     """
-    target = project_dir / _PLUGIN_PATH
+    target = project_dir / PLUGIN_PATH
     if target.exists() and not force:
         raise FileExistsError(f"Refusing to overwrite existing OpenCode plugin: {target} (pass force=True)")