Merge pull request #6 from GobbyAI/dev

Release gcode v0.9.2

Author: joshwilhelmi

.gobby/plans/gcode-graph-enhancements.md

@@ -9,6 +9,116 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.9.2] — gcode
+
+### Added
+
+#### gcode
+
+- **Project-id graph clear** — `gcode graph clear --project-id <PROJECT_ID>`
+  now clears a code graph projection by explicit project id before normal
+  project-root resolution. This is the daemon stale-project cleanup path and can
+  run from any cwd without `.gobby/project.json`.
+
+### Fixed
+
+#### gcode
+
+- **Deleted-file projection cleanup** — `gcode index` now removes FalkorDB code
+  graph nodes/edges and Qdrant code-symbol vectors for deleted files before
+  deleting PostgreSQL hub facts. This covers missing explicit
+  `--files <deleted-file>` inputs and whole-project stale/orphan cleanup without
+  relying on daemon reconciliation.
+- **Projection ownership boundary** — code graph clears remain scoped to
+  code-index FalkorDB labels, and code vector clears remain scoped to
+  `code_symbols_{project_id}`. Memory graph nodes and memory vector collections
+  are not targeted by these lifecycle paths.
+
+## [0.9.1] — gcode
+
+### Added
+
+#### gcode
+
+- **Overview graph limit** — `gcode graph overview` now accepts `--limit N`
+  to cap the number of files included in the overview graph, matching the
+  daemon's graph overview limit contract.
+
+### Fixed
+
+#### gcode
+
+- **File graph read aliases** — `gcode graph file` now keeps node file paths
+  and edge metadata file paths under distinct FalkorDB result aliases, fixing
+  duplicate-column failures when returning JSON graph payloads.
+
+## [0.9.0] — gcode
+
+### Added
+
+#### gcode
+
+- **Standalone setup reset boundary** — `gcode setup --standalone` now fails
+  safely when it detects incompatible existing code-index PostgreSQL state and
+  prints guidance to rerun with `--overwrite-code-index` only when a full
+  code-index reset is intended.
+- **Advanced full code-index overwrite** —
+  `gcode setup --standalone --overwrite-code-index` drops/recreates only
+  allowlisted gcode code-index PostgreSQL relations and BM25 indexes, clears
+  code-index graph nodes in FalkorDB, and deletes Qdrant collections with the
+  `code_symbols_` prefix. Gobby project files, config, secrets, tasks,
+  sessions, memory, and daemon-owned data stay untouched.
+- **Rust graph/vector projection lifecycle** — graph reads, graph reports,
+  vector projection sync, and graph/vector lifecycle operations now route
+  through the Rust `gobby-code` library boundary for daemon adoption.
+
+### Changed
+
+#### gcode
+
+- **Project-scoped invalidation** — `gcode invalidate` remains the normal
+  project reset. PostgreSQL deletes stay filtered to the current project, and
+  configured standalone FalkorDB/Qdrant projections are cleaned only for that
+  project.
+- **Shared foundation dependency** — `gobby-code` now consumes
+  `gobby-core 0.2`.
+
+## [0.2.0] — gobby-core
+
+### Added
+
+#### gobby-core
+
+- **Expanded shared foundation** — added reusable context/config contracts,
+  attached/standalone setup contracts, PostgreSQL hub helpers, FalkorDB and
+  Qdrant adapters, standalone service provisioning helpers, indexing
+  primitives, search-fusion primitives, and degradation vocabulary for Rust
+  Gobby CLI consumers.
+
+### Changed
+
+#### gobby-core
+
+- **Consumer dependency line** — workspace consumers now target the
+  `gobby-core 0.2` minor line.
+
+## [0.8.7] — gcode
+
+### Fixed
+
+#### gcode
+
+- **Project identity resolution** — self-referential
+  `parent_project_path` / `parent_project_id` markers now keep the owning
+  `.gobby/project.json` ID, while linked worktrees and isolated roots keep
+  filesystem-scoped code index IDs.
+- **Source `build` package indexing** — root generated `build` / `dist`
+  directories stay excluded, while source directories such as
+  `src/gobby/build/` are indexed.
+- **Duplicate-root pruning** — `gcode prune` now marks stale duplicate project
+  entries for an existing root when they differ from that root's resolved
+  project ID.
+
 ## [0.4.4] — gsqz
 
 ### Fixed

.gobby/plans/gcore-rust-foundation.md

@@ -32,8 +32,9 @@ navigation, and hybrid ranking. When FalkorDB, Qdrant, and an embeddings
 endpoint are configured - typically through Gobby - `gcode` adds graph-aware
 search, semantic search, optional graph expansion for exact symbol lookup
 (`gcode search-symbol --with-graph`), dependency analysis (`callers`, `usages`,
-`imports`, `blast-radius`), and daemon-backed graph lifecycle commands
-(`gcode graph clear`, `gcode graph rebuild`).
+`imports`, `blast-radius`), and Rust-owned graph/vector projection lifecycle.
+`gcode graph clear --project-id <PROJECT_ID>` is available for daemon
+stale-project graph cleanup without cwd project resolution.
 
 For non-Gobby-managed projects, `gcode init` installs the bundled `gcode` skill
 for Claude Code, Codex, Droid, Grok, Qwen, Gemini CLI (deprecated
@@ -52,7 +53,9 @@ One command to launch Claude Code or Codex against a local LLM backend. Auto-det
 
 Sandbox-tolerant hook dispatcher invoked by host AI CLIs (Claude Code, Codex, Gemini CLI, Qwen CLI) on lifecycle and tool-use events. Spools envelopes to `~/.gobby/hooks/inbox/` *before* POSTing to the local Gobby daemon, so the daemon's drain worker can replay any delivery lost to a sandbox FS-read denial, network blip, or daemon restart. You don't usually invoke it directly — Gobby wires it into your AI CLI for you.
 
-`gobby-core` underpins them all — a small shared-primitives library (project root walk-up, bootstrap config, daemon URL). Not a standalone tool.
+`gobby-core` underpins them all — a small shared-primitives library for project
+root walk-up, bootstrap config, daemon URL composition, setup/provisioning
+contracts, and optional datastore adapters. It is not a standalone tool.
 
 ## Documentation
 
@@ -100,6 +103,17 @@ Bootstrap fallback is valid only when `hub_backend: postgres` and bootstrap
 contains an inline `database_url`. Bootstrap `database_url_ref` is rejected
 during bootstrap validation; it is never resolved or used to restart the
 fallback chain.
+
+For daemon-independent service provisioning, use `gcode setup --standalone`.
+The default setup path is non-destructive. If incompatible code-index state is
+already present, rerun with `gcode setup --standalone --overwrite-code-index`
+only when you intend to reset all gcode-owned code-index PostgreSQL,
+FalkorDB, and Qdrant projection state.
+
+Graph/vector lifecycle is code-index scoped. FalkorDB clears target only
+code-index labels, and Qdrant clears target only `code_symbols_{project_id}`;
+Gobby memory graph and memory vector collections stay outside this boundary.
+
 Installing from source or crates.io requires Rust 1.88+.
 
 ### From source

CHANGELOG.md

@@ -1,6 +1,6 @@
 [package]
 name = "gobby-code"
-version = "0.8.6"
+version = "0.9.2"
 edition = "2024"
 rust-version = "1.88"
 authors = ["Josh Wilhelmi <hello@gobby.ai>"]
@@ -12,13 +12,17 @@ readme = "README.md"
 keywords = ["code-search", "ast", "code-index", "developer-tools", "gobby"]
 categories = ["command-line-utilities", "development-tools"]
 
+[lib]
+name = "gobby_code"
+path = "src/lib.rs"
+
 [[bin]]
 name = "gcode"
 path = "src/main.rs"
 
 [dependencies]
 # Internal
-gobby-core = { path = "../gcore", version = "0.1" }
+gobby-core = { path = "../gcore", version = "0.2", features = ["postgres", "falkor", "qdrant", "search", "indexing"] }
 
 # CLI
 clap = { version = "4", features = ["derive"] }

Cargo.lock

@@ -136,18 +136,21 @@ gcode symbols <id1> <id2> ...             # Batch retrieve
 gcode tree                                # File tree with symbol counts
 
 # Dependency graph reads (requires FalkorDB)
+gcode graph overview --limit 100          # Project overview graph
 gcode callers "handleAuth"                # Who calls this?
 gcode usages "handleAuth"                 # Incoming call sites
 gcode imports src/auth.ts                 # Import graph for a file
 gcode blast-radius "handleAuth" --depth 3 # Transitive impact analysis
 
-# Graph lifecycle (requires Gobby daemon)
+# Graph lifecycle (requires FalkorDB)
 gcode graph clear                         # Clear current project's graph projection
+gcode graph clear --project-id <id>       # Clear graph projection by explicit project id
 gcode graph rebuild                       # Rebuild current project's graph projection
 
 # Project management
 gcode status                              # Index stats
 gcode projects                            # List all indexed projects
+gcode setup --standalone                  # Provision daemon-independent services
 gcode index                               # Re-index (incremental)
 gcode invalidate                          # Clear index, force full re-index
 
@@ -193,7 +196,7 @@ source of truth for code-index rows.
 codebase → tree-sitter → PostgreSQL hub + pg_search BM25
                           FalkorDB              → call graphs, blast radius, imports
                           Qdrant + embeddings   → semantic vector search
-                          Gobby daemon          → auto-indexing, graph/vector sync,
+                          Gobby daemon          → auto-indexing, graph/vector orchestration,
                                                   config, secrets, sessions, agents
 ```
 
@@ -217,7 +220,7 @@ bootstrap `database_url`. Bootstrap `database_url_ref` is rejected.
 | Semantic vector search | When Qdrant + embeddings are configured | Yes |
 | Call graph / blast radius | When FalkorDB is configured | Yes |
 | Import graph | When FalkorDB is configured | Yes |
-| Graph clear / rebuild lifecycle | Requires daemon | Yes |
+| Graph clear / rebuild lifecycle | When FalkorDB is configured | Yes |
 | Auto-indexing on file change | Manual `gcode index` | Yes (daemon file watcher) |
 | Centralized config + secrets | Reads PostgreSQL `config_store` + secrets | Yes |
 | Shared index (daemon + CLI) | PostgreSQL hub | PostgreSQL hub |
@@ -237,9 +240,11 @@ Get started with Gobby at [github.com/GobbyAI/gobby](https://github.com/GobbyAI/
 | PostgreSQL hub unavailable | Runtime index/search commands fail with a bootstrap or connection error. |
 | No index yet | Commands error with `Run gcode init to initialize`. |
 
-Read-side graph commands depend on FalkorDB. `gcode graph clear` and `gcode graph rebuild`
-are separate lifecycle operations routed through the Gobby daemon for the
-current resolved project.
+Read-side graph commands and graph lifecycle depend on FalkorDB. Vector
+lifecycle depends on Qdrant plus embeddings for sync/rebuild. All code-index
+projection lifecycle paths are Rust-owned and scoped to code projection state:
+graph clears target code-index FalkorDB labels only, and vector clears target
+only `code_symbols_{project_id}` rather than memory vector collections.
 
 ## Language Support