sidegraph 0.21.0__tar.gz → 0.22.0__tar.gz

{sidegraph-0.21.0 → sidegraph-0.22.0}/.github/workflows/ci.yml

@@ -113,6 +113,15 @@ jobs:
       - name: Install dependencies
         run: uv sync --locked
 
+      # The Muse hook adapter runs on the stock macOS python3 (3.9); its test needs a 3.9 here.
+      - name: Install Python 3.9 for the Muse adapter test
+        run: |
+          set -euo pipefail
+          uv python install 3.9
+          py39="$(uv python find --no-project 3.9)"
+          "$py39" -c 'import sys; assert sys.version_info[:2] == (3, 9)'
+          echo "SIDEGRAPH_TEST_PY39=$py39" >> "$GITHUB_ENV"
+
       - name: Run tests
         run: uv run pytest -q --durations=30 --durations-min=1
 

{sidegraph-0.21.0 → sidegraph-0.22.0}/CHANGELOG.md

@@ -7,6 +7,69 @@ interfaces, exactly, and what each one promises: [`docs/reference/stability.md`]
 
 ## [Unreleased]
 
+## [0.22.0] — 2026-10-30
+
+### Changed (Contract change)
+
+- **Packed drift checks (0.22.0).** On a format-2 store, `sidegraph-compact` now folds the
+  committed scoped drift-check files (`verifications/<id>.json`) into one file,
+  `verifications/packed.shard`, and drops dead checks: a check whose decision has a newer check
+  or is superseded, rejected or deprecated. A check file folds once it is tracked and
+  unmodified against `HEAD`. The first run that packs or drops a check raises
+  `requires-sidegraph` to `0.22.0`: 0.17 to 0.21 then refuse the store, and an older pinned
+  `sidegraph-verify` reports `requirement-above-verifier`, so move every teammate and CI pin
+  first. The dry run says so. `sidegraph-verify` reports `packed-checks-without-requirement`
+  and, with `--against`, `packed-check-without-source`; a deleted check is judged per check
+  instead of always illegal. Drift-check files now count toward the `maintenance-due` threshold.
+  A format-1 store and `sidegraph-migrate` are unchanged. See
+  [Scoped drift checks](docs/reference/store-format.md#scoped-drift-checks).
+
+## [0.21.1] — 2026-10-30
+
+### Added
+
+- Muse sessions get the Sidegraph session map at start and a memory brief for subagents,
+  through two plugin hooks that run on the stock macOS `python3`. Approve the hook
+  capabilities with `muse plugins approve sidegraph`.
+
+### Fixed
+
+- On Grok Build, records now reach the agent when it reads, searches, edits or writes a file and when
+  it starts a subagent. The hook did not recognise Grok's tool names, and resolved a relative
+  path against the repository root instead of the directory the session started in; see
+  [`docs/integrations/grok.md`](docs/integrations/grok.md).
+- On Grok Build, the hook now starts for shell reads (`sed`, `grep`, `rg`, `cat`), and the Hooks
+  tab no longer shows the four `if` errors. The plugin gives Grok its own hooks file without the
+  `if` field Grok skips.
+- On Grok Build, every session shared one session key, because Grok names each transcript
+  `updates.jsonl`. A file's records reached the agent once across all Grok sessions, and after
+  ten files no Grok session got records at all. Each Grok session is now keyed by its own id.
+- Grok Build sessions are attributed to Grok, not to Claude Code: hooks stamp the `grok` host
+  family, and MCP calls from Grok are bound to the same session as its hooks. A Grok session
+  no longer gets the notice about Claude Code's settings in subdirectories.
+- Grok Build sessions now see the project's session map. Grok drops the SessionStart hook's
+  output, so as a workaround the MCP server sends the map as its instructions, to Grok clients
+  only; the map carries the domain table of contents but not SessionStart's status lines. It
+  goes away once Grok passes hook context to the model.
+- On Grok Build, the Stop hook now asks for a capture once a session has had two prompts: it
+  reads Grok's own transcript, ignores the Stop Grok sends when a process exits and on the
+  turns Grok starts itself, and never asks in a headless `grok -p` run, where the request would
+  be printed into the run's output.
+- On Grok Build, the first `SessionStart` after installing no longer runs out of time: it downloads
+  and builds Sidegraph (5–7 seconds measured on its own, about 10 inside Grok), past Grok's
+  5-second default for a hook. The Grok hooks file now gives `SessionStart` 30 seconds and the
+  file and subagent hooks 10.
+- Grok Build is no longer marked experimental: with the hooks, the session map and the capture
+  request working, the README and the Grok guide list it beside Claude Code and Codex. The Grok
+  guide adds what to do when the plugin is disabled, and that under `--sandbox read-only` the
+  hooks deliver no records.
+- A malformed line in a session transcript (a `method`, `origin.kind` or `promptSource` that is
+  a list or an object) no longer stops the prompt count, which had silently dropped the capture
+  reminder for that session.
+- The Muse install and update instructions in the README and the Muse guide now use the
+  public marketplace (`muse plugins marketplace add`, `install sidegraph@sidegraph`) instead
+  of a maintained local clone of the repository.
+
 ## [0.21.0] — 2026-10-28
 
 ### Changed

{sidegraph-0.21.0 → sidegraph-0.22.0}/CLAUDE.md

@@ -13,7 +13,7 @@ task-aware retrieval + decision memory riding on the engine's entity graph.
 continuing participant in the project. A core feature must preserve, organize, or deliver
 accumulated project understanding. Document search by itself is not the product.
 
-Sidegraph is pre-1.0 (v0.21.0) — the full loop (capture, ratification, mistakes-first
+Sidegraph is pre-1.0 (v0.22.0) — the full loop (capture, ratification, mistakes-first
 retrieval, refactor-surviving re-anchoring, semantic docs layer, mind-model domains, and the
 facts evidence layer) ships and is exercised end-to-end, but interfaces may still move before
 a stable release. See

{sidegraph-0.21.0 → sidegraph-0.22.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sidegraph
-Version: 0.21.0
+Version: 0.22.0
 Summary: Own the memory, rent the graph — a durable decision/lessons layer as a sidecar over a code-graph engine.
 Project-URL: Homepage, https://github.com/SantyagoSeaman/sidegraph
 Project-URL: Repository, https://github.com/SantyagoSeaman/sidegraph
@@ -48,9 +48,10 @@ the files and symbols an agent is working on.
 
 Records live in your repository as reviewable JSON files. A derived SQLite index supports
 retrieval; [Graphify](https://github.com/Graphify-Labs/graphify) supplies the code and document
-graph used to anchor records. Claude Code and Codex plugins connect capture and retrieval
-to coding sessions. OpenCode V2 and the experimental Muse and Grok Build expose MCP tools and shared skills
-for explicit retrieval and capture.
+graph used to anchor records. Claude Code, Codex and Grok Build plugins connect capture and
+retrieval to coding sessions. OpenCode V2 and the experimental Muse expose MCP tools and shared
+skills for explicit retrieval and capture; Muse also receives the session map and a subagent
+brief.
 
 - Keep decisions, rejected alternatives, and evidence with their provenance and history.
 - Hand the agent the relevant mistakes and constraints before it edits, sized to fit its context.
@@ -83,8 +84,7 @@ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | ie
 ```
 
 Linux follows the macOS commands but is not among the checked platforms. Open a new terminal afterwards so `uv` is on your PATH, then change into the root of your
-repository (`cd /path/to/your/repo`). Every command below runs there, except the Muse
-install, which says otherwise.
+repository (`cd /path/to/your/repo`). Every command below runs there.
 
 **Already using Sidegraph?** (New here? Skip to step 1.) Follow the [0.14 migration guide](docs/guides/migrating-to-0.14.md)
 before upgrading Graphify, so accepted domains keep their membership. Update every client
@@ -148,9 +148,9 @@ Details: [`sidegraph-init`](docs/reference/cli.md#sidegraph-init).
 |---|---|---|
 | Claude Code | yes: hooks, capture reminders, context on reads | macOS and Windows |
 | Codex | yes: hooks, after you approve them | macOS and Windows |
-| Muse (experimental) | no: MCP and skills | macOS |
+| Muse (experimental) | partly: session map and subagent brief, after you approve them | macOS |
 | OpenCode V2 | no: MCP and skills | macOS |
-| Grok Build (experimental) | no: MCP and skills | macOS |
+| Grok Build | yes: hooks, capture reminders, context on reads; the session map through the MCP server | macOS |
 
 Claude Code is shown first; open the section for another host. Host plugin updates and the
 MCP runtime are separate: the default runtime follows the public repository's `main`, which
@@ -207,12 +207,14 @@ or later. See the [Codex guide](docs/getting-started/codex-setup.md#keep-the-plu
 </details>
 
 <details>
-<summary><strong>Grok Build</strong> (experimental)</summary>
+<summary><strong>Grok Build</strong></summary>
 
-#### Grok Build (experimental)
+#### Grok Build
 
-MCP and skills only; no automatic session map, read context or capture reminder: ask the
-agent for context and for capture explicitly. Run in a terminal:
+The plugin brings the MCP tools, the skills and the hooks: records arrive when the agent reads,
+searches, edits or writes a file or starts a subagent, and the agent is reminded to propose
+decisions once a session has done some work. Grok does not pass the `SessionStart` hook's output
+to the model, so the session map comes from the MCP server instead. Run in a terminal:
 
 ```sh
 grok plugin marketplace add SantyagoSeaman/sidegraph
@@ -221,8 +223,9 @@ grok plugin install sidegraph@sidegraph
 
 Accept the trust prompt (`--trust` skips it), then start a new Grok session in the repository.
 Ask the agent which Sidegraph tools it has: `get_task_context` should be among them. Checked
-with Grok Build 1.0.62 on macOS: install, MCP tools, skills, and recording and retrieving a
-gotcha across two sessions. Windows is not checked. See the [Grok Build guide](docs/integrations/grok.md).
+on macOS with Grok Build 1.0.70 (hooks, session map, capture reminder) and 1.0.62 (install,
+MCP tools, skills, a gotcha recorded in one session and retrieved in the next). Windows is not
+checked. See the [Grok Build guide](docs/integrations/grok.md).
 For an existing install, run these in your terminal, then start a new session:
 
 ```sh
@@ -237,17 +240,17 @@ grok plugin update sidegraph
 
 #### Muse (experimental)
 
-MCP and shared skills only; no automatic session map, read context or capture reminder.
-Run the install and update commands from the same stable directory outside any project
-(for example, your home directory), not from the repository. Keep that checkout with LF line endings:
+MCP, shared skills, a session map at start and a memory brief for subagents; no context on
+reads and no capture reminder. The hooks need `python3` (3.9 or later; the macOS one works).
+Add the marketplace and install the plugin:
 
 ```sh
-git clone -c core.autocrlf=false https://github.com/SantyagoSeaman/sidegraph.git sidegraph-plugin
-muse plugins install ./sidegraph-plugin/plugin/sidegraph
+muse plugins marketplace add sidegraph https://github.com/SantyagoSeaman/sidegraph
+muse plugins install sidegraph@sidegraph
 muse plugins inspect sidegraph
 ```
 
-Review the MCP capability, then approve it:
+Review the two hook capabilities and the MCP capability, then approve them:
 
 ```sh
 muse plugins approve sidegraph
@@ -255,10 +258,11 @@ muse plugins approve sidegraph
 
 Exit Muse and start a new Muse process from the intended project directory. Restart it there
 whenever you switch projects; selecting a workspace in a running process is insufficient.
-For an existing install, refresh the maintained checkout and inspect the changed capability:
+For an existing install, refresh the marketplace and the plugin, then inspect the changed
+capability:
 
 ```sh
-git -C sidegraph-plugin pull --ff-only
+muse plugins marketplace update sidegraph
 muse plugins update sidegraph
 muse plugins inspect sidegraph
 ```
@@ -269,9 +273,8 @@ Review changes, then approve and restart Muse from the target project:
 muse plugins approve sidegraph
 ```
 
-Basic installation and MCP access were checked on Muse 1.4.7 on macOS; the update command is
-supported by native help, with its full lifecycle and Windows not checked. See the
-[Muse guide](docs/integrations/muse.md).
+Installation, update, MCP approval, the session map and the subagent brief were checked on
+Muse 1.4.14 on macOS; Windows is not checked. See the [Muse guide](docs/integrations/muse.md).
 
 </details>
 
@@ -388,8 +391,9 @@ evaluate it on your own repository.
 ## How it works
 
 1. **Capture.** During a session the agent saves a decision when you ask for one. At the end of
-   a Claude Code or Codex session the plugin reminds it to propose decisions worth keeping.
-   In OpenCode, Muse and Grok Build, ask for capture explicitly. Known secret patterns are redacted before storage (best effort).
+   a Claude Code, Codex or Grok Build session the plugin reminds it to propose decisions worth
+   keeping (on Grok Build in interactive sessions only). In OpenCode and Muse, ask for capture
+   explicitly. Known secret patterns are redacted before storage (best effort).
 2. **Review.** You accept or drop what the agent proposed; Sidegraph calls this *ratifying*.
    Records are JSON in `.sidegraph/`, committed with your code: one file per record, or lines
    in shard files once maintenance has packed them.

{sidegraph-0.21.0 → sidegraph-0.22.0}/README.md

@@ -15,9 +15,10 @@ the files and symbols an agent is working on.
 
 Records live in your repository as reviewable JSON files. A derived SQLite index supports
 retrieval; [Graphify](https://github.com/Graphify-Labs/graphify) supplies the code and document
-graph used to anchor records. Claude Code and Codex plugins connect capture and retrieval
-to coding sessions. OpenCode V2 and the experimental Muse and Grok Build expose MCP tools and shared skills
-for explicit retrieval and capture.
+graph used to anchor records. Claude Code, Codex and Grok Build plugins connect capture and
+retrieval to coding sessions. OpenCode V2 and the experimental Muse expose MCP tools and shared
+skills for explicit retrieval and capture; Muse also receives the session map and a subagent
+brief.
 
 - Keep decisions, rejected alternatives, and evidence with their provenance and history.
 - Hand the agent the relevant mistakes and constraints before it edits, sized to fit its context.
@@ -50,8 +51,7 @@ powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | ie
 ```
 
 Linux follows the macOS commands but is not among the checked platforms. Open a new terminal afterwards so `uv` is on your PATH, then change into the root of your
-repository (`cd /path/to/your/repo`). Every command below runs there, except the Muse
-install, which says otherwise.
+repository (`cd /path/to/your/repo`). Every command below runs there.
 
 **Already using Sidegraph?** (New here? Skip to step 1.) Follow the [0.14 migration guide](docs/guides/migrating-to-0.14.md)
 before upgrading Graphify, so accepted domains keep their membership. Update every client
@@ -115,9 +115,9 @@ Details: [`sidegraph-init`](docs/reference/cli.md#sidegraph-init).
 |---|---|---|
 | Claude Code | yes: hooks, capture reminders, context on reads | macOS and Windows |
 | Codex | yes: hooks, after you approve them | macOS and Windows |
-| Muse (experimental) | no: MCP and skills | macOS |
+| Muse (experimental) | partly: session map and subagent brief, after you approve them | macOS |
 | OpenCode V2 | no: MCP and skills | macOS |
-| Grok Build (experimental) | no: MCP and skills | macOS |
+| Grok Build | yes: hooks, capture reminders, context on reads; the session map through the MCP server | macOS |
 
 Claude Code is shown first; open the section for another host. Host plugin updates and the
 MCP runtime are separate: the default runtime follows the public repository's `main`, which
@@ -174,12 +174,14 @@ or later. See the [Codex guide](docs/getting-started/codex-setup.md#keep-the-plu
 </details>
 
 <details>
-<summary><strong>Grok Build</strong> (experimental)</summary>
+<summary><strong>Grok Build</strong></summary>
 
-#### Grok Build (experimental)
+#### Grok Build
 
-MCP and skills only; no automatic session map, read context or capture reminder: ask the
-agent for context and for capture explicitly. Run in a terminal:
+The plugin brings the MCP tools, the skills and the hooks: records arrive when the agent reads,
+searches, edits or writes a file or starts a subagent, and the agent is reminded to propose
+decisions once a session has done some work. Grok does not pass the `SessionStart` hook's output
+to the model, so the session map comes from the MCP server instead. Run in a terminal:
 
 ```sh
 grok plugin marketplace add SantyagoSeaman/sidegraph
@@ -188,8 +190,9 @@ grok plugin install sidegraph@sidegraph
 
 Accept the trust prompt (`--trust` skips it), then start a new Grok session in the repository.
 Ask the agent which Sidegraph tools it has: `get_task_context` should be among them. Checked
-with Grok Build 1.0.62 on macOS: install, MCP tools, skills, and recording and retrieving a
-gotcha across two sessions. Windows is not checked. See the [Grok Build guide](docs/integrations/grok.md).
+on macOS with Grok Build 1.0.70 (hooks, session map, capture reminder) and 1.0.62 (install,
+MCP tools, skills, a gotcha recorded in one session and retrieved in the next). Windows is not
+checked. See the [Grok Build guide](docs/integrations/grok.md).
 For an existing install, run these in your terminal, then start a new session:
 
 ```sh
@@ -204,17 +207,17 @@ grok plugin update sidegraph
 
 #### Muse (experimental)
 
-MCP and shared skills only; no automatic session map, read context or capture reminder.
-Run the install and update commands from the same stable directory outside any project
-(for example, your home directory), not from the repository. Keep that checkout with LF line endings:
+MCP, shared skills, a session map at start and a memory brief for subagents; no context on
+reads and no capture reminder. The hooks need `python3` (3.9 or later; the macOS one works).
+Add the marketplace and install the plugin:
 
 ```sh
-git clone -c core.autocrlf=false https://github.com/SantyagoSeaman/sidegraph.git sidegraph-plugin
-muse plugins install ./sidegraph-plugin/plugin/sidegraph
+muse plugins marketplace add sidegraph https://github.com/SantyagoSeaman/sidegraph
+muse plugins install sidegraph@sidegraph
 muse plugins inspect sidegraph
 ```
 
-Review the MCP capability, then approve it:
+Review the two hook capabilities and the MCP capability, then approve them:
 
 ```sh
 muse plugins approve sidegraph
@@ -222,10 +225,11 @@ muse plugins approve sidegraph
 
 Exit Muse and start a new Muse process from the intended project directory. Restart it there
 whenever you switch projects; selecting a workspace in a running process is insufficient.
-For an existing install, refresh the maintained checkout and inspect the changed capability:
+For an existing install, refresh the marketplace and the plugin, then inspect the changed
+capability:
 
 ```sh
-git -C sidegraph-plugin pull --ff-only
+muse plugins marketplace update sidegraph
 muse plugins update sidegraph
 muse plugins inspect sidegraph
 ```
@@ -236,9 +240,8 @@ Review changes, then approve and restart Muse from the target project:
 muse plugins approve sidegraph
 ```
 
-Basic installation and MCP access were checked on Muse 1.4.7 on macOS; the update command is
-supported by native help, with its full lifecycle and Windows not checked. See the
-[Muse guide](docs/integrations/muse.md).
+Installation, update, MCP approval, the session map and the subagent brief were checked on
+Muse 1.4.14 on macOS; Windows is not checked. See the [Muse guide](docs/integrations/muse.md).
 
 </details>
 
@@ -355,8 +358,9 @@ evaluate it on your own repository.
 ## How it works
 
 1. **Capture.** During a session the agent saves a decision when you ask for one. At the end of
-   a Claude Code or Codex session the plugin reminds it to propose decisions worth keeping.
-   In OpenCode, Muse and Grok Build, ask for capture explicitly. Known secret patterns are redacted before storage (best effort).
+   a Claude Code, Codex or Grok Build session the plugin reminds it to propose decisions worth
+   keeping (on Grok Build in interactive sessions only). In OpenCode and Muse, ask for capture
+   explicitly. Known secret patterns are redacted before storage (best effort).
 2. **Review.** You accept or drop what the agent proposed; Sidegraph calls this *ratifying*.
    Records are JSON in `.sidegraph/`, committed with your code: one file per record, or lines
    in shard files once maintenance has packed them.

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/README.md

@@ -8,10 +8,10 @@ agent.
 
 1. [Install Sidegraph and Graphify](getting-started/installation.md).
 2. Follow the [end-to-end quickstart](getting-started/quickstart.md).
-3. Use the recommended host path for [Claude Code](getting-started/claude-code-setup.md) or
-   [Codex](getting-started/codex-setup.md), or the MCP/skills-only paths for
-   [OpenCode V2](../.opencode/INSTALL.md), experimental [Muse](integrations/muse.md) and experimental
-   [Grok Build](integrations/grok.md).
+3. Use the recommended host path for [Claude Code](getting-started/claude-code-setup.md),
+   [Codex](getting-started/codex-setup.md) or [Grok Build](integrations/grok.md), or the narrower
+   paths for [OpenCode V2](../.opencode/INSTALL.md) (MCP and skills) and experimental
+   [Muse](integrations/muse.md) (MCP, skills, the session map and a subagent brief).
 4. Run the [four-case verification checklist](guides/verifying-your-setup.md).
 
 If the repository already has ADRs or specs, use the
@@ -62,4 +62,4 @@ it is optional background on evidence, limits, and repository fit.
 - [Git bindings](reference/git-bindings.md)
 - Integrations: [Claude Code](integrations/claude-code.md),
   [Codex](integrations/codex.md), [OpenCode V2](integrations/opencode.md),
-  experimental [Muse](integrations/muse.md), experimental [Grok Build](integrations/grok.md), [Graphify](integrations/graphify.md)
+  experimental [Muse](integrations/muse.md), [Grok Build](integrations/grok.md), [Graphify](integrations/graphify.md)

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/concepts/data-model.md

@@ -295,17 +295,19 @@ The `Initiative` model below is a separate low-level persisted record supported
 
 ## `DriftCheck` — attributed auxiliary inspection
 
-An optional immutable file under `.sidegraph/verifications/` records an explicit agent
+An optional file under `.sidegraph/verifications/` records an explicit agent
 judgment that an existing decision still holds. It preserves the decision and original
 capture provenance; it never ratifies a proposal or proves semantic truth. It is outside
-the shared canonical digest/index record tables. See
+the shared canonical digest/index record tables. A check file is never edited, but on a
+format-2 store `sidegraph-compact` may pack it into `verifications/packed.shard` (the same JSON
+body, one line) and drop it once it is dead: its decision has a newer check or is retired. See
 [scoped checks](../reference/store-format.md#scoped-drift-checks) and
 [`record_drift_check`](../reference/mcp-tools.md#record_drift_check).
 
 | Field | Type | Meaning |
 |---|---|---|
 | `schema_version` | literal `1` | Version of the auxiliary assertion and fixed subject-digest definition; independent of the store format version. |
-| `id` | ULID | Generated check identity, also its immutable filename. Highest generated id is the deterministic per-decision selection rule, not causal ordering. |
+| `id` | ULID | Generated check identity, also its immutable filename (or, once packed, its line's key). Highest generated id is the deterministic per-decision selection rule, not causal ordering. |
 | `decision_id` | str | Existing decision id; terminal or archived decisions remain valid history references. |
 | `checked_at` | aware datetime | UTC time at which the assertion was recorded. |
 | `checked_commit` | str | Full inspected Git HEAD object id, retained as provenance even after squash/clone removes the object locally. |

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/getting-started/installation.md

@@ -9,9 +9,11 @@ file- and domain-linked records without a graph; the complete workflow below ins
 - **Python 3.13+** for Sidegraph (`.python-version` pins it).
 - **Python 3.10+** for Graphify.
 - [`uv`](https://docs.astral.sh/uv/) — used to install and run both.
-- For automatic session integration: [Claude Code](claude-code-setup.md) or
-  [Codex](codex-setup.md). [OpenCode V2](../../.opencode/INSTALL.md) and experimental
-  [Muse](../integrations/muse.md) provide MCP tools and shared skills without lifecycle hooks.
+- For automatic session integration: [Claude Code](claude-code-setup.md),
+  [Codex](codex-setup.md) or [Grok Build](../integrations/grok.md).
+  [OpenCode V2](../../.opencode/INSTALL.md) provides MCP tools and shared skills without
+  lifecycle hooks; experimental [Muse](../integrations/muse.md) adds the session map and a
+  subagent brief through two hooks.
   Other stdio MCP clients can call the tools directly; the CLI also works without a host.
 
 ### Platform coverage
@@ -37,8 +39,8 @@ above, including a Windows 3.14 cell with PowerShell 7 unavailable for preflight
 real host sessions. Windows 3.13 retains PowerShell 7; its launcher checks also cover 5.1.
 Stable publication of 0.14.0 required the full gate to pass without a known-issue exception.
 The README's blue badges summarize release acceptance, rather than live workflow status or
-support for every published version. Muse and OpenCode have the narrower coverage in
-their installation guides and are outside this native matrix.
+support for every published version. Muse, OpenCode and Grok Build have the narrower
+coverage in their installation guides and are outside this native matrix.
 
 On native Windows, the Claude Code hooks run through Git Bash, which comes with Git for
 Windows; the MCP launchers and the Codex hooks need no POSIX shell. The native checks run
@@ -215,8 +217,10 @@ keep `sidegraph@sidegraph`; update cached assets with the host's native update c
 then start a new session and review any changed approvals. The runtime's `@main` does not
 refresh cached skills or manifests. OpenCode V2 uses the
 [canonical Git package guide](../../.opencode/INSTALL.md). Experimental
-[Muse](../integrations/muse.md) supplies MCP/skills only and must be restarted from the
-intended project when switching workspaces; expanded native acceptance is deferred.
+[Muse](../integrations/muse.md) supplies MCP, skills, the session map and a subagent brief,
+and must be restarted from the intended project when switching workspaces; expanded native
+acceptance is deferred. Grok Build installs from its own plugin marketplace; see the
+[Grok Build guide](../integrations/grok.md).
 
 ### Option C — uvx directly from git
 

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/getting-started/quickstart.md

@@ -33,7 +33,8 @@ creates the repo-committed `.sidegraph/` record directories and a gitignored der
 
 Run `sidegraph-init` from the repository root before starting your host session. On Claude Code and Codex, without a
 store, SessionStart shows setup guidance and Stop stays silent; neither creates one.
-OpenCode and Muse use explicit MCP calls instead of lifecycle hooks. If an
+OpenCode uses explicit MCP calls instead of lifecycle hooks, and Muse has no `Stop` hook. On
+Grok Build the setup guidance appears only in Grok's own interface, not to the agent. If an
 older hook already left an empty store, init identifies it as empty and prints setup guidance.
 
 In a terminal, `sidegraph-init` asks two questions. Both default to yes, so pressing Enter twice
@@ -74,8 +75,9 @@ codex plugin add sidegraph@sidegraph
 
 Start a new interactive session in the repository and review its approval prompts; Codex
 hooks require explicit trust through the startup warning or `/hooks`. For OpenCode V2, use
-the [native Git installation guide](../../.opencode/INSTALL.md); for experimental MCP/skills-only
-Muse, use the [Muse guide](../integrations/muse.md) and start its process in this project.
+the [native Git installation guide](../../.opencode/INSTALL.md); for experimental
+Muse, use the [Muse guide](../integrations/muse.md) and start its process in this project; for
+Grok Build, use the [Grok Build guide](../integrations/grok.md).
 The [README host recipes](../../README.md#claude-code) describe installation and updates. For a
 manual or source-checkout setup, use the host-specific page:
 [Claude Code](claude-code-setup.md) or [Codex](codex-setup.md).
@@ -131,5 +133,6 @@ alone and only installs the graph hook.
 
 Next, run the short
 [verification checklist](../guides/verifying-your-setup.md), then
-[name domains](../guides/naming-your-domains.md) if you want a table of contents of your memory. Claude Code and Codex also inject it at
-SessionStart; OpenCode and Muse retrieve it explicitly through MCP.
+[name domains](../guides/naming-your-domains.md) if you want a table of contents of your memory. Claude Code, Codex and Muse also inject it at
+SessionStart; Grok Build receives it through the MCP server's instructions; OpenCode retrieves it
+explicitly through MCP.

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/guides/ci-cd-maintenance.md

@@ -420,5 +420,11 @@ drafts. Proposed content stays below accepted memory and may be hidden by regula
 
 Scoped drift checks are committed auxiliary history under `.sidegraph/verifications/`.
 Use the current `sidegraph-verify` for their schema/reference checks and write-once
-`--against` enforcement; older verifiers ignore them. CI should not create semantic
+`--against` enforcement; older verifiers ignore them. On a format-2 store
+`sidegraph-compact` folds them into `verifications/packed.shard` and drops dead ones, and the
+first such run raises the store's requirement to 0.22.0: move the CI pin to 0.22.0 or newer
+before that pull request merges, or a pinned older `sidegraph-verify` fails with
+`requirement-above-verifier`. `--against` accepts a fold only when each line equals a check
+already on the target branch (`packed-check-without-source`), so land newly recorded checks
+before folding them. CI should not create semantic
 inspection assertions automatically merely to obtain fewer drift warnings.

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/guides/migrating-to-0.17.md

@@ -126,7 +126,7 @@ Maintenance only folds a file that has been on your branch for at least **7 days
 with `--settled-days`), runs on the default branch, and never commits. The 7-day window exists
 so that a record still being ratified or edited stays a plain file where merges handle it
 well. After a run, commit `.sidegraph/` in a pull request. Both SessionStart and
-`sidegraph-doctor` say when maintenance is due: more than 200 per-record files, a legacy
+`sidegraph-doctor` say when maintenance is due: more than 200 per-record files (drift-check files count), a legacy
 `archive/` segment that maintenance would delete, a shard line in the wrong shard file or
 repeated, or a stray shard file.
 

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/guides/team-workflow.md

@@ -168,7 +168,9 @@ survivor and retire the other:
 
 In a packed (format 2) store, `sidegraph-compact` is maintenance: it folds per-record files that
 have settled (landed on the default branch at least seven days ago) into the shard files, byte
-for byte, and deletes a file only once a shard line holds its exact content. It runs on the
+for byte, and deletes a file only once a shard line holds its exact content. It also folds scoped
+drift-check files into `verifications/packed.shard`, drops dead ones, and on the first such run
+raises the store's minimum version to 0.22.0 for the whole team. It runs on the
 default branch and never commits, so review and commit the result in a pull request. See
 [`reference/cli.md`](../reference/cli.md#sidegraph-compact) and the
 [0.17 migration guide](migrating-to-0.17.md). The rest of this section describes the

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/guides/troubleshooting.md

@@ -329,7 +329,7 @@ has nothing to migrate and says nothing. Doctor lists one finding at the store p
 
 ### maintenance-due
 
-A packed (format 2) store has work for `sidegraph-compact`: more than 200 per-record files, a
+A packed (format 2) store has work for `sidegraph-compact`: more than 200 per-record files (drift-check files count), a
 legacy `archive/` segment that maintenance would delete, a shard line in the wrong shard file or
 repeated with an equal body, or a stray shard file. Nothing is broken, and `sidegraph-verify`
 does not report these states. A segment that stays because one of its lines is not safe to
@@ -337,7 +337,7 @@ delete does not count. Run `sidegraph-compact` on the default branch. Doctor lis
 at the store path; `--check` reports it but does not exit `2` on it. A legacy segment that maintenance would delete counts, whether its records are already in shard
 lines or maintenance would pack them. The check does not consult git, so a record file that
 still has to settle (or is untracked) is not predicted. It reads the shard files once; a store
-with more than 200 per-record files is decided from the directory listing.
+with more than 200 per-record files (drift-check files included) is decided from the directory listing.
 
 ### version-skew
 

{sidegraph-0.21.0 → sidegraph-0.22.0}/docs/guides/verifying-your-setup.md

@@ -20,12 +20,16 @@ you can drop the prefix and use the bare `sidegraph-*` names.
 **Success:** the tool is available and returns either task context or `No context found.` A
 missing record is fine; a trailing `## No code graph` block means the code graph is missing or not
 readable (build it with `graphify update .`, or fix its permissions), not that the wiring failed. “Unknown tool”, a different repository's
-records, or a silent SessionStart hook is not fine. For Codex, confirm hook trust before debugging the JSON.
+records, or a silent SessionStart hook is not fine. For Codex, confirm hook trust before debugging the JSON. On Grok Build
+the opening map comes from the MCP server rather than the hook; it is there before the first
+answer, unless the server started slowly, when it arrives after the first tool call (see the [Grok Build guide](../integrations/grok.md)); on Muse, approve the hooks
+first (see the [Muse guide](../integrations/muse.md)).
 
 If this fails, compare the resolved paths with
 [Configuration](../reference/configuration.md#store-path-resolution) and the relevant host
-page: [Claude Code](../getting-started/claude-code-setup.md) or
-[Codex](../getting-started/codex-setup.md).
+page: [Claude Code](../getting-started/claude-code-setup.md),
+[Codex](../getting-started/codex-setup.md), [Grok Build](../integrations/grok.md) or
+[Muse](../integrations/muse.md).
 
 ## Case 2 — Durable capture and retrieval