Skip to content

Durable Code Graphs & Honest Provider Readiness

Choose a tag to compare

@Foxfire1st Foxfire1st released this 09 Jun 21:29
· 52 commits to main since this release
6beccd0

Agents Remember 2.5.0

The CodeGraphContext provider becomes durable and honest about readiness, and the toolchain stops fearing Windows long paths. Born from a real incident: a context packet reported green over a 0-node code graph for three days.

Highlights

  • FalkorDB graph data now survives container recreates (configurable dataDestination mount fix)
  • Provider status probes actual graph content: indexed / indexing / empty / backend-unreachable
  • Empty-graph targets degrade the global context packet (ok: false) with per-repo restart recovery actions
  • New additive ProviderSummary.indexing list tells agents a provider is healthy but mid-scan
  • Watcher self-heal entrypoint guard clears poisoned empty graphs at startup (runner image 0.4.10-ar1)
  • Crash-safe, long-path-proof skill/runtime sync and a worktree_start long-path preflight for native Windows

CGC Provider Durability And Readiness

  • FalkorDB data volume binds the backend dataDestination (default /var/lib/falkordb/data, where FalkorDB v4 actually writes) instead of /data; mount verification follows the setting and mismatched containers are recreated on the next backend start.
  • The backend healthcheck requires a genuine PONG, so dataset-LOADING replies no longer count as healthy.
  • cgc_status derives indexingState from a read-only GRAPH.RO_QUERY content probe plus watcher scan markers; indexing stays green at every level while busy targets surface in the compact providers summary and the l-01 trust checkpoint doctrine.
  • All watcher compose runs pass --remove-orphans, cleaning up watchers of de-configured repos.

Windows Long-Path Hardening

  • sync-skills.py / sync-runtime.py use a staged copy-then-swap with \\?\ extended-length path support - a mid-sync crash can no longer gut package_data.
  • worktree_start blocks up front with projected path lengths and remedies when a Windows host without LongPathsEnabled cannot represent the worktree's deepest tracked files.
  • The install guide documents the one-time Windows long-path setup; WSL is unaffected.

All changes are backward-compatible. Fixes #47.