Version: graphifyy 0.9.11 (uv tool install), macOS. Reproduced on 0.9.9 and 0.9.11.
Symptom: graphify check-update . exits 0 with no output even when the corpus has drifted substantially since the last extract. In our repo the graph was extracted ~1 day earlier; since then 110+ extractable files changed, including entire new modules (a new test suite, new app pages). check-update reports nothing.
Cause (from observation): the new files are absent from graphify-out/manifest.json — check-update appears to only compare files already present in the manifest, so anything created after the last extract is invisible. Verified directly: files added since the last extract have no manifest entry and check-update stays silent; a manifest-tracked file with unchanged mtime is correctly considered fresh.
Why it matters: check-update is the natural staleness detector to wire into a session-start hook. A detector that can't see new files misses exactly the drift it exists to catch. We've replaced it with a git-based check (git diff --name-only $(git log -1 --format=%H -- graphify-out/graph.json)..HEAD) as a workaround.
Suggested fix: walk the corpus (same include/exclude rules as extract) and diff against the manifest keyset — report added/changed/removed counts. Also print a one-line status on success; today success and "didn't really check" are both silent exit 0.
Version: graphifyy 0.9.11 (uv tool install), macOS. Reproduced on 0.9.9 and 0.9.11.
Symptom:
graphify check-update .exits 0 with no output even when the corpus has drifted substantially since the last extract. In our repo the graph was extracted ~1 day earlier; since then 110+ extractable files changed, including entire new modules (a new test suite, new app pages). check-update reports nothing.Cause (from observation): the new files are absent from
graphify-out/manifest.json— check-update appears to only compare files already present in the manifest, so anything created after the last extract is invisible. Verified directly: files added since the last extract have no manifest entry and check-update stays silent; a manifest-tracked file with unchanged mtime is correctly considered fresh.Why it matters: check-update is the natural staleness detector to wire into a session-start hook. A detector that can't see new files misses exactly the drift it exists to catch. We've replaced it with a git-based check (
git diff --name-only $(git log -1 --format=%H -- graphify-out/graph.json)..HEAD) as a workaround.Suggested fix: walk the corpus (same include/exclude rules as extract) and diff against the manifest keyset — report added/changed/removed counts. Also print a one-line status on success; today success and "didn't really check" are both silent exit 0.