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.54.0 (#2720)
Raghav Chamadiyaeaf9fb2638af
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex 642de15ad..3182c2a44 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.53.0",+ "version": "0.54.0","category": "productivity","keywords": ["codebase",diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.mdindex 66b25a262..1ddcedc9a 100644--- a/docs/CHANGELOG.md+++ b/docs/CHANGELOG.md@@ -9,6 +9,83 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0---+## [0.54.0] - 2026-09-30++Most of this release is about getting the facts right. Tests showed up as entry points, a package's real CLI did not, a file renamed last month started its history from zero, one person counted as three contributors, and dead-code reports flagged config files that a tool loads by name. Each of those came from a rule that guessed where it could have read the answer from the repository itself: the manifest, git's rename records, the symbol table. This release reads it.++It also brings coverage into CI. `repowise coverage check` gates a change on its patch coverage with no index and no API key, `repowise impacted-tests` picks the tests a change needs and runs everything whenever that is not certain, and one GitHub Action or GitLab template runs the coverage, documentation drift and security gates together.++### Added++- **Patch coverage gates a change in CI** (#2630, #2634, #2644, #2649, #2664). `repowise coverage check [REVSPEC]` reports the share of a change's executable lines the tests ran and fails below `--fail-under` (or `coverage.fail_under`). It needs git and a coverage report only. Report paths accept globs and per-report prefixes, `coverage.ignore` drops generated or vendored files, and a change with too few measured lines is reported rather than failed. `coverage.gates` sets per-area thresholds, and `repowise coverage suggest-gates` proposes areas from owners, layout and the graph. Branches on changed lines are reported beside patch coverage, never blended into it, with an optional branch gate.+- **Coverage compared with the base, and a coverage trend** (#2659, #2642, #2636). `--base-report` or the coverage ingested at the base commit gives the project delta, and `--max-drop` fails a change that lowers it. Each ingest is recorded with its freshness and how its paths matched, and the last 50 ingests form a history shown as a trend in the dashboard and in `get_health`.+- **Each uncovered change names the test to extend** (#2650, #2645). Uncovered ranges carry the innermost symbol around them and up to three tests to extend, and each carries its file's risk, so attention rows sort by it. `get_change_risk` with no revspec covers everything a push would bring, uncommitted files included.+- **An opt-in coverage re-ingest for agents** (#2658). With `hooks.coverage_reingest: true`, a test run inside Claude Code, passing or failing, refreshes the stored coverage through a repository-local hook. `coverage add` accepts globs.+- **Risk as a CI gate** (#2645). `repowise risk --fail-above-percentile P` fails a change ranked above the P-th percentile of the repository's own history, never on the 0 to 10 score.+- **Run only the tests a change needs, safely** (#2665). `repowise impacted-tests --format args` prints runner-ready arguments (pytest node ids, Go packages, Jest or Vitest paths) or `:all`, with every reason on stderr. Anything not positively known runs the whole suite: lockfiles, build and CI config, test data and helpers no test imports, changed files no test reaches, an index built at neither end of the change, or a failed graph read. `conftest.py` selects the tests under its directory, imported helpers select their importers, a document that code or a doctest config reads runs everything, and tests the graph cannot see into run with every subset. `tests.full_run_on` and `tests.always_run` extend the rules, and the GitHub Action and GitLab template expose the selection so a missing or failed one runs everything.+- **One GitHub Action and one GitLab template for all three gates** (#2641, #2643). They run the coverage, documentation drift and security gates in one step, keep going when one fails, and can upload SARIF. `repowise doc-drift` and `repowise security check` also write a GitLab Code Quality report with `--format gitlab`. A new CI guide documents all three.+- **Documentation drift catches renamed and deleted symbols** (#2661, #2631, #2640, #2646, #2647). A backticked identifier that was a real definition when the doc line was written, and that nothing names at HEAD, is a finding, with the rename as the suggested fix when one is clear. Findings suggest a replacement wherever the tree says where a reference went, the CI gate keeps only the drift a change is answerable for (`--since REVSPEC|auto`), findings are grouped by document and marked new since the last update, and drift is recorded in health history. The VS Code extension shows drift in the Problems panel for Markdown files (#2648).+- **Security gate for CI and pre-commit** (#2635, #2657). `repowise security check` fails a change on the findings it adds. A `repowise-security-ignore` marker silences a line, `security.patterns` adds your own named patterns, and `repowise hook install --security` adds an opt-in pre-commit check.+- **"Do next" leads the Overview** (#2651). A short list of actions built from what the index already stores (health, fix history, performance, security, doc drift, dead code, decisions, coverage), each with its reason, effort and what done looks like, and a `repowise next` command. Dismiss, snooze and done are remembered.+- **`get_why` answers from code comments and history when no decision matches** (#2692). A question that matches no decision record now gets the rationale comments or commit subjects that state the reason, labelled as such and never presented as decisions.+- **Decisions whose commits were reverted are retired, and decisions whose files are all gone read as stale** (#2675, #2694). A revert is matched from git's own records, and a restored file clears the stale mark on the next run.+- **Commit history for non-code files** (#2690). Docs, config, workflows and data files now carry commit counts, windows and authors instead of an unknown count. They stay out of hotspot and percentile rankings, and an existing index gains them on its first update (#2719).++### Changed++- **Entry points come from the manifest first** (#2698, #2704). `package.json` `bin`, `main`, `module` and `exports["."]` (with a built `dist` path mapped back to its source when the build is not checked in), `[project.scripts]` and each distribution's package `__init__.py` rank ahead of every filename guess. Test files no longer have to claim to be entry points to be exempt from dead code: a separate reachability flag carries that exemption.+- **Author identities are merged with guardrails** (#2684). One person's GitHub noreply addresses, handle and machine-local email are joined into one contributor, and bots are left out of people counts. Two real email addresses are never joined on a shared display name alone, so someone who commits from two personal addresses still counts twice. Owners, the truck factor and the contributor count all read the merged identity.+- **"Commits" means non-merge commits everywhere** (#2683). Repository totals, per-file counts and the stats sample all count the same way, merges are counted separately, and a complete history no longer reads as truncated.+- **A file keeps its history across renames** (#2569, #2690). Churn, age, authorship, co-change partners and prior-defect counts follow the file to its new path, and rename detection is explicit.+- **History windows are measured from the indexed commit** (#2568), so re-indexing an unchanged tree on a later day gives the same scores. `REPOWISE_GIT_WINDOW_ANCHOR=now` restores the wall-clock behaviour.+- **Git history weighs less on a file with no code problems** (#2566). A file with no code finding loses at most one point to git history, and the score breakdown shows the cap each file was scored under.+- **`hidden_coupling` is advisory** (#2596). It is still detected and listed but no longer lowers the score; on its own it ranked defect-prone files near chance.+- **Search ranks same-named symbols by one key, and a name that does not exist returns no symbol** (#2701, #2691). Exact case, then kind (class before function before variable), then code before tests and docs. A code-shaped query such as `AuthServiceXyz` no longer returns its fuzzy neighbour as if it were the match, and question parsing recognises lowerCamel and acronym names by checking them against the symbol table.+- **The C4 views show the system you run** (#2699, #2697, #2678). System Context lists runtime services rather than every library and the repository's own packages, test and example projects are no longer containers, a container is named by its manifest and labelled by its code language, and a container's own components stay in its component view.+- **Stats and the overview agree** (#2710). One rule for the language split (code languages, with docs and config listed apart) and one module count on every surface.+- **Package pages and a computed Public API** (#2712). A package whose files span several concept groups always gets its own page. What a package publishes is read from its manifest entries or its barrel, following re-exports, aliases and `__all__`, and listed in its page prompt, so a class consumers import but nothing inside the repository does is no longer left out.+- **Module pages see the code they describe** (#2713). Module page prompts carry the Public API, signatures and capped bodies of each file's public or documented symbols within a fixed token budget, and the model is told to state behaviour only when an excerpt shows it.+- **Wiki pages stick to the subject** (#2681, #2702, #2705, #2709, #2711). Template pages are written only for real API contracts and never for tests, package roots bound concept groups, the overview drops capabilities the repository never defines, a UI layer needs UI files, the module prompt no longer invites the model to discuss dead code, page footers say what a page was generated from, and a template page names no model.+- **Findings shown on each surface come from one registry** (#2687). Every surface that lists dead-code or health findings reads the same record of which finding types are shown, so a withheld type never appears in one list and not another.+- **`HEALTH_ANALYZER_VERSION` moved from 31 to 36** across the health and git changes above, so existing indexes re-score on their next update. **`PARSER_SCHEMA_VERSION` moved from 3 to 5** (Python import resolution and overload declarations), so the parse cache refreshes automatically. `STORE_FORMAT_VERSION` is unchanged and nothing needs re-indexing.++### Fixed++- **Python imports resolve by their full dotted path** (#2674, #2612). `from pydantic import X` can no longer land on a repository's own `utils/pydantic.py`, `import typing` inside a package no longer resolves to a sibling `typing.py`, and qualified names use the importable module. A bare import inside a package still finds a module that sits beside the package's top level, as `from adafruit_ticks import ...` does in a CircuitPython library (#2717).+- **Calls on a chained field receiver resolve** (#2703). `this.store.users.find()` and `self.store.users.find()` now reach the method they call.+- **Overload stubs are declarations** (#2696). Python `@overload` stubs and TypeScript overload signatures no longer stand in for the implementation in lookups.+- **TypeScript methods keep their parameters** (#2680). Methods with an access modifier were recorded with a bare-name signature, and module-level regex and ternary constants are now symbols.+- **No file self-loops, and tests no longer dominate PageRank** (#2677, #2695). A `package.json` that exports itself no longer points at itself, and test-to-test edges are left out of PageRank and betweenness, so `conftest.py` is no longer a repository's most central file.+- **Workspace packages are found at any depth and checked against the declared members** (#2685), and a workspace export that names build output absent from the checkout binds to its source file (#2706).+- **Dead code stops flagging files something loads by name** (#2700, #2707, #2673). Any tool's `*.config.*` file, `.<tool>rc` files, `.pnpmfile.cjs` and `sitecustomize.py` are exempt. Files shaped like path-loaded entries (a lone default export, a script with a main block) are capped to the review tier. Internals used elsewhere in their own file, files named by path, and functions registered on a receiver are no longer reported.+- **Dead-code line counts are measured, not estimated** (#2682), and a whole unreachable file stays in the review tier (#2716).+- **Full-text search covers each page's file vocabulary** (#2718), so keyword searches on an index built without a model match the terms a file defines. Existing indexes are widened and refilled when they are next opened.+- **Health false positives** (#2693, #2688, #2679, #2574, #2573). Clone pairs are verified on identifiers, so import blocks and same-shaped data tables no longer read as duplication. An untested hotspot pairs with tests that import it directly or through a barrel, and a file with nothing to test is skipped. SDK `execute` calls and re-raising exception handlers no longer raise findings. A file's dependents are counted from code edges, not co-change history, and a chain through a re-export barrel counts as a dependency.+- **The update's full re-score keeps history markers** (#2614), and displayed scores are floored so a figure never rounds into the next band (#2587).+- **Test detection by whole words** (#2676). `e2e-tests/` and `pkg_tests/` are test trees, `latest-release/` and `contest_results/` are not, and filename rules such as `.test.` apply to source files only, so `tsconfig.test.json` is config.+- **Hand-written files that mention code generation are kept** (#2689). A generated-file marker must be in a comment or docstring opener, and tracked files under ignored paths are indexed.+- **Refactoring plans are more accurate** (#2570, #2571, #2572). `extract_method` is credited only with the impact its span recovers, each step carries only the findings it answers, and `move_method` no longer targets result types or base classes.+- **Security scanning reports credentials, not examples of them** (#2660, #2618). Keyword secrets in comments, docstrings and doctests are examples, and call-kind findings ignore comments, strings and prose files.+- **Windows: no console window flashes** when the telemetry flusher or another detached child starts, for example during VS Code index updates (#2380).+- **`repowise update --full` finishes when a few pages fail** and points to `repowise generate` to refill them, and Ollama prompts are no longer truncated (#2564). The cascade-budget warning separates model and structural pages (#2616), and `repowise generate` accounts for every planned page and prints the actual cost (#2615).+- **Decisions**: the id migration no longer copies a record onto an occupied id, which failed persistence on every update (#2613); conventional ADR directories stay ahead of loose name matches (#2586); both commit miners read significant-commit metadata the same way (#2605); and archaeology cross-references match whole tokens (#2588).+- `get_answer` reads "the evidence does not identify" as a hedge and lowers its confidence (#2708). `get_change_risk` no longer fails when the index has no repository row (#2553), `get_symbol` checks for a repository path first (#2554), and `get_health`'s targeted mode keeps its reads inside its session (#2670).+- `repowise init` edits only the repowise entry in `.mcp.json`, leaving other servers byte-identical (#1836). A malformed manifest no longer crashes the tech-stack scan (#2608), and a corrupt omission store closes its connection (#2555).+- Anthropic cached input tokens are counted (#2433), `.env` and other config dotfiles are classified as config (#2381, #2516), non-executable post-commit hooks are reported (#2476), the hook filters workspace targets and reports failures (#2478), coverage-gap uncovered lines come from the percentage (#2259), and Codex session tool calls are attributed to the assistant (#2652).+- Web UI: commit filters stay visible on empty results (#2487), the repo avatar no longer shows twice on phones (#2583), graph narrowing handles communities outside the top 20 (#2656), and `text-xs` / `text-sm` sit on the type ladder (#2619).++### Documentation++- A CI guide covers the coverage, documentation drift and security gates and test selection in one place (#2641, #2665).+- Dead-code docs list every unused-export edge type and the dynamic-import language coverage (#2477, #2629), graph benchmark figures match BENCHMARKS.md (#2628), a stale edge-type reference is fixed (#2536), and `get_overview`'s ownership block is described as it is returned (#2610).+- Plugin: the `coverage` command documents the new gate options.++### Internal++- Many long functions across the server, core and CLI were split into named steps with unchanged output (get_health, get_why, get_risk, get_overview, the call resolver, the parser, the decision miners, the job executor and others).++---+## [0.53.0] - 2026-09-24A workspace is only as useful as the contracts it can read, and outside Python and TypeScript servers it read most stacks one call at a time. A Laravel route inside `Route::prefix('v1')->group(...)` lost its prefix, `routes/api.php` lost its `/api`, and `apiResource` produced nothing. A NestJS controller produced no routes. An Angular service calling `HttpClient` on an injected receiver, or an axios instance created in one file and called from another, produced no calls. Queues, pub/sub and sockets linked only when both ends spelled the same literal name. This release reads those stacks the way their frameworks serve them, and the workspace pages that show the result were rebuilt around drawers, so a contract, a relationship between services or a co-changing file pair opens in place with the evidence behind it.diff --git a/packages/cli/src/repowise/cli/__init__.py b/packages/cli/src/repowise/cli/__init__.pyindex 327fa563b..c94a5e67a 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.53.0"+__version__ = "0.54.0"diff --git a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.mdindex 0810a1732..92f5f9d66 100644--- a/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md+++ b/packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-impacted-tests.md@@ -25,6 +25,9 @@ an index lookup. Useful as a pre-merge / CI gate ("run these 40, not all 4,000")Useful flags:- `--format list` — test ids one per line (pipe to `xargs pytest`)- `--format json` — full report+- `--format args` — one line of runner arguments, or `:all` when the whole suite+ must run; reasons go to stderr. `--runner pytest|go|jest|files|auto` picks the+ argument shape- `--path <dir>` — point at a different repo```@@ -44,5 +47,8 @@ repowise impacted-tests main..HEAD --format list | xargs pytestguess). Report them as candidates. Only `via: coverage` proves a testexecuted the change.- A file none of those can speak to is "unknown, run the full suite".+- In CI, `--format args` prints `:all` whenever the selection is not certain+ (lockfiles, build or CI config, a changed file no test reaches, an index built+ at neither end of the change). Run everything when you see it.- For a whole-change repo-relative review priority, use `/prompts:repowise-risk`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.diff --git a/packages/core/src/repowise/core/__init__.py b/packages/core/src/repowise/core/__init__.pyindex 14584f796..a1a05bdda 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.53.0"+__version__ = "0.54.0"diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.mdindex 66b25a262..1ddcedc9a 100644--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md@@ -9,6 +9,83 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0---+## [0.54.0] - 2026-09-30++Most of this release is about getting the facts right. Tests showed up as entry points, a package's real CLI did not, a file renamed last month started its history from zero, one person counted as three contributors, and dead-code reports flagged config files that a tool loads by name. Each of those came from a rule that guessed where it could have read the answer from the repository itself: the manifest, git's rename records, the symbol table. This release reads it.++It also brings coverage into CI. `repowise coverage check` gates a change on its patch coverage with no index and no API key, `repowise impacted-tests` picks the tests a change needs and runs everything whenever that is not certain, and one GitHub Action or GitLab template runs the coverage, documentation drift and security gates together.++### Added++- **Patch coverage gates a change in CI** (#2630, #2634, #2644, #2649, #2664). `repowise coverage check [REVSPEC]` reports the share of a change's executable lines the tests ran and fails below `--fail-under` (or `coverage.fail_under`). It needs git and a coverage report only. Report paths accept globs and per-report prefixes, `coverage.ignore` drops generated or vendored files, and a change with too few measured lines is reported rather than failed. `coverage.gates` sets per-area thresholds, and `repowise coverage suggest-gates` proposes areas from owners, layout and the graph. Branches on changed lines are reported beside patch coverage, never blended into it, with an optional branch gate.+- **Coverage compared with the base, and a coverage trend** (#2659, #2642, #2636). `--base-report` or the coverage ingested at the base commit gives the project delta, and `--max-drop` fails a change that lowers it. Each ingest is recorded with its freshness and how its paths matched, and the last 50 ingests form a history shown as a trend in the dashboard and in `get_health`.+- **Each uncovered change names the test to extend** (#2650, #2645). Uncovered ranges carry the innermost symbol around them and up to three tests to extend, and each carries its file's risk, so attention rows sort by it. `get_change_risk` with no revspec covers everything a push would bring, uncommitted files included.+- **An opt-in coverage re-ingest for agents** (#2658). With `hooks.coverage_reingest: true`, a test run inside Claude Code, passing or failing, refreshes the stored coverage through a repository-local hook. `coverage add` accepts globs.+- **Risk as a CI gate** (#2645). `repowise risk --fail-above-percentile P` fails a change ranked above the P-th percentile of the repository's own history, never on the 0 to 10 score.+- **Run only the tests a change needs, safely** (#2665). `repowise impacted-tests --format args` prints runner-ready arguments (pytest node ids, Go packages, Jest or Vitest paths) or `:all`, with every reason on stderr. Anything not positively known runs the whole suite: lockfiles, build and CI config, test data and helpers no test imports, changed files no test reaches, an index built at neither end of the change, or a failed graph read. `conftest.py` selects the tests under its directory, imported helpers select their importers, a document that code or a doctest config reads runs everything, and tests the graph cannot see into run with every subset. `tests.full_run_on` and `tests.always_run` extend the rules, and the GitHub Action and GitLab template expose the selection so a missing or failed one runs everything.+- **One GitHub Action and one GitLab template for all three gates** (#2641, #2643). They run the coverage, documentation drift and security gates in one step, keep going when one fails, and can upload SARIF. `repowise doc-drift` and `repowise security check` also write a GitLab Code Quality report with `--format gitlab`. A new CI guide documents all three.+- **Documentation drift catches renamed and deleted symbols** (#2661, #2631, #2640, #2646, #2647). A backticked identifier that was a real definition when the doc line was written, and that nothing names at HEAD, is a finding, with the rename as the suggested fix when one is clear. Findings suggest a replacement wherever the tree says where a reference went, the CI gate keeps only the drift a change is answerable for (`--since REVSPEC|auto`), findings are grouped by document and marked new since the last update, and drift is recorded in health history. The VS Code extension shows drift in the Problems panel for Markdown files (#2648).+- **Security gate for CI and pre-commit** (#2635, #2657). `repowise security check` fails a change on the findings it adds. A `repowise-security-ignore` marker silences a line, `security.patterns` adds your own named patterns, and `repowise hook install --security` adds an opt-in pre-commit check.+- **"Do next" leads the Overview** (#2651). A short list of actions built from what the index already stores (health, fix history, performance, security, doc drift, dead code, decisions, coverage), each with its reason, effort and what done looks like, and a `repowise next` command. Dismiss, snooze and done are remembered.+- **`get_why` answers from code comments and history when no decision matches** (#2692). A question that matches no decision record now gets the rationale comments or commit subjects that state the reason, labelled as such and never presented as decisions.+- **Decisions whose commits were reverted are retired, and decisions whose files are all gone read as stale** (#2675, #2694). A revert is matched from git's own records, and a restored file clears the stale mark on the next run.+- **Commit history for non-code files** (#2690). Docs, config, workflows and data files now carry commit counts, windows and authors instead of an unknown count. They stay out of hotspot and percentile rankings, and an existing index gains them on its first update (#2719).++### Changed++- **Entry points come from the manifest first** (#2698, #2704). `package.json` `bin`, `main`, `module` and `exports["."]` (with a built `dist` path mapped back to its source when the build is not checked in), `[project.scripts]` and each distribution's package `__init__.py` rank ahead of every filename guess. Test files no longer have to claim to be entry points to be exempt from dead code: a separate reachability flag carries that exemption.+- **Author identities are merged with guardrails** (#2684). One person's GitHub noreply addresses, handle and machine-local email are joined into one contributor, and bots are left out of people counts. Two real email addresses are never joined on a shared display name alone, so someone who commits from two personal addresses still counts twice. Owners, the truck factor and the contributor count all read the merged identity.+- **"Commits" means non-merge commits everywhere** (#2683). Repository totals, per-file counts and the stats sample all count the same way, merges are counted separately, and a complete history no longer reads as truncated.+- **A file keeps its history across renames** (#2569, #2690). Churn, age, authorship, co-change partners and prior-defect counts follow the file to its new path, and rename detection is explicit.+- **History windows are measured from the indexed commit** (#2568), so re-indexing an unchanged tree on a later day gives the same scores. `REPOWISE_GIT_WINDOW_ANCHOR=now` restores the wall-clock behaviour.+- **Git history weighs less on a file with no code problems** (#2566). A file with no code finding loses at most one point to git history, and the score breakdown shows the cap each file was scored under.+- **`hidden_coupling` is advisory** (#2596). It is still detected and listed but no longer lowers the score; on its own it ranked defect-prone files near chance.+- **Search ranks same-named symbols by one key, and a name that does not exist returns no symbol** (#2701, #2691). Exact case, then kind (class before function before variable), then code before tests and docs. A code-shaped query such as `AuthServiceXyz` no longer returns its fuzzy neighbour as if it were the match, and question parsing recognises lowerCamel and acronym names by checking them against the symbol table.+- **The C4 views show the system you run** (#2699, #2697, #2678). System Context lists runtime services rather than every library and the repository's own packages, test and example projects are no longer containers, a container is named by its manifest and labelled by its code language, and a container's own components stay in its component view.+- **Stats and the overview agree** (#2710). One rule for the language split (code languages, with docs and config listed apart) and one module count on every surface.+- **Package pages and a computed Public API** (#2712). A package whose files span several concept groups always gets its own page. What a package publishes is read from its manifest entries or its barrel, following re-exports, aliases and `__all__`, and listed in its page prompt, so a class consumers import but nothing inside the repository does is no longer left out.+- **Module pages see the code they describe** (#2713). Module page prompts carry the Public API, signatures and capped bodies of each file's public or documented symbols within a fixed token budget, and the model is told to state behaviour only when an excerpt shows it.+- **Wiki pages stick to the subject** (#2681, #2702, #2705, #2709, #2711). Template pages are written only for real API contracts and never for tests, package roots bound concept groups, the overview drops capabilities the repository never defines, a UI layer needs UI files, the module prompt no longer invites the model to discuss dead code, page footers say what a page was generated from, and a template page names no model.+- **Findings shown on each surface come from one registry** (#2687). Every surface that lists dead-code or health findings reads the same record of which finding types are shown, so a withheld type never appears in one list and not another.+- **`HEALTH_ANALYZER_VERSION` moved from 31 to 36** across the health and git changes above, so existing indexes re-score on their next update. **`PARSER_SCHEMA_VERSION` moved from 3 to 5** (Python import resolution and overload declarations), so the parse cache refreshes automatically. `STORE_FORMAT_VERSION` is unchanged and nothing needs re-indexing.++### Fixed++- **Python imports resolve by their full dotted path** (#2674, #2612). `from pydantic import X` can no longer land on a repository's own `utils/pydantic.py`, `import typing` inside a package no longer resolves to a sibling `typing.py`, and qualified names use the importable module. A bare import inside a package still finds a module that sits beside the package's top level, as `from adafruit_ticks import ...` does in a CircuitPython library (#2717).+- **Calls on a chained field receiver resolve** (#2703). `this.store.users.find()` and `self.store.users.find()` now reach the method they call.+- **Overload stubs are declarations** (#2696). Python `@overload` stubs and TypeScript overload signatures no longer stand in for the implementation in lookups.+- **TypeScript methods keep their parameters** (#2680). Methods with an access modifier were recorded with a bare-name signature, and module-level regex and ternary constants are now symbols.+- **No file self-loops, and tests no longer dominate PageRank** (#2677, #2695). A `package.json` that exports itself no longer points at itself, and test-to-test edges are left out of PageRank and betweenness, so `conftest.py` is no longer a repository's most central file.+- **Workspace packages are found at any depth and checked against the declared members** (#2685), and a workspace export that names build output absent from the checkout binds to its source file (#2706).+- **Dead code stops flagging files something loads by name** (#2700, #2707, #2673). Any tool's `*.config.*` file, `.<tool>rc` files, `.pnpmfile.cjs` and `sitecustomize.py` are exempt. Files shaped like path-loaded entries (a lone default export, a script with a main block) are capped to the review tier. Internals used elsewhere in their own file, files named by path, and functions registered on a receiver are no longer reported.+- **Dead-code line counts are measured, not estimated** (#2682), and a whole unreachable file stays in the review tier (#2716).+- **Full-text search covers each page's file vocabulary** (#2718), so keyword searches on an index built without a model match the terms a file defines. Existing indexes are widened and refilled when they are next opened.+- **Health false positives** (#2693, #2688, #2679, #2574, #2573). Clone pairs are verified on identifiers, so import blocks and same-shaped data tables no longer read as duplication. An untested hotspot pairs with tests that import it directly or through a barrel, and a file with nothing to test is skipped. SDK `execute` calls and re-raising exception handlers no longer raise findings. A file's dependents are counted from code edges, not co-change history, and a chain through a re-export barrel counts as a dependency.+- **The update's full re-score keeps history markers** (#2614), and displayed scores are floored so a figure never rounds into the next band (#2587).+- **Test detection by whole words** (#2676). `e2e-tests/` and `pkg_tests/` are test trees, `latest-release/` and `contest_results/` are not, and filename rules such as `.test.` apply to source files only, so `tsconfig.test.json` is config.+- **Hand-written files that mention code generation are kept** (#2689). A generated-file marker must be in a comment or docstring opener, and tracked files under ignored paths are indexed.+- **Refactoring plans are more accurate** (#2570, #2571, #2572). `extract_method` is credited only with the impact its span recovers, each step carries only the findings it answers, and `move_method` no longer targets result types or base classes.+- **Security scanning reports credentials, not examples of them** (#2660, #2618). Keyword secrets in comments, docstrings and doctests are examples, and call-kind findings ignore comments, strings and prose files.+- **Windows: no console window flashes** when the telemetry flusher or another detached child starts, for example during VS Code index updates (#2380).+- **`repowise update --full` finishes when a few pages fail** and points to `repowise generate` to refill them, and Ollama prompts are no longer truncated (#2564). The cascade-budget warning separates model and structural pages (#2616), and `repowise generate` accounts for every planned page and prints the actual cost (#2615).+- **Decisions**: the id migration no longer copies a record onto an occupied id, which failed persistence on every update (#2613); conventional ADR directories stay ahead of loose name matches (#2586); both commit miners read significant-commit metadata the same way (#2605); and archaeology cross-references match whole tokens (#2588).+- `get_answer` reads "the evidence does not identify" as a hedge and lowers its confidence (#2708). `get_change_risk` no longer fails when the index has no repository row (#2553), `get_symbol` checks for a repository path first (#2554), and `get_health`'s targeted mode keeps its reads inside its session (#2670).+- `repowise init` edits only the repowise entry in `.mcp.json`, leaving other servers byte-identical (#1836). A malformed manifest no longer crashes the tech-stack scan (#2608), and a corrupt omission store closes its connection (#2555).+- Anthropic cached input tokens are counted (#2433), `.env` and other config dotfiles are classified as config (#2381, #2516), non-executable post-commit hooks are reported (#2476), the hook filters workspace targets and reports failures (#2478), coverage-gap uncovered lines come from the percentage (#2259), and Codex session tool calls are attributed to the assistant (#2652).+- Web UI: commit filters stay visible on empty results (#2487), the repo avatar no longer shows twice on phones (#2583), graph narrowing handles communities outside the top 20 (#2656), and `text-xs` / `text-sm` sit on the type ladder (#2619).++### Documentation++- A CI guide covers the coverage, documentation drift and security gates and test selection in one place (#2641, #2665).+- Dead-code docs list every unused-export edge type and the dynamic-import language coverage (#2477, #2629), graph benchmark figures match BENCHMARKS.md (#2628), a stale edge-type reference is fixed (#2536), and `get_overview`'s ownership block is described as it is returned (#2610).+- Plugin: the `coverage` command documents the new gate options.++### Internal++- Many long functions across the server, core and CLI were split into named steps with unchanged output (get_health, get_why, get_risk, get_overview, the call resolver, the parser, the decision miners, the job executor and others).++---+## [0.53.0] - 2026-09-24A workspace is only as useful as the contracts it can read, and outside Python and TypeScript servers it read most stacks one call at a time. A Laravel route inside `Route::prefix('v1')->group(...)` lost its prefix, `routes/api.php` lost its `/api`, and `apiResource` produced nothing. A NestJS controller produced no routes. An Angular service calling `HttpClient` on an injected receiver, or an axios instance created in one file and called from another, produced no calls. Queues, pub/sub and sockets linked only when both ends spelled the same literal name. This release reads those stacks the way their frameworks serve them, and the workspace pages that show the result were rebuilt around drawers, so a contract, a relationship between services or a co-changing file pair opens in place with the evidence behind it.diff --git a/packages/server/src/repowise/server/__init__.py b/packages/server/src/repowise/server/__init__.pyindex 1daf366ad..07ed48e1a 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.53.0"+__version__ = "0.54.0"diff --git a/plugins/claude-code/.claude-plugin/plugin.json b/plugins/claude-code/.claude-plugin/plugin.jsonindex a74273699..d5de7f516 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.53.0",+ "version": "0.54.0","author": {"name": "Repowise","email": "[email protected]",diff --git a/plugins/claude-code/CHANGELOG.md b/plugins/claude-code/CHANGELOG.mdindex c4b10c106..b6c243b47 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.54.0++### Changed+- The `coverage` command documents gating a change in CI with+ `repowise coverage check`: the report, threshold and output-format options,+ and the report formats the parser reads (Go cover profiles, JaCoCo and+ repowise JSON joined LCOV, Cobertura, Clover and coverage.py).+- The `impacted-tests` command documents `--format args` and `--runner`, and+ that the selection answers `:all` whenever it is not certain.+- No MCP tool was added, removed or renamed, and `hooks.json` still mirrors the+ global augment matcher. The new coverage re-ingest hook is opt-in and+ repository-local, written by the CLI, so the plugin does not ship it.+## 0.53.0### Changeddiff --git a/plugins/claude-code/commands/impacted-tests.md b/plugins/claude-code/commands/impacted-tests.mdindex df16255a6..c92b7c67e 100644--- a/plugins/claude-code/commands/impacted-tests.md+++ b/plugins/claude-code/commands/impacted-tests.md@@ -26,6 +26,9 @@ an index lookup. Useful as a pre-merge / CI gate ("run these 40, not all 4,000")Useful flags:- `--format list` — test ids one per line (pipe to `xargs pytest`)- `--format json` — full report+- `--format args` — one line of runner arguments, or `:all` when the whole suite+ must run; reasons go to stderr. `--runner pytest|go|jest|files|auto` picks the+ argument shape- `--path <dir>` — point at a different repo```@@ -45,5 +48,8 @@ repowise impacted-tests main..HEAD --format list | xargs pytestguess). Report them as candidates. Only `via: coverage` proves a testexecuted the change.- A file none of those can speak to is "unknown, run the full suite".+- In CI, `--format args` prints `:all` whenever the selection is not certain+ (lockfiles, build or CI config, a changed file no test reaches, an index built+ at neither end of the change). Run everything when you see it.- For a whole-change repo-relative review priority, use `/repowise:risk`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.diff --git a/plugins/shared/commands/impacted-tests.md b/plugins/shared/commands/impacted-tests.mdindex b5c576dcf..27d2bdf2a 100644--- a/plugins/shared/commands/impacted-tests.md+++ b/plugins/shared/commands/impacted-tests.md@@ -27,6 +27,9 @@ an index lookup. Useful as a pre-merge / CI gate ("run these 40, not all 4,000")Useful flags:- `--format list` — test ids one per line (pipe to `xargs pytest`)- `--format json` — full report+- `--format args` — one line of runner arguments, or `:all` when the whole suite+ must run; reasons go to stderr. `--runner pytest|go|jest|files|auto` picks the+ argument shape- `--path <dir>` — point at a different repo```@@ -46,5 +49,8 @@ repowise impacted-tests main..HEAD --format list | xargs pytestguess). Report them as candidates. Only `via: coverage` proves a testexecuted the change.- A file none of those can speak to is "unknown, run the full suite".+- In CI, `--format args` prints `:all` whenever the selection is not certain+ (lockfiles, build or CI config, a changed file no test reaches, an index built+ at neither end of the change). Run everything when you see it.- For a whole-change repo-relative review priority, use `{{cmd:risk}}`. For per-fileblast radius / `tests_to_run`, use the `get_risk` MCP tool.diff --git a/pyproject.toml b/pyproject.tomlindex bd42dff70..d27e19b9e 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"[project]name = "repowise"-version = "0.53.0"+version = "0.54.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 602f7ca33..b20425e13 100644--- a/server.json+++ b/server.json@@ -8,12 +8,12 @@"source": "github"},"websiteUrl": "https://www.repowise.dev",- "version": "0.53.0",+ "version": "0.54.0","packages": [{"registryType": "pypi","identifier": "repowise",- "version": "0.53.0",+ "version": "0.54.0","transport": {"type": "stdio"},diff --git a/uv.lock b/uv.lockindex e4c6eb636..a9c1e840b 100644--- a/uv.lock+++ b/uv.lock@@ -3051,7 +3051,7 @@ wheels = [[[package]]name = "repowise"-version = "0.53.0"+version = "0.54.0"source = { editable = "." }dependencies = [{ name = "aiosqlite" },