sidegraph 0.17.2__tar.gz → 0.18.0__tar.gz

{sidegraph-0.17.2 → sidegraph-0.18.0}/.github/workflows/ci.yml

@@ -180,10 +180,13 @@ jobs:
       - name: Test portable core and MCP contracts
         shell: pwsh
         run: |
-          # The wheel-smoke tests are release-only (tests/private); the public snapshot has no copy.
+          # Private acceptance files are absent from the public snapshot.
           $privateTests = @()
           if (Test-Path "tests/private/test_installed_wheel_smoke.py") {
-            $privateTests = @("tests/private/test_installed_wheel_smoke.py")
+            $privateTests += "tests/private/test_installed_wheel_smoke.py"
+          }
+          if (Test-Path "tests/private/test_older_reader_native.py") {
+            $privateTests += "tests/private/test_older_reader_native.py"
           }
           uv run pytest -q --junitxml="$env:RUNNER_TEMP/windows-core.xml" `
             tests/test_store_mutation_guard.py `
@@ -195,12 +198,14 @@ jobs:
             tests/test_verify_format2_snapshot.py `
             tests/test_store_format.py tests/test_store_rules.py `
             tests/test_maintenance_publish.py tests/test_migrate.py `
+            tests/test_store_junctions.py tests/test_format2_windows.py `
             tests/test_repo_relative_paths_portable.py `
             tests/test_command_windows.py `
             tests/test_hook_payload_encoding.py tests/test_hook_failure_diagnostics.py `
             tests/test_hot_index_facts.py `
             tests/test_delivery_evidence.py tests/test_delivery_stats.py tests/test_delivery_surfaces.py `
             tests/test_git_output_utf8.py `
+            tests/test_githooks_atomic_lock.py::test_windows_pid_probe_is_never_a_signal_from_python `
             tests/test_health_check_skill.py `
             $privateTests
           if ($LASTEXITCODE -ne 0) { exit $LASTEXITCODE }

{sidegraph-0.17.2 → sidegraph-0.18.0}/CHANGELOG.md

@@ -7,6 +7,42 @@ interfaces, exactly, and what each one promises: [`docs/reference/stability.md`]
 
 ## [Unreleased]
 
+## [0.18.0] — 2026-10-26
+
+### Changed
+
+- `get_task_context` and `query_decisions` show at most 5 lines of related memory reached by
+  expansion. Each line has a short choice snippet and the record's id. The rest are counted
+  in one closing `- (+N more related not shown: …)` line. Global-scope rules and a seed's
+  superseded one-liners are not capped.
+
+### Fixed
+
+- Internal Windows directory junctions are refused by the store's link guard, including
+  junctions added before maintenance. Deliberately linked store roots remain supported.
+
+### Tests
+
+- Native Windows CI exercises packed-store migration, edits, compaction, Git checkout under
+  both autocrlf settings, long paths, busy files, case aliases and older-reader refusal.
+
+## [0.17.3] — 2026-10-26
+
+### Fixed
+
+- Graph refresh hooks acquire both the runner lock and stale-breaker gate with exclusive
+  shell PID files. Concurrent hooks remain serialized on systems whose external `mkdir`
+  can report success to two racing callers, while live legacy directory locks are respected.
+- Installer cleanup coordinates with the same breaker gate and preserves a lock whose owner
+  changed during its PID check. Optional native-lock failures no longer prevent publishing
+  an updated helper, and a failed gate PID write no longer leaves a permanent gate.
+- Doctor detects the complete older directory-lock helper; plain `sidegraph-init` repairs
+  it while keeping hook bytes and the recorded choice. Automatic detection conservatively
+  preserves unfamiliar scripts and quoted examples. Run `sidegraph-init` after upgrading
+  in each clone that uses the old helper.
+- Native Windows installer cleanup leaves PID-bearing locks untouched, instead of using
+  Python signal probes on process ids from a potentially different POSIX-shell namespace.
+
 ## [0.17.2] — 2026-10-25
 
 ### Fixed

{sidegraph-0.17.2 → sidegraph-0.18.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.17.2) — the full loop (capture, ratification, mistakes-first
+Sidegraph is pre-1.0 (v0.18.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.17.2 → sidegraph-0.18.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: sidegraph
-Version: 0.17.2
+Version: 0.18.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

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/concepts/retrieval.md

@@ -250,11 +250,18 @@ unrelated question. The render is tiered instead:
   clipped to ~1200 characters, plus `rejected` and `consequences` (when populated) each
   clipped to ~400 characters, rendered as `"(context: ...)"`/`"(rejected: ...)"`/
   `"(consequences: ...)"` suffixes.
-- **Related tier** (`TaskContext.related` — bucket C/D and superseded one-liners): the
-  original tight one-liner — `choice` clipped to ~240 characters, title + snippet only, no
-  `context`/`rejected`/`consequences` at all, regardless of whether those fields are
-  populated. This is also what stops an off-topic decision's `rejected`/`consequences` from
-  repeating across unrelated questions — a related entry never renders them.
+- **Related tier** (`TaskContext.related` — bucket C/D and superseded one-liners): a
+  short one-liner with no `context`/`rejected`/`consequences` and no inline evidence,
+  regardless of whether those fields are populated. This is also what stops an off-topic
+  decision's `rejected`/`consequences` from repeating across unrelated questions — a
+  related entry never renders them. Records reached through community, domain, peripheral
+  or guessed-seed expansion show at most **5** lines, each with `choice` clipped to ~80
+  characters and the record's `(id: …)` so it can be expanded with
+  `retrieve_decisions(ids=[…])`; any further ones are counted in one closing
+  `- (+N more related not shown: …)` line instead of rendered. Most of these records were
+  measured off-task for the task at hand. Two kinds stay outside that cap and keep the
+  plain one-liner (`choice` clipped to ~240 characters, no id): `scope: global` decisions,
+  which are repo-wide rules, and the seed's own superseded one-liners, which are its history.
 
 Every clip cuts at a word boundary with a trailing ellipsis. The one exception is a single unbroken token longer than the limit (a long identifier or URL), which is cut hard at the limit. The per-field
 clips are applied *before* the `memory_chars` check, not a bypass of it: a single
@@ -291,7 +298,7 @@ already on the line (the `(id: …)` suffix these tiers carry).
 
 Whenever at least one marker renders, one fixed legend line is appended to the context
 (and `drill_down` returns it as a separate `"legend"` key) explaining exactly that. The
-related tight tier never carries the marker — no id, no supersede consumer there. Marker
+related tight tier never carries the marker, even on the capped lines that show an id. Marker
 freshness rides a store-meta cache refreshed by the SessionStart/Stop hooks
 (`sync.refresh_code_drift_cache`, one bounded git scan); records superseded mid-session are
 filtered out at read time, so a marker never outlives its record's liveness. Only

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/guides/retrieval-in-sessions.md

@@ -200,8 +200,9 @@ Proposed records use the final quarantine block instead of the accepted sections
 A `Fact` you attached to a decision (its own `facts` list — see
 [`guides/capturing-decisions.md#facts-the-evidence-layer`](capturing-decisions.md#facts-the-evidence-layer))
 rides that decision's line after both records are accepted: the moment an accepted decision is
-rendered in `## ⚠ Known mistakes & gotchas`, `## Decisions`, or `## Related`, its accepted
-supporting facts render right under it, one indented line each. A proposed fact is collected
+rendered in `## ⚠ Known mistakes & gotchas`, `## Decisions`, or as a `scope: global` line in
+`## Related`, its accepted supporting facts render right under it, one indented line each. The
+other `## Related` lines are short capped one-liners and carry no evidence. A proposed fact is collected
 for `## Unratified proposals` instead. The one exception:
 the `~ tried, reverted 2026-01: ...` superseded one-liners also shown under `## Related` never
 get evidence — a reverted decision's evidence isn't useful at that tight, unbudgeted-for-detail

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/guides/troubleshooting.md

@@ -222,8 +222,11 @@ entity file is skipped, an anchor to the same name mints a second entity; once t
 
 ### refresh-helper-outdated
 
-A git hook runs a graph refresh helper that starts Graphify without `GRAPHIFY_NO_AUTO_REFRESH=1`
-(an older Sidegraph wrote it). Graphify 0.9.87 and later refresh the agent skills they installed,
+A git hook runs an older graph refresh helper that uses directory-based locking, or starts
+Graphify without `GRAPHIFY_NO_AUTO_REFRESH=1`.
+The directory lock can admit overlapping rebuilds with uutils `mkdir`; the replacement uses
+exclusive PID files for both the runner lock and the stale-breaker gate.
+Graphify 0.9.87 and later refresh the agent skills they installed,
 such as `~/.claude/skills/graphify/`, on the first run after a Graphify upgrade unless that
 variable is set. One hook that runs the helper is enough for the check to fire, and a recorded "no"
 does not silence it. Run `sidegraph-init` with no flag: it rewrites the helper and keeps your

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/integrations/graphify.md

@@ -242,13 +242,25 @@ the `/graphify` skill's `--update` form).
   [above](#linked-worktrees-read-the-main-checkouts-graph)), so a commit in one does nothing.
   Rebuilding there as well costs about 18 MB and 43 s for a cold build on one field corpus with
   25 worktrees, and agents commit in worktrees constantly.
-- **In the background, one at a time.** Git never waits for the rebuild. A lock directory keeps
+- **In the background, one at a time.** Git never waits for the rebuild. An exclusively created PID file keeps
   one rebuild running; a hook that fires while it runs makes it go once more when it finishes, so
   the graph never settles on a tree older than the last request. A lock left by a job that died
   is detected and cleared: by its pid, or, when the job died before writing one (a full disk, a
-  quota), by its age, ten minutes. `sidegraph-init --hooks` clears such a lock at once. One risk
+  quota), by its age, ten minutes. Re-running `sidegraph-init --hooks` refreshes the helper and clears a dead lock;
+  a fresh lock without a PID is kept until the ten-minute grace period expires. One risk
   remains: after a reboot a pid can belong to a live, unrelated process, and the hook then waits
   until that process exits.
+  Plain `sidegraph-init` also repairs an outdated helper in use, keeping the recorded choice.
+  Older helpers used lock directories; the new helper respects a live old runner and can
+  recover its stale directory. Both the lock and the stale-breaker gate now use shell
+  exclusive creation, so locking does not depend on external `mkdir`.
+  Installer cleanup takes the same breaker gate before removing a dead runner lock. A small
+  native OS lock on `sidegraph-graph-refresh.repair` serializes installers while they recover
+  a dead gate; the coordination file stays in the common git directory to keep a stable inode.
+  Where native locks are unsupported, helper publication still proceeds and optional installer
+  cleanup is skipped. On Windows, PID-bearing locks are left to the POSIX helper to recover,
+  because its PIDs need not be native Windows PIDs. Installing or repairing a helper does not
+  itself start a rebuild.
 - **Where the output goes.** The last rebuild's output is `sidegraph-graph-refresh.log` in the
   common git directory (`.git/` in a normal clone).
 - **No `sidegraph-sync` in the hook.** The next memory call notices the new graph version and

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/reference/cli.md

@@ -1562,7 +1562,7 @@ plain-text line):
 | `orphaned-record` | an open (`proposed`/`accepted`) decision or fact whose every Tier-2 (leaf) anchor is `orphaned`, so retrieval reaches it only through its file or domain; one finding per record, at its canonical file, naming how many leaf anchors it has. Statuses come from `index.db` and read "as of last sync", so the check is skipped while the statuses are not computed for the current graph (see *Skipped checks* below; run `sidegraph-sync`). It is the record-level view of `orphaned-binding` (any record it flags has orphaned bindings, which that code already reports), so it adds no new reason for `--check` to exit `2`. The fix is to rebuild a stale graph, then `sidegraph-sync`; otherwise re-anchor the record with `add_anchors` or the `heal-anchors` skill, or supersede it if the code is gone. Needs a usable `index.db` |
 | `store-uncommitted` | store files nobody committed for at least 24 hours: records, bindings, entities, an archive segment or the root files (`format`, `.gitignore`, `stamping_live_since`) that `git status` shows as new, modified or deleted. One finding, at the store path, naming how many files there are, how old the oldest is and what kinds they are (a new `archive/` segment beside deleted records reads as "a compaction"). A new record or entity file is aged by its ULID name, which a `git stash` cannot rewrite; a modified file, or anything under `bindings/`, by its modification time; a deleted file by its subdirectory's, a lower bound. Entries fully staged in the index are not counted, so a `--check` run in a pre-commit hook does not block the commit that fixes the problem. **`--check` exits `2` on it.** The fix is to commit the store in a pull request. Silent, and not run, outside a git repository, with no `git`, or when git is slower than 2 seconds |
 | `plugin-off-in-subdirectories` | Claude Code sessions started below the repository root run without the Sidegraph plugin. Claude Code reads the project settings (`.claude/settings.json`) of the launch directory only, and the repository root's `.claude/settings.local.json` for every launch inside the repository; `enabledPlugins` merges key by key (user settings, then project, then local). Two problems, reported as up to two findings: (a) the plugin is enabled only in the root's `.claude/settings.json`, so every directory below the root without its own enabling settings runs without it (reported at that file); (b) nested directories with a `.claude/settings.json` or `.claude/settings.local.json` of their own that sets `enabledPlugins` and whose merge leaves the plugin off (reported at the first such directory, naming how many there are; a nested settings file without `enabledPlugins` cannot change the merge, so it is not counted). The walk covers every directory that holds a tracked file (one `git ls-files` over the index, a few tens of milliseconds on a large repository) and looks for the two settings files in each directly, so a repository that ignores `.claude/` is covered. User settings are read from `$CLAUDE_CONFIG_DIR/settings.json` when that variable is set and non-empty, else from `~/.claude/settings.json`. Silent when the plugin is not enabled for a launch at the root at all, and not run outside a git repository, with no `git`, or when `git ls-files` takes longer than 5 seconds. **`--check` exits `2` on it**, like any finding; enabling the plugin at user scope or in the root's `.claude/settings.local.json` clears it |
-| `refresh-helper-outdated` | a git hook runs a graph refresh helper whose Graphify line lacks `GRAPHIFY_NO_AUTO_REFRESH=1` (an older Sidegraph wrote it), so Graphify 0.9.87 and later can rewrite the agent skills they installed on the first rebuild after an upgrade. Advisory, per clone (the helper lives in `.git/hooks`); **`--check` exits `2` on it**, like any finding. One hook that runs the helper is enough, and a recorded decline does not silence it. The fix is `sidegraph-init` (no flag), which refreshes the helper and keeps a recorded hook choice. Silent outside a git repository, with no helper, or when no hook runs it |
+| `refresh-helper-outdated` | a git hook runs an older graph refresh helper that uses directory-based locking (unsafe with uutils `mkdir`), or whose Graphify line lacks `GRAPHIFY_NO_AUTO_REFRESH=1` (Graphify 0.9.87 and later can rewrite installed agent skills after an upgrade). Advisory, per clone (the helper lives in `.git/hooks`); **`--check` exits `2` on it**, like any finding. One hook that runs the helper is enough, and a recorded decline does not silence it. The fix is `sidegraph-init` (no flag), which refreshes the helper and keeps a recorded hook choice. Silent outside a git repository, with no helper, or when no hook runs it |
 | `engine-version` | the graph was built by a Graphify release this Sidegraph was not tested with (its `graph.graphify_version` stamp is neither absent nor in the tested set), so anchors and domains may read differently. Advisory; **`--check` exits `2` on it**, like any finding. Pin Graphify to a tested release listed under [Engine version pinning](../integrations/graphify.md#engine-version-pinning), then rebuild the graph. It also fires for a mention-edge graph (Graphify 0.9.62 or later) over a store without a minimum Sidegraph version; follow the [0.14 migration guide](https://github.com/SantyagoSeaman/sidegraph/blob/main/docs/guides/migrating-to-0.14.md). A malformed marker leaves this second case silent. Silent without a readable graph |
 | `store-not-migrated` | the store uses the pre-0.17 layout (a format marker below major 2) and holds at least one record of any kind (initiatives included). One finding, at the store path, naming `sidegraph-migrate` (run on the default branch, after the team checklist in the [0.17 migration guide](https://github.com/SantyagoSeaman/sidegraph/blob/main/docs/guides/migrating-to-0.17.md)) and the `sidegraph:compact` skill. Degraded; **`--check` exits `2` on it**, like any finding. Silent on an empty store and on a store that is already format 2 |
 | `maintenance-due` | a format-2 store that `sidegraph-compact` would tidy: more than 200 per-record files, or a legacy `archive/` segment it would delete, or a misplaced or duplicated shard line, or a stray shard file. `sidegraph-verify` does not report these; maintenance heals them. A segment kept because one of its lines is not safe to delete does not count. Advisory; **`--check` exits `2` on it**, like any finding. Run `sidegraph-compact` on the default branch. Silent on a store that is not format 2 |

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/reference/hooks.md

@@ -402,6 +402,13 @@ raises costs only its own line.
     > installed on the first rebuild after an upgrade. Ask the user to run `sidegraph-init`,
     > which refreshes the helper and keeps their recorded hook choice; do not run it unasked.
 
+    A helper using the old directory-based lock is also reported: uutils `mkdir` can admit
+    overlapping rebuilds. `sidegraph-init` replaces it with exclusive PID-file locking while
+    preserving hook bytes and the recorded choice. The outdated-helper check recognizes concrete defects in simple shell helpers,
+    rather than comparing the whole template. It conservatively skips unfamiliar scripts with
+    heredocs or multiline quotes. This controls automatic defect repair; an ordinary init
+    that refreshes a fully installed hook still rewrites its managed helper.
+
     It also sends a notice for the person. See
     [`refresh-helper-outdated`](../guides/troubleshooting.md#refresh-helper-outdated).
 15. **Refresh-hook line.** When no git hook keeps the graph fresh, one line tells the model to

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/reference/mcp-tools.md

@@ -788,7 +788,9 @@ degrades to un-synced retrieval, never an error), resolves `files`/`entities` in
 and returns a rendered Markdown string with up to six sections — accepted mistakes (with
 accepted inline evidence facts), accepted decisions (with accepted inline evidence), accepted
 known facts (standalone), structural map, related accepted memory, and unratified proposals —
-under the given character budgets. See
+under the given character budgets. Related memory reached by expansion shows at most 5 short
+lines with ids, plus a count of the rest; see
+[retrieval: two-tier rendering](../concepts/retrieval.md). See
 [retrieval: facts](../concepts/retrieval.md#facts-inline-evidence-and-the-known-facts-bucket)
 for the inline-vs-standalone split and the guarantee that facts never displace a mistake. The
 structural map omits

{sidegraph-0.17.2 → sidegraph-0.18.0}/docs/reference/store-format.md

@@ -46,11 +46,12 @@ characters long. Every ULID qualifies. The store refuses to write a record whose
 different from its filename is not a record at all: see
 [Freshness](#freshness-absorbing-a-git-pull) for how a reload treats it.
 
-**Symlinks inside the store are refused.** A `Store` will not open a directory any of whose
+**Symlinks and Windows junctions inside the store are refused.** A `Store` will not open a directory any of whose
 subdirectories (`decisions/`, `facts/`, `domains/`, `entities/`, `bindings/`, `initiatives/`,
 `archive/`, `verifications/`, `shards/`), store files (`format`, `stamping_live_since`,
 `domain-snapshot.json`, `.gitignore`, `.gitattributes`, `index.db`, and
-SQLite's `index.db-journal`, `-wal` and `-shm`) or shard files (`shards/*.shard`) is a symlink, live or dangling: a linked
+SQLite's `index.db-journal`, `-wal` and `-shm`) or shard entries (`shards/*.shard`) is a symlink
+(live or dangling) or Windows directory junction: a linked
 `decisions/` would send every record write to the link's target, and a linked `index.db` would
 make SQLite write there. The error names the entry (`… inside the store is a symlink`);
 replace it with a real directory or file. `sidegraph-verify` reports each such entry as
@@ -58,10 +59,29 @@ replace it with a real directory or file. `sidegraph-verify` reports each such e
 `--against` comparison until the links are removed, and its text output says so in one line.
 An `--against` ref that does not resolve, or a store outside git, is checked before the stop and
 exits `1` without reporting the links.
-`sidegraph-doctor` does the same and skips its advisory checks. A symlinked store **root**
+`sidegraph-doctor` does the same and skips its advisory checks. Junctions use the same
+`symlinked-store-entry` code and existing symlink error wording. A deliberately linked store **root**
 (`.sidegraph -> ../shared/store`) is fine: a deliberately shared store is a real use. Record
 files inside a real subdirectory are still read as they are.
 
+On Windows, format-2 maintenance writes shard bytes in binary mode, avoiding Python's
+newline conversion. The store's `*.shard -text` Git attribute preserves those LF bytes
+across checkout under either `core.autocrlf` setting. If another application holds a shard open
+without delete sharing, replacement can fail with `PermissionError`. The error propagates;
+maintenance does not delete the source files it has not finished publishing. Close the other
+application and rerun the operation. Filesystem path/component limits likewise remain
+operational errors; use a shorter store path if the host or Git cannot handle long paths
+(`core.longpaths=true` enables Git for Windows' long-path support).
+That option does not guarantee every Git operation can start from a directory longer than
+260 characters. If Git refuses the store directory during migration's entry checks, the
+marker and records remain unchanged; use a shorter checkout/store path and retry.
+
+Verify each committed operation against its input commit: migration against the format-1
+commit, a record edit against the migrated commit, and compaction against the commit containing
+the edited hot file. A compaction comparison checks that each published body existed in its
+baseline; comparing an edited, compacted body directly to a ref before the edit does not meet
+that requirement.
+
 **A symlinked store belongs to the project that holds the link.** The code a record is anchored
 to lives in that project, so the repository Sidegraph asks about the store is the project's, not
 the one the link points into: the `provenance.commit` stamped at capture is the project's `HEAD`

{sidegraph-0.17.2 → sidegraph-0.18.0}/package.json

@@ -1,6 +1,6 @@
 {
   "name": "sidegraph",
-  "version": "0.17.2",
+  "version": "0.18.0",
   "type": "module",
   "exports": "./index.js"
 }

{sidegraph-0.17.2 → sidegraph-0.18.0}/plugin/sidegraph/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "sidegraph",
   "displayName": "Sidegraph",
-  "version": "0.17.2",
+  "version": "0.18.0",
   "description": "Durable decision/lessons memory over your code graph — ADRs, gotchas, and constraints that survive refactors, retrieved mistakes-first.",
   "author": { "name": "SantyagoSeaman", "url": "https://github.com/SantyagoSeaman" },
   "homepage": "https://github.com/SantyagoSeaman/sidegraph",

{sidegraph-0.17.2 → sidegraph-0.18.0}/plugin/sidegraph/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "sidegraph",
-  "version": "0.17.2",
+  "version": "0.18.0",
   "description": "Durable decision/lessons memory over your code graph — ADRs, gotchas, and constraints that survive refactors, retrieved mistakes-first.",
   "license": "Apache-2.0",
   "skills": "./skills/",

{sidegraph-0.17.2 → sidegraph-0.18.0}/plugin/sidegraph/.muse-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "name": "sidegraph",
-  "version": "0.17.2",
+  "version": "0.18.0",
   "description": "Durable decisions, facts and lessons over your code graph.",
   "compat": {
     "source": "native",

{sidegraph-0.17.2 → sidegraph-0.18.0}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "sidegraph"
-version = "0.17.2"
+version = "0.18.0"
 description = "Own the memory, rent the graph — a durable decision/lessons layer as a sidecar over a code-graph engine."
 readme = "README.md"
 requires-python = ">=3.13"

{sidegraph-0.17.2 → sidegraph-0.18.0}/src/sidegraph/__init__.py

@@ -30,7 +30,7 @@ if TYPE_CHECKING:
     )
     from .store import Store
 
-__version__ = "0.17.2"
+__version__ = "0.18.0"
 
 # name -> the submodule that defines it
 _LAZY = {

{sidegraph-0.17.2 → sidegraph-0.18.0}/src/sidegraph/cli.py

@@ -416,11 +416,14 @@ def _hook_graph_problem(
 
 
 def _refresh_outdated_helper(info: githooks.RepoInfo) -> bool:
-    """Rewrite the helper alone when a hook runs it and it runs Graphify without
+    """Rewrite a helper in use with the old directory lock or a Graphify run without
     ``GRAPHIFY_NO_AUTO_REFRESH=1``; ``True`` when it did. The helper is per repository, so this
     holds whatever graph the store reads; the recorded choice and the hook files are not touched.
     see design/superpowers/specs/2026-10-14-graphify-upgrade-design.md (D7)"""
-    if githooks.helper_is_current(info) is not False or not githooks.helper_in_use(info):
+    old_lock = githooks.helper_uses_directory_lock(info)
+    if (
+        githooks.helper_is_current(info) is not False and not old_lock
+    ) or not githooks.helper_in_use(info):
         return False
     graphify = shutil.which("graphify")
     try:
@@ -428,10 +431,13 @@ def _refresh_outdated_helper(info: githooks.RepoInfo) -> bool:
     except OSError as e:
         print(f"graph refresh hook: could not refresh the helper ({e})")
         return False
-    print(
-        "graph refresh hook: refreshed the helper, which ran Graphify without "
-        f"{githooks.GRAPH_REBUILD_ENV}"
-    )
+    if old_lock:
+        print("graph refresh hook: refreshed the helper, which used directory-based locking")
+    else:
+        print(
+            "graph refresh hook: refreshed the helper, which ran Graphify without "
+            f"{githooks.GRAPH_REBUILD_ENV}"
+        )
     return True