codespine 1.0.10__tar.gz → 1.0.12__tar.gz

{codespine-1.0.10 → codespine-1.0.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: codespine
-Version: 1.0.10
+Version: 1.0.12
 Summary: Local Java code intelligence indexer backed by a graph database
 Author: CodeSpine contributors
 License: MIT License
@@ -66,7 +66,7 @@ Dynamic: license-file
 
 # CodeSpine
 
-**v1.0.10** — Local Java code intelligence for coding agents, backed by a graph database.
+**v1.0.12** — Local Java code intelligence for coding agents, backed by a graph database.
 
 CodeSpine cuts token burn for coding agents working on Java codebases.
 
@@ -111,6 +111,7 @@ pip install "codespine[ui]"
 ```
 
 The current lite UI is dependency-free and served locally by CodeSpine; the `ui` extra is the stable add-on install target for the browser explorer.
+Quotes are required in zsh: use `pip install "codespine[ui]"`, not `pip install codespine[ui]`.
 
 Everything at once (ml + community detection):
 
@@ -323,12 +324,14 @@ Higher-level tools designed to answer full agent questions in a single call, wit
 
 ```bash
 # Indexing
-codespine analyse <path>                     # incremental index (default)
+codespine analyse <path>                     # trust-first incremental index (default)
 codespine analyse <path> --full              # full re-index from scratch
-codespine analyse <path> --budget 90         # fast index with a resolver deadline
+codespine analyse <path> --fast --budget 90  # budgeted partial core index
 codespine analyse <path> --complete --deep   # + communities, flows, dead code, coupling
 codespine analyse <path> --complete --incremental-deep
 codespine analyse <path> --embed             # + vector embeddings
+codespine repair <project-id-or-path>        # retry failed or incomplete phase
+codespine repair <project-id-or-path> --full # force full core rebuild
 
 # Background jobs and local UI
 codespine background                         # background task progress
@@ -381,7 +384,7 @@ codespine force-reset                        # emergency: delete all data files
 
 `analyse` defaults to incremental mode. Repeat runs only process changed files and are fast.
 
-`analyse` runs in fast mode by default: it indexes the core graph, publishes that read replica from a detached process, then continues communities, flows, dead code, coupling, and cross-module enrichment in the background. Use `codespine tasks` or `codespine ui` to watch that work. Use `--complete --deep` when you want those passes refreshed before the command returns.
+`analyse` is trust-first by default: it completes the core graph in the foreground, validates and publishes the read replica, then keeps deep enrichment moving in the background. Use `--fast` only when you want a budgeted partial core index. Use `codespine background`, `codespine ui`, or `codespine repair` to inspect and recover incomplete or degraded work.
 
 ---
 
@@ -567,11 +570,15 @@ The deep analysis phase covers four passes that are expensive but optional:
 | Dead code | Finds methods with no callers (Java-aware exemptions) | Cleanup audits |
 | Change coupling | Analyses git history for co-changed file pairs | `get_change_coupling`, `related` |
 
-**Fast default:** `codespine analyse` prioritizes a queryable core index. Communities, flows, dead-code, git coupling, and cross-module links are queued in a detached background enrichment job unless you use `--complete`.
+**Trust-first default:** `codespine analyse` now treats success as “the core graph is complete, validated, and queryable.” The default foreground path finishes parse, DB writes, call resolution, type resolution, DI resolution, and snapshot publish before it returns. Deep enrichment still continues in the background unless you use `--complete --deep`.
+
+**Fast mode:** `codespine analyse --fast` keeps the old budgeted behavior for large repos. If the budget expires before the core graph is complete, CodeSpine publishes a partial snapshot, marks the project as partial, and tracks the background continuation until the core graph is repaired.
 
 **Health checks:** every analyse run now performs a small self-test query suite and reports index anomalies such as large projects with zero call edges. Use `codespine health` for the terminal dashboard or `codespine self-test --json` in CI.
 
-**Background visibility:** `codespine background` shows running background job progress in the terminal, and `codespine tasks` remains available as the shorter registry view. `codespine ui` serves a local read-only index explorer with project counts, index health, and the same background task state at `http://127.0.0.1:8765`.
+**Background visibility:** `codespine background` shows status, result, last phase, progress, and repair hints in the terminal, and `codespine tasks` remains available as the shorter registry view. `codespine ui` serves a local explorer with project state (`ready`, `enriching`, `partial`, `degraded`, `repair_required`), background tasks, and one-click Repair/Reindex actions at `http://127.0.0.1:8765`.
+
+**Repair flows:** `codespine repair <project-id-or-path>` retries the failed or incomplete phase first. Use `--full` when the project needs a full core rebuild.
 
 **Complete deep:** `--complete --deep` runs the expensive enrichment passes before returning. `--complete --incremental-deep` combines incremental file indexing with a forced full deep pass.
 

{codespine-1.0.10 → codespine-1.0.12}/README.md

@@ -1,6 +1,6 @@
 # CodeSpine
 
-**v1.0.10** — Local Java code intelligence for coding agents, backed by a graph database.
+**v1.0.12** — Local Java code intelligence for coding agents, backed by a graph database.
 
 CodeSpine cuts token burn for coding agents working on Java codebases.
 
@@ -45,6 +45,7 @@ pip install "codespine[ui]"
 ```
 
 The current lite UI is dependency-free and served locally by CodeSpine; the `ui` extra is the stable add-on install target for the browser explorer.
+Quotes are required in zsh: use `pip install "codespine[ui]"`, not `pip install codespine[ui]`.
 
 Everything at once (ml + community detection):
 
@@ -257,12 +258,14 @@ Higher-level tools designed to answer full agent questions in a single call, wit
 
 ```bash
 # Indexing
-codespine analyse <path>                     # incremental index (default)
+codespine analyse <path>                     # trust-first incremental index (default)
 codespine analyse <path> --full              # full re-index from scratch
-codespine analyse <path> --budget 90         # fast index with a resolver deadline
+codespine analyse <path> --fast --budget 90  # budgeted partial core index
 codespine analyse <path> --complete --deep   # + communities, flows, dead code, coupling
 codespine analyse <path> --complete --incremental-deep
 codespine analyse <path> --embed             # + vector embeddings
+codespine repair <project-id-or-path>        # retry failed or incomplete phase
+codespine repair <project-id-or-path> --full # force full core rebuild
 
 # Background jobs and local UI
 codespine background                         # background task progress
@@ -315,7 +318,7 @@ codespine force-reset                        # emergency: delete all data files
 
 `analyse` defaults to incremental mode. Repeat runs only process changed files and are fast.
 
-`analyse` runs in fast mode by default: it indexes the core graph, publishes that read replica from a detached process, then continues communities, flows, dead code, coupling, and cross-module enrichment in the background. Use `codespine tasks` or `codespine ui` to watch that work. Use `--complete --deep` when you want those passes refreshed before the command returns.
+`analyse` is trust-first by default: it completes the core graph in the foreground, validates and publishes the read replica, then keeps deep enrichment moving in the background. Use `--fast` only when you want a budgeted partial core index. Use `codespine background`, `codespine ui`, or `codespine repair` to inspect and recover incomplete or degraded work.
 
 ---
 
@@ -501,11 +504,15 @@ The deep analysis phase covers four passes that are expensive but optional:
 | Dead code | Finds methods with no callers (Java-aware exemptions) | Cleanup audits |
 | Change coupling | Analyses git history for co-changed file pairs | `get_change_coupling`, `related` |
 
-**Fast default:** `codespine analyse` prioritizes a queryable core index. Communities, flows, dead-code, git coupling, and cross-module links are queued in a detached background enrichment job unless you use `--complete`.
+**Trust-first default:** `codespine analyse` now treats success as “the core graph is complete, validated, and queryable.” The default foreground path finishes parse, DB writes, call resolution, type resolution, DI resolution, and snapshot publish before it returns. Deep enrichment still continues in the background unless you use `--complete --deep`.
+
+**Fast mode:** `codespine analyse --fast` keeps the old budgeted behavior for large repos. If the budget expires before the core graph is complete, CodeSpine publishes a partial snapshot, marks the project as partial, and tracks the background continuation until the core graph is repaired.
 
 **Health checks:** every analyse run now performs a small self-test query suite and reports index anomalies such as large projects with zero call edges. Use `codespine health` for the terminal dashboard or `codespine self-test --json` in CI.
 
-**Background visibility:** `codespine background` shows running background job progress in the terminal, and `codespine tasks` remains available as the shorter registry view. `codespine ui` serves a local read-only index explorer with project counts, index health, and the same background task state at `http://127.0.0.1:8765`.
+**Background visibility:** `codespine background` shows status, result, last phase, progress, and repair hints in the terminal, and `codespine tasks` remains available as the shorter registry view. `codespine ui` serves a local explorer with project state (`ready`, `enriching`, `partial`, `degraded`, `repair_required`), background tasks, and one-click Repair/Reindex actions at `http://127.0.0.1:8765`.
+
+**Repair flows:** `codespine repair <project-id-or-path>` retries the failed or incomplete phase first. Use `--full` when the project needs a full core rebuild.
 
 **Complete deep:** `--complete --deep` runs the expensive enrichment passes before returning. `--complete --incremental-deep` combines incremental file indexing with a forced full deep pass.
 

{codespine-1.0.10 → codespine-1.0.12}/codespine/__init__.py

@@ -1,4 +1,4 @@
 """CodeSpine package."""
 
 __all__ = ["__version__"]
-__version__ = "1.0.10"
+__version__ = "1.0.12"

{codespine-1.0.10 → codespine-1.0.12}/codespine/analysis/deadcode.py

@@ -197,9 +197,9 @@ def detect_dead_code(store, limit: int = 200, project: str | None = None, strict
                    m.is_constructor as is_constructor,
                    m.is_test as is_test,
                    f.path as file_path
-            LIMIT $limit
+            LIMIT $lim
             """,
-            {"limit": int(limit * 5), "proj": project},
+            {"lim": int(limit * 5), "proj": project},
         )
     else:
         candidates = store.query_records(
@@ -215,9 +215,9 @@ def detect_dead_code(store, limit: int = 200, project: str | None = None, strict
                    m.is_constructor as is_constructor,
                    m.is_test as is_test,
                    f.path as file_path
-            LIMIT $limit
+            LIMIT $lim
             """,
-            {"limit": int(limit * 5)},
+            {"lim": int(limit * 5)},
         )
 
     if not candidates: