Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Python aicode-complexitycode-healthcode-intelligencecode-qualitydead-codedeveloper-toolsdocumentationgit-analyticsmcpopen-sourcepythonrefactoringstatic-analysistechnical-debt
release: v0.51.0 — an index that says what it actually covers (#2269)
Swati Ahujae9e58fcdc4d3
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex 10f1c8cde..e56ae2c6c 100644--- a/.claude-plugin/marketplace.json+++ b/.claude-plugin/marketplace.json@@ -14,7 +14,7 @@"name": "repowise","source": "./plugins/claude-code","description": "Codebase intelligence for Claude Code. Indexes your repo into five layers (Graph, Git, Docs, Decisions, Code Health) and gives Claude deep understanding of architecture, ownership, hotspots, decisions, and defect risk — fewer greps, fewer file reads, lower cost per query.",- "version": "0.50.0",+ "version": "0.51.0","category": "productivity","keywords": ["codebase",diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.mdindex 5dcf633a2..c872307a2 100644--- a/docs/CHANGELOG.md+++ b/docs/CHANGELOG.md@@ -9,6 +9,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0---+## [0.51.0] - 2026-09-16++An index makes claims about a repository, and several of them were not being checked. A fast index and a full one described their scope differently in every place that reported it, and a configured cap could be read as achieved coverage. Git history sampling let a file's retained history depend on which of two internal lanes happened to serve it. Pages that fell outside a generation selection could be marked stale and stay stale through every later update, while `doctor` blamed the wrong cause and named a command that could not clear it. An update could call a repository current because its commit had not moved, even when the configuration deciding what to index had changed underneath it. This release makes each of those say what is actually true, and records the coverage a run achieved rather than the coverage it was allowed. Next to that, contract evidence stops depending on whether a handler signature can be recovered from code: a checked-in OpenAPI document is now a provider schema, compared directionally, and local Maven coordinates resolve across a workspace. COBOL is a parsed language.++### Added++- **COBOL is a parsed language** (#1770). `.cbl`, `.cob`, `.cobol` and `.cpy` reach the Good tier: program IDs, sections, paragraphs and data-level symbols are extracted, and literal `CALL` and local `PERFORM` targets resolve. Programs entered externally by JCL or a scheduler no longer produce unsound unreachable-file findings. Dynamic `CALL data-item`, copybook resolution and dialect-specific source formats are deliberately outside this tier and stay silent rather than guess. A 30-file COBOL repository indexed in fast mode read 1,348 symbols and resolved 86 of 88 extracted calls in 6.8 seconds.+- **A checked-in OpenAPI document is a provider schema** (#2227). Previously a provider's wire shape came only from code, so a repository could describe its API precisely in `openapi.yaml` and still produce no request or response evidence. The extractor joins the existing per-repository walk rather than adding a second one, and an operation emits the same `http::<METHOD>::<normalized-path>` identity as a framework route, so it flows through the matching, diagnostics and persistence already in place. Candidate filenames are narrow on purpose, and when exactly one code provider matches the same identity, the code-backed row keeps its file and symbol.+- **OpenAPI request and response schemas are compared directionally** (#2229). Request rules follow what a provider will accept; response rules follow what a consumer may receive; the comparison recurses through object properties and array items for type, requiredness, nullability and enum changes. Comparison runs only when both sides are complete and share an extraction source and comparison key — an incomplete extraction or a source transition produces a stated uncertainty rather than a confident claim that a field was removed.+- **Local Maven package dependencies resolve across a workspace** (#2231). A bounded, filesystem-only effective model reads local parents, reactor modules, properties, dependency management and direct dependencies, then resolves unique coordinates between repositories, carrying manifest, coordinate, version, scope and resolution evidence through the system graph, REST, MCP and the UI. No Maven subprocess, network resolution, transitive solving, BOM import or profile activation is involved; an ambiguous or invalid model is refused with a diagnostic instead of being half-resolved.+- **`index_scope`, one persisted contract for what an index actually covers** (#2246). Run mode and content provenance, the Git tier and both the configured commit cap and the coverage achieved against it, configured and effective file-page caps with eligible / generated / omitted counts, analysis that was unavailable as distinct from analysis intentionally skipped, provider and model details, full-text and semantic search availability with the exact command that restores them, and the state of any pending or resumable upgrade. CLI status, `/api/repos`, the generated AGENTS/CLAUDE guidance and MCP metadata all read that one projection. Older state degrades missing evidence to `unknown` rather than inferring completed coverage from configuration. The default commit limit is unchanged.+- **Onboarding pages are grounded in the repository's own setup evidence** (#2228). Setup guidance is drawn from contributor documents and package manifests, including working directories and exact script invocations, and concept and execution-flow selection now prefers representative lifecycle entry points and subsystem breadth over graph-central internals. Vocabulary corroboration is separated from definition quality, so incidental prose is no longer published as a definition, and generated file references are canonicalized into repository-relative links that resolve to a file page.++### Changed++- **Git history sampling is per-file and monotonic** (#2244). For every eligible rename-free file the sampler retains the newest `min(per_file_limit, available non-merge history)` commits, satisfied through three bounded lanes — the recent repository-wide window, serial deep repository-wide chunks that top up underfilled files without retaining unrelated histories, and a per-file walk only for what remains. Retained history no longer depends on which lane served a file, Git concurrency is bounded by the machine's actual resources rather than a fixed number, and the coverage a run achieved is recorded. The default commit limit is not raised and a bounded index is not reported as complete repository history.+- **Change analysis is separated from git and from transport** (#2263). Scoring composition, independent-change partitioning, review verdicts and symbol-contract classification each have one owner and can be answered without a checkout or a rendering layer; a review decision is carried as data and rendered at the edge. No current surface changes what it returns.++### Fixed++- **Stale-page recovery converges** (#2145, #2254). `update` marked file pages stale on every commit but never the module, SCC or repository-overview pages above them, so model-written summaries drifted from HEAD with `doctor`, `get_stale_pages` and `generate --stale` all reporting clean. Those dependants are now derived from the same scoped cascade during `update`, seeded so they are marked without being regenerated, which keeps sync free of model spend. A successful full generation is authoritative and retires pages outside the current selection, cleaning their vector and full-text entries; full-text cleanup debt is persisted so a failed deletion converges on retry; `doctor` now classifies who owns a stale page and names `update --full` as the reconciliation path; and a page regenerated by an update is no longer marked stale again by that same update.+- **`update` reconciles configuration changes, not just new commits** (#2235). A repository whose commit had not moved was treated as current even when indexing-relevant configuration had changed, leaving clean updates out of step with a fresh index. Configuration is now fingerprinted by the layer it affects — traversal, Git history, health, generation or state alone — and an update rebuilds that layer and its dependants while leaving the rest untouched. Unknown keys take the conservative full-invalidation path, a failed required rebuild keeps the prior fingerprint so the next run retries rather than accepting partial state, and search or vector cleanup that fails after the database transaction is recorded and retried later.+- **A failed embedding batch no longer multiplies across the corpus** (#2251). Reindex retried whole batches blindly, so a provider outage could run for an hour. Failed chunk identities and the stage they failed at are preserved; individual items are retried only for input-specific 400/413/422 failures; two consecutive provider-wide batch failures stop the run; and only a confirmed single-input token-limit failure is adaptively truncated, with a bounded retry count. A restricted-network run now stops in seconds with a clear connection error. Reindex batch size is validated and the underlying failure cause is surfaced.+- **Symbol complexity computed during health analysis is persisted** (#2236), so clean, incremental, resumed and workspace indexing converge on the same symbol IDs and the same stored complexity.+- **Workspace members register and search fans out on a shared database** (#2138, #2195). When a workspace runs against a configured database URL, per-repo indexes live in that database and no `.repowise/wiki.db` file exists — server startup and search fan-out both skipped every member on that basis, so semantic search and full-text search could not reach any non-primary repository.+- **A language query that fails to compile now warns** (#2166, #2177). Compilation failures were silent, so a whole language could quietly extract nothing. Unaffected languages continue indexing normally.+- **The zero-result search rescue stops riding on one common word** (#2092, #2214). The rescue's full-text fallback returned the first row pointing at a code page with no quality check, so a multi-token query where only one ordinary token matched produced a confident suggestion for an unrelated file. A row must now cover at least two distinct query tokens across its title, path and snippet; single-token queries still fire, since the rescue is meant to allow generic names.+- **`editor_files.<id>: false` opt-outs are honored** during `init` and `update` (#2137, #2226), `vscode_mcp: false` included. An explicit per-run override still wins over a persisted opt-out, and Codex MCP and hook registration stay independent of the `agents_md` opt-out.+- **Windows users are warned to stop running server and MCP processes before upgrading** (#2149, #2204), in both `doctor` and the shared update advisory. The note also clarifies that `Repowise: Stop Server` only stops a server the VS Code extension started.+- **Saving or deleting a provider API key no longer reports a false failure** (#2237). The endpoints answer `204 No Content` and the shared API client tried to parse every success as JSON, so a completed mutation surfaced as `Unexpected end of JSON input` and skipped its refresh.+- **DeepSeek reasoning controls match the documented contract** (#2239). `reasoning_effort` is sent at the top level rather than nested in the thinking payload, low effort no longer maps to high, reasoning support is restricted to model IDs that actually have it, and thinking is disabled for streaming chat because the conversation history cannot replay the reasoning content a later tool call would need.+- **Kimi K2 and K3 advertise the controls they have** (#2238). K2 exposes only the disable-thinking control instead of graded choices that all collapsed to the same toggle, K3 exposes and forwards its `low`, `high` and `max` effort levels, and `auto` leaves the provider default alone.+- **Generation progress cannot read above 100%** (#2176, #2224). A job reporting more completed pages than a stale total rendered `4820%`, passed an invalid value to the progress primitive and dropped `aria-valuenow`. The shared primitive now bounds every finite input; non-finite input keeps the indeterminate state.+- **A select inside a dialog opens in front of it** (#2172, #2173). Floating layers are portalled to the document body, so DOM nesting does not settle paint order and the raw z-index did — a dropdown opened behind the dialog overlay while still holding keyboard focus, so typeahead changed a value nobody could see. The `--z-*` scale is documented and guarded by an ordering test.+- **A long AI fix prompt stays inside its modal** (#2249). Unbroken paths and generated identifiers contributed their minimum content width to the dialog and could push the footer, and the Copy prompt action with it, past the right edge.++### Documentation++- The supported COBOL surface and its deferred ceilings are documented (#1770), as is the supported OpenAPI subset, its static evidence boundary and the endpoint-exposure vocabulary (#2229).++---+## [0.50.0] - 2026-09-11Code health had six different vocabularies for one number, and roughly half of what it measured was change history, which rises as a file is worked on. A week of refactoring could drop the headline and print "Declining health" in error red at the person who did the work. This release rebuilds that reading end to end: one absolute band scale wherever a score appears, one figure at the top of the page, a control that says whether you are counting code shape alone or code shape plus history, and a decline that names which half moved and whether an edit can settle it. No score moves. What changes is what the product tells you a score means. Next to it, findings stop being a list you scroll and become a queue you work, with a disposition you record once and never have re-proposed at you. The other change you will notice first is chat: it is no longer a widget in a corner, it is reachable from the row you are already looking at, pointed at that row, with its first answer grounded in the page you asked from.diff --git a/packages/cli/src/repowise/cli/__init__.py b/packages/cli/src/repowise/cli/__init__.pyindex 1da3c9b3c..75508b73f 100644--- a/packages/cli/src/repowise/cli/__init__.py+++ b/packages/cli/src/repowise/cli/__init__.py@@ -16,4 +16,4 @@ from repowise.cli._stdio import _ensure_utf8_stdio# is already UTF-8._ensure_utf8_stdio()-__version__ = "0.50.0"+__version__ = "0.51.0"diff --git a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-reindex.md b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-reindex.mdindex 57496e788..18f4d6d7e 100644--- a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-reindex.md+++ b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-reindex.md@@ -22,7 +22,7 @@ This is useful when:## Available flags- `--embedder gemini|openai|openrouter|ollama|edenai|auto` — embedding provider (default: auto-detect from env vars)-- `--batch-size N` — pages per embedding batch (default: 20)+- `--batch-size N` — pages per embedding batch, must be 1 or greater (default: 32)## Requirementsdiff --git a/packages/core/src/repowise/core/__init__.py b/packages/core/src/repowise/core/__init__.pyindex 63e1de814..7795566a4 100644--- a/packages/core/src/repowise/core/__init__.py+++ b/packages/core/src/repowise/core/__init__.py@@ -6,4 +6,4 @@ generation engine. This is the heart of repowise — all other packages depend oNamespace package: repowise.core is part of the repowise namespace."""-__version__ = "0.50.0"+__version__ = "0.51.0"diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.mdindex 5dcf633a2..c872307a2 100644--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md@@ -9,6 +9,48 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0---+## [0.51.0] - 2026-09-16++An index makes claims about a repository, and several of them were not being checked. A fast index and a full one described their scope differently in every place that reported it, and a configured cap could be read as achieved coverage. Git history sampling let a file's retained history depend on which of two internal lanes happened to serve it. Pages that fell outside a generation selection could be marked stale and stay stale through every later update, while `doctor` blamed the wrong cause and named a command that could not clear it. An update could call a repository current because its commit had not moved, even when the configuration deciding what to index had changed underneath it. This release makes each of those say what is actually true, and records the coverage a run achieved rather than the coverage it was allowed. Next to that, contract evidence stops depending on whether a handler signature can be recovered from code: a checked-in OpenAPI document is now a provider schema, compared directionally, and local Maven coordinates resolve across a workspace. COBOL is a parsed language.++### Added++- **COBOL is a parsed language** (#1770). `.cbl`, `.cob`, `.cobol` and `.cpy` reach the Good tier: program IDs, sections, paragraphs and data-level symbols are extracted, and literal `CALL` and local `PERFORM` targets resolve. Programs entered externally by JCL or a scheduler no longer produce unsound unreachable-file findings. Dynamic `CALL data-item`, copybook resolution and dialect-specific source formats are deliberately outside this tier and stay silent rather than guess. A 30-file COBOL repository indexed in fast mode read 1,348 symbols and resolved 86 of 88 extracted calls in 6.8 seconds.+- **A checked-in OpenAPI document is a provider schema** (#2227). Previously a provider's wire shape came only from code, so a repository could describe its API precisely in `openapi.yaml` and still produce no request or response evidence. The extractor joins the existing per-repository walk rather than adding a second one, and an operation emits the same `http::<METHOD>::<normalized-path>` identity as a framework route, so it flows through the matching, diagnostics and persistence already in place. Candidate filenames are narrow on purpose, and when exactly one code provider matches the same identity, the code-backed row keeps its file and symbol.+- **OpenAPI request and response schemas are compared directionally** (#2229). Request rules follow what a provider will accept; response rules follow what a consumer may receive; the comparison recurses through object properties and array items for type, requiredness, nullability and enum changes. Comparison runs only when both sides are complete and share an extraction source and comparison key — an incomplete extraction or a source transition produces a stated uncertainty rather than a confident claim that a field was removed.+- **Local Maven package dependencies resolve across a workspace** (#2231). A bounded, filesystem-only effective model reads local parents, reactor modules, properties, dependency management and direct dependencies, then resolves unique coordinates between repositories, carrying manifest, coordinate, version, scope and resolution evidence through the system graph, REST, MCP and the UI. No Maven subprocess, network resolution, transitive solving, BOM import or profile activation is involved; an ambiguous or invalid model is refused with a diagnostic instead of being half-resolved.+- **`index_scope`, one persisted contract for what an index actually covers** (#2246). Run mode and content provenance, the Git tier and both the configured commit cap and the coverage achieved against it, configured and effective file-page caps with eligible / generated / omitted counts, analysis that was unavailable as distinct from analysis intentionally skipped, provider and model details, full-text and semantic search availability with the exact command that restores them, and the state of any pending or resumable upgrade. CLI status, `/api/repos`, the generated AGENTS/CLAUDE guidance and MCP metadata all read that one projection. Older state degrades missing evidence to `unknown` rather than inferring completed coverage from configuration. The default commit limit is unchanged.+- **Onboarding pages are grounded in the repository's own setup evidence** (#2228). Setup guidance is drawn from contributor documents and package manifests, including working directories and exact script invocations, and concept and execution-flow selection now prefers representative lifecycle entry points and subsystem breadth over graph-central internals. Vocabulary corroboration is separated from definition quality, so incidental prose is no longer published as a definition, and generated file references are canonicalized into repository-relative links that resolve to a file page.++### Changed++- **Git history sampling is per-file and monotonic** (#2244). For every eligible rename-free file the sampler retains the newest `min(per_file_limit, available non-merge history)` commits, satisfied through three bounded lanes — the recent repository-wide window, serial deep repository-wide chunks that top up underfilled files without retaining unrelated histories, and a per-file walk only for what remains. Retained history no longer depends on which lane served a file, Git concurrency is bounded by the machine's actual resources rather than a fixed number, and the coverage a run achieved is recorded. The default commit limit is not raised and a bounded index is not reported as complete repository history.+- **Change analysis is separated from git and from transport** (#2263). Scoring composition, independent-change partitioning, review verdicts and symbol-contract classification each have one owner and can be answered without a checkout or a rendering layer; a review decision is carried as data and rendered at the edge. No current surface changes what it returns.++### Fixed++- **Stale-page recovery converges** (#2145, #2254). `update` marked file pages stale on every commit but never the module, SCC or repository-overview pages above them, so model-written summaries drifted from HEAD with `doctor`, `get_stale_pages` and `generate --stale` all reporting clean. Those dependants are now derived from the same scoped cascade during `update`, seeded so they are marked without being regenerated, which keeps sync free of model spend. A successful full generation is authoritative and retires pages outside the current selection, cleaning their vector and full-text entries; full-text cleanup debt is persisted so a failed deletion converges on retry; `doctor` now classifies who owns a stale page and names `update --full` as the reconciliation path; and a page regenerated by an update is no longer marked stale again by that same update.+- **`update` reconciles configuration changes, not just new commits** (#2235). A repository whose commit had not moved was treated as current even when indexing-relevant configuration had changed, leaving clean updates out of step with a fresh index. Configuration is now fingerprinted by the layer it affects — traversal, Git history, health, generation or state alone — and an update rebuilds that layer and its dependants while leaving the rest untouched. Unknown keys take the conservative full-invalidation path, a failed required rebuild keeps the prior fingerprint so the next run retries rather than accepting partial state, and search or vector cleanup that fails after the database transaction is recorded and retried later.+- **A failed embedding batch no longer multiplies across the corpus** (#2251). Reindex retried whole batches blindly, so a provider outage could run for an hour. Failed chunk identities and the stage they failed at are preserved; individual items are retried only for input-specific 400/413/422 failures; two consecutive provider-wide batch failures stop the run; and only a confirmed single-input token-limit failure is adaptively truncated, with a bounded retry count. A restricted-network run now stops in seconds with a clear connection error. Reindex batch size is validated and the underlying failure cause is surfaced.+- **Symbol complexity computed during health analysis is persisted** (#2236), so clean, incremental, resumed and workspace indexing converge on the same symbol IDs and the same stored complexity.+- **Workspace members register and search fans out on a shared database** (#2138, #2195). When a workspace runs against a configured database URL, per-repo indexes live in that database and no `.repowise/wiki.db` file exists — server startup and search fan-out both skipped every member on that basis, so semantic search and full-text search could not reach any non-primary repository.+- **A language query that fails to compile now warns** (#2166, #2177). Compilation failures were silent, so a whole language could quietly extract nothing. Unaffected languages continue indexing normally.+- **The zero-result search rescue stops riding on one common word** (#2092, #2214). The rescue's full-text fallback returned the first row pointing at a code page with no quality check, so a multi-token query where only one ordinary token matched produced a confident suggestion for an unrelated file. A row must now cover at least two distinct query tokens across its title, path and snippet; single-token queries still fire, since the rescue is meant to allow generic names.+- **`editor_files.<id>: false` opt-outs are honored** during `init` and `update` (#2137, #2226), `vscode_mcp: false` included. An explicit per-run override still wins over a persisted opt-out, and Codex MCP and hook registration stay independent of the `agents_md` opt-out.+- **Windows users are warned to stop running server and MCP processes before upgrading** (#2149, #2204), in both `doctor` and the shared update advisory. The note also clarifies that `Repowise: Stop Server` only stops a server the VS Code extension started.+- **Saving or deleting a provider API key no longer reports a false failure** (#2237). The endpoints answer `204 No Content` and the shared API client tried to parse every success as JSON, so a completed mutation surfaced as `Unexpected end of JSON input` and skipped its refresh.+- **DeepSeek reasoning controls match the documented contract** (#2239). `reasoning_effort` is sent at the top level rather than nested in the thinking payload, low effort no longer maps to high, reasoning support is restricted to model IDs that actually have it, and thinking is disabled for streaming chat because the conversation history cannot replay the reasoning content a later tool call would need.+- **Kimi K2 and K3 advertise the controls they have** (#2238). K2 exposes only the disable-thinking control instead of graded choices that all collapsed to the same toggle, K3 exposes and forwards its `low`, `high` and `max` effort levels, and `auto` leaves the provider default alone.+- **Generation progress cannot read above 100%** (#2176, #2224). A job reporting more completed pages than a stale total rendered `4820%`, passed an invalid value to the progress primitive and dropped `aria-valuenow`. The shared primitive now bounds every finite input; non-finite input keeps the indeterminate state.+- **A select inside a dialog opens in front of it** (#2172, #2173). Floating layers are portalled to the document body, so DOM nesting does not settle paint order and the raw z-index did — a dropdown opened behind the dialog overlay while still holding keyboard focus, so typeahead changed a value nobody could see. The `--z-*` scale is documented and guarded by an ordering test.+- **A long AI fix prompt stays inside its modal** (#2249). Unbroken paths and generated identifiers contributed their minimum content width to the dialog and could push the footer, and the Copy prompt action with it, past the right edge.++### Documentation++- The supported COBOL surface and its deferred ceilings are documented (#1770), as is the supported OpenAPI subset, its static evidence boundary and the endpoint-exposure vocabulary (#2229).++---+## [0.50.0] - 2026-09-11Code health had six different vocabularies for one number, and roughly half of what it measured was change history, which rises as a file is worked on. A week of refactoring could drop the headline and print "Declining health" in error red at the person who did the work. This release rebuilds that reading end to end: one absolute band scale wherever a score appears, one figure at the top of the page, a control that says whether you are counting code shape alone or code shape plus history, and a decline that names which half moved and whether an edit can settle it. No score moves. What changes is what the product tells you a score means. Next to it, findings stop being a list you scroll and become a queue you work, with a disposition you record once and never have re-proposed at you. The other change you will notice first is chat: it is no longer a widget in a corner, it is reachable from the row you are already looking at, pointed at that row, with its first answer grounded in the page you asked from.diff --git a/packages/server/src/repowise/server/__init__.py b/packages/server/src/repowise/server/__init__.pyindex 2a2f15153..37d09d983 100644--- a/packages/server/src/repowise/server/__init__.py+++ b/packages/server/src/repowise/server/__init__.py@@ -7,4 +7,4 @@ Provides:- Background job scheduler (APScheduler)"""-__version__ = "0.50.0"+__version__ = "0.51.0"diff --git a/packages/types/src/generated/http.ts b/packages/types/src/generated/http.tsindex d6ff499c6..cc6f347cf 100644--- a/packages/types/src/generated/http.ts+++ b/packages/types/src/generated/http.ts@@ -2568,7 +2568,9 @@ export interface TestImpactEvidence {export interface TestImpactFile {source_file: string;- status: "measured" | "inferred" | "unknown";+ status: "measured" | "inferred" | "unknown" | "deleted";+ change_status?: string | null;+ head_present?: boolean;measured_tests: string[];measured_tests_total: number;inferred_tests: string[];@@ -2601,6 +2603,7 @@ export interface TestImpactResponse {files_total: number;files_without_measured_tests: string[];unknown_files: string[];+ deleted_files?: string[];coverage: TestImpactCoverage;inference: TestImpactInference;analysis: TestImpactAnalysis;diff --git a/plugins/claude-code/.claude-plugin/plugin.json b/plugins/claude-code/.claude-plugin/plugin.jsonindex 13168f374..bd7fcab81 100644--- a/plugins/claude-code/.claude-plugin/plugin.json+++ b/plugins/claude-code/.claude-plugin/plugin.json@@ -1,7 +1,7 @@{"name": "repowise","description": "Codebase intelligence for Claude Code. Indexes your codebase into five layers (Graph, Git, Docs, Decisions, Code Health) and exposes them through ten task-shaped MCP tools — so Claude understands architecture, ownership, hotspots, why code is built the way it is, and where the defect risk lives.",- "version": "0.50.0",+ "version": "0.51.0","author": {"name": "Repowise","email": "[email protected]",diff --git a/plugins/claude-code/CHANGELOG.md b/plugins/claude-code/CHANGELOG.mdindex 96fabfc43..d399854ca 100644--- a/plugins/claude-code/CHANGELOG.md+++ b/plugins/claude-code/CHANGELOG.md@@ -2,6 +2,19 @@All notable changes to the Repowise Claude Code plugin are documented here.+## 0.51.0++### Fixed+- The `reindex` command documented `--batch-size` as defaulting to 20. The CLI+ default is 32, and the flag now rejects values below 1 rather than accepting+ them and failing later.++### Changed+- No tool-surface change this cycle: every tool named in a command or skill is+ one the server still lists, and `hooks.json` still mirrors `claude_config.py`.+ `set_finding_status` remains live and deliberately unreferenced, since it+ mutates.+## 0.50.0### Changeddiff --git a/plugins/claude-code/commands/reindex.md b/plugins/claude-code/commands/reindex.mdindex 1b93f1523..234daab4a 100644--- a/plugins/claude-code/commands/reindex.md+++ b/plugins/claude-code/commands/reindex.md@@ -23,7 +23,7 @@ This is useful when:## Available flags- `--embedder gemini|openai|openrouter|ollama|edenai|auto` — embedding provider (default: auto-detect from env vars)-- `--batch-size N` — pages per embedding batch (default: 20)+- `--batch-size N` — pages per embedding batch, must be 1 or greater (default: 32)## Requirementsdiff --git a/plugins/shared/commands/reindex.md b/plugins/shared/commands/reindex.mdindex d1304a27c..71d246bbf 100644--- a/plugins/shared/commands/reindex.md+++ b/plugins/shared/commands/reindex.md@@ -24,7 +24,7 @@ This is useful when:## Available flags- `--embedder gemini|openai|openrouter|ollama|edenai|auto` — embedding provider (default: auto-detect from env vars)-- `--batch-size N` — pages per embedding batch (default: 20)+- `--batch-size N` — pages per embedding batch, must be 1 or greater (default: 32)## Requirementsdiff --git a/pyproject.toml b/pyproject.tomlindex ccc189eb5..08a25c60f 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"[project]name = "repowise"-version = "0.50.0"+version = "0.51.0"description = "The codebase intelligence layer for your AI coding agent — dependency graph, git history, dead code, decisions, and code health, exposed over MCP"readme = "README.md"requires-python = ">=3.11"diff --git a/server.json b/server.jsonindex 1bbfa6855..878bb7713 100644--- a/server.json+++ b/server.json@@ -8,12 +8,12 @@"source": "github"},"websiteUrl": "https://www.repowise.dev",- "version": "0.50.0",+ "version": "0.51.0","packages": [{"registryType": "pypi","identifier": "repowise",- "version": "0.50.0",+ "version": "0.51.0","transport": {"type": "stdio"},diff --git a/uv.lock b/uv.lockindex 001da6544..f43b5ccf6 100644--- a/uv.lock+++ b/uv.lock@@ -3051,7 +3051,7 @@ wheels = [[[package]]name = "repowise"-version = "0.50.0"+version = "0.51.0"source = { editable = "." }dependencies = [{ name = "aiosqlite" },