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.53.0 (#2533)
Raghav Chamadiya669917156d2c
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex 6f3b3d8de..642de15ad 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.52.0",+ "version": "0.53.0","category": "productivity","keywords": ["codebase",diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.mdindex 0e62eecba..66b25a262 100644--- a/docs/CHANGELOG.md+++ b/docs/CHANGELOG.md@@ -9,14 +9,58 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0----## [Unreleased]+## [0.53.0] - 2026-09-24++A 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.++Performance plans said more than their evidence supported. A plan now claims `proven` only when the loop itself shows that the rewrite returns what the loop returned. Repetition with nothing to change, such as N reads of N files, leaves the default queue. Two new detectors cover shapes with no call in the loop body for the old ones to see: an ORM relationship lazily loaded once per row, and an unbounded read deduplicated in memory.++PHP gets a graph that reads it correctly. Grouped `use` imports were dropped, same-namespace references had no edge, and PHP framework conventions lived nowhere, so a Laravel app's route files, providers and base controller read as dead code. On laravel/framework, dead-code rows drop from 680 to 392. The Architecture page opens on a Files view that bundles the links between communities, and security finding snippets stop storing credential values in plain text.++### Added++- **Laravel is read the way the framework serves it** (#2512). Route chains and nested closure groups keep their prefixes, `resource` / `apiResource` expand (honouring `only`, `except` and `shallow`), and `routes/api.php` is served under `/api` unless `withRouting(apiPrefix:)` or a route provider says otherwise. A prefix that cannot be read, or two declarations that disagree, refuse the route instead of guessing. Listeners, policies, commands, middleware aliases and scheduled jobs get edges from the file that registers them, so an unregistered listener reads as unused. Eloquent models and `Schema::create` migrations become data contracts. On a five-service TypeScript and Laravel workspace, all 39 cross-service HTTP links now match exactly, against 7 before.+- **NestJS routes, Node HTTP clients and Node ORM tables** (#2527). NestJS controllers are served under the global prefix, URI version and controller prefix, read from wherever the bootstrap settings are declared, per app in a monorepo. axios, ky, got and ofetch calls are read directly or through an instance created with `baseURL` / `prefixUrl`, and an exported instance is followed into the files that import it. Tables are read from Prisma, TypeORM, Sequelize, Drizzle and Knex.+- **Angular `HttpClient` calls and Angular entry points** (#2531). Calls on a receiver typed or injected as `HttpClient` are read for every verb, with the base folded from the `environment.ts` the service imports and from class fields built on it. Files `angular.json` or Nx `project.json` names as loaded are anchored, and names written only in router config or module metadata count as used. Over four Angular apps, 129 new consumer contracts, and dead-code rows drop from 315 to 304.+- **Queues, pub/sub and socket events across Laravel and Node** (#2525). Laravel dispatch sites link to the `ShouldQueue` classes that consume them, joined by fully qualified class name. php-amqplib, BullMQ, SQS/SNS, Redis pub/sub and NestJS microservices are read; NATS, Redis and Kafka pattern subscriptions link every publisher they match; two ends link only when they can share a broker. socket.io, NestJS gateways, `ws` and Laravel broadcasting to Echo and pusher-js are read as socket contracts.+- **Topics follow RabbitMQ bindings** (#2501). A `bindQueue` / `queue_bind` links each consumer of the bound queue to the exchange's publishers whose routing key the binding accepts, wherever the binding is declared. Every contract type now runs on one dialect base and one string-expression layer, and topic extraction got faster in the process (307 to 222 ms on a 724-file Python repository).+- **Workspace pages open their evidence in a drawer.** A contract opens its detail and consumer test impact in place, and the contract list pages on the server with search and a linked / unlinked filter; a Needs attention section groups unmatched calls by the matcher's reason (#2497). A co-changing file pair shows each file's recent history, the commit pairs that likely formed it, and whether a contract link explains it, and the page reports which cap trimmed the stored pairs (#2499). Selecting a service or relationship on the System Map opens a non-modal drawer, and blast radius, breaking changes, conformance and the cyclic core are one lens control that recolours the map and lists its findings (#2500). Each surface offers a copyable prompt for an agent.+- **`lazy_load_in_loop`, a new Python performance marker** (#2528). A loop over ORM rows that reads a relationship the query did not load issues one SELECT per row, and with no call in the loop body, `io_in_loop` could not see it. SQLAlchemy, Flask-SQLAlchemy and Django are covered, and the finding names the fix (`selectinload`, `select_related`, `prefetch_related`). Blind-labelled on held-out applications: 29 of 32 correct on a fresh Django repository, 20 of 24 on SQLAlchemy. Advisory, and never the lead of the performance directive.+- **`unbounded_read_reduced_in_memory`, an advisory over-fetch marker** (#2495). A query with no limit whose rows are then deduplicated per key in code; the fix is to select one row per key in the query.+- **An `expected` performance actionability state** (#2514). Filesystem and subprocess repetition has no batch operation to point at, and a loop that already walks its data a chunk at a time is already batched. Both sat in the queue as `investigate` waiting on a prerequisite nothing could supply. On this repository that moved 523 of 629 `investigate` rows to `expected`, one filter away and still counted in every total.+- **Vendor credential shapes and PEM keys are detected by value** (#2223). AWS access keys, GitHub tokens, Slack tokens, Google API keys, Stripe secret keys and PEM private keys are found by their shape, not only by the variable name they are assigned to, in both the file scan and `repowise security scan --history`.+- **The stats page is one report with scoped figures and seven new records** (#2526). Figures drawn from the indexed commit sample say what window they cover. New records: longest function, most patched function, longest name, most reused name, biggest cleanup commit, longest silence between commits, and the test-to-source line ratio.### Changed-- **`HEALTH_ANALYZER_VERSION` is 31.** Pascal opts into assertion detection: DUnit's `Check` / `CheckEquals` / `Fail` family (a new `asserts/lexicon.py` row, broad tier) and DUnitX's `Assert.*` plus the RTL's own `Assert(cond, msg)` (narrow tier — `Assert` is itself an assert-prefixed identifier, so no row was needed). A call in flat statement position sits under a node named `statement`, not the `expression_statement` every other mapped grammar uses, and a `try`'s guarded body and its `except`/`finally` clauses use a distinct `statements` container rather than `block` — both were invisible to the assertion pass, so every assertion inside a `try ... finally Free; end` (close to universal in Delphi tests) went uncounted. Measured on a real ~150-file Delphi codebase's `Test*.dpr` suite: assertion coverage moved from 66/120 files (1,844 assertions) to 86/120 (2,873). `large_assertion_block` / `duplicated_assertion_block` now fire for Pascal; `assertion_free_test` deliberately does not — it gates on a `SHIPPING_LANGUAGES` allowlist that needs its own measured-precision pass before Pascal joins it. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.-- **`HEALTH_ANALYZER_VERSION` is 30.** A Pascal call to a zero-argument procedure may omit its parentheses entirely (`Q.Open;` is as idiomatic as `Q.Open();`), which produces no `exprCall` node at all — just a bare `identifier` / `exprDot` sitting directly under a `statement` wrapper, the same wrapper `Exit;` / `inherited;` use. The performance pass's `call_kinds` gate only recognised `exprCall`, so every parenless call was invisible to it regardless of sink kind — filesystem, subprocess, db and network alike. A new `bare_call_wrapper_kinds` / `PerfDialect.bare_statement_call` hook (default: no-op for every other language) tells a parenless call apart from the wrapper's other tenants; Pascal now finds an `io_in_loop` on `Q.Open;` in a loop exactly as it already did on `Q.Open();`. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.-- **`HEALTH_ANALYZER_VERSION` is 29.** Pascal's `for x in collection do` parses as its own `foreach` node, distinct from the counted `for`, and was missing from `loop_kinds` — the walker skipped it entirely, so any Pascal function using a for-in loop understated both CCN and nesting depth. Pascal also gained a `PerfDialect` (filesystem and subprocess sinks by RTL/VCL/FPC call name, e.g. `CopyFile` / `TFileStream.SaveToFile` / `ShellExecute`), so `io_in_loop` / `hot_path_sync_io` now fire for it instead of the performance pass silently skipping every Pascal file. The `uses` clause now feeds the shared `io_kind` table too (`FireDAC` / `ADODB` → db, `IdHTTP` / `System.Net.HttpClient` → network), so a `TDataSet.Open` / `.ExecSQL` / `.Post` or an HTTP client's `.Get` / `.Post` inside a loop is now a `db` / `network` `io_in_loop` finding when the file's own imports back it up, rather than staying silent — the same file-wide (not receiver-scoped) evidence trade the design already documents for languages with no per-variable type binding. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.+- **Performance plans claim only what they can back** (#2495, #2504, #2513, #2521). Fan-out against a pooled database or network client is advisory with a `bounded_concurrency` prerequisite, since independence says nothing about what the pool can serve. A chunked loop reports `loop_already_chunked` instead of being told to batch. A bulk rewrite is proven only when one bulk call touches exactly the rows the loop did, and not when the loop builds its result in key order, calls something for its effect, or reads through `session.get`, which answers from the identity map when a row is already loaded. Loops report their magnitude (`grows_with_data`, `bounded`, `unknown`), and a raw SQL read with a `LIMIT` no longer claims to grow. Plans carry ordered steps bound to the evidence's locations, and plan validation, which was `unknown` for 330 of 330 plans resolved by id, now resolves for all but 5 of 287.+- **The Architecture page opens on the Files view** (#2503). Each strong pair of communities is drawn as one band sized by its edge count, third-party modules and unconnected files are hidden and counted in the key, and hovering a file draws its real imports, importers and co-change partners in about 1 ms at the default 1,500 nodes. Community colours are keyed by label, so they survive a re-index.+- **PHP has one composer reader and one framework-facts registry** (#2505). Nested manifests, PSR-0 and classmaps are read, and PSR-4 falls back to shorter prefixes as composer's loader does. Grouped and comma-separated `use` statements expand per class, and same-namespace and fully qualified references become edges. A namespaced class no autoload prefix claims is external, so `Illuminate\Http\Request` no longer binds to a local `LoginRequest.php`. Laravel, TYPO3 and Symfony entry points anchor dead-code liveness. Measured on five public PHP repositories: guzzle 10 to 1 dead-code rows, monica 555 to 148, laravel/framework 680 to 392, with graph build time on laravel/framework down from 3.4s to 2.4s.+- **Pascal gains loop, performance and assertion coverage** (#2233). A `for x in collection do` loop was skipped by the complexity walker, understating CCN and nesting. A new performance dialect covers filesystem and subprocess sinks by RTL/VCL/FPC name, the `uses` clause classifies database and network units so `TDataSet.Open` or an HTTP client's `.Get` in a loop is a finding, and a parenless call such as `Q.Open;` is recognised as a call. DUnit and DUnitX assertions are counted, including inside `try ... finally` blocks: on a real ~150-file Delphi test suite, assertion coverage moved from 66 of 120 files to 86 of 120.+- **`HEALTH_ANALYZER_VERSION` moved from 21 to 31** across the performance and Pascal work above, so existing indexes re-score on their next update. `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.+- **Workspace contract maps moved from version 8 to 13**, so the next `repowise update --workspace` re-extracts them.+- **LiteLLM reasoning efforts come from the model's own metadata** (#2240), so discovery and execution agree on which effort values a model accepts.+- **Importing one server schema loads one module** (#2507). `from repowise.server.schemas import X` ran all 29 schema submodules; it now loads the one that defines `X`, taking the import from about 1.3s to 0.44s.+- Several server-side folds moved into `repowise.core` as plain functions over rows, with unchanged output: the overview attention ranking (#2506), test impact assembly (#2508), decision acceptance requirements (#2510), `search_codebase` query routing (#2511), knowledge silos and onboarding targets (#2517), owners, module health and reviewer suggestions (#2518), refactoring summary chips (#2519), the per-file health lead (#2494) and the workspace list reads and MCP tool payloads (#2530).+### Fixed++- **Security snippets never store a credential value** (#2496). A value longer than the 120-character snippet cap was cut before masking, so its head was stored raw; `public_env_secret` values were not masked at all; and any other finding on the same line showed the value unmasked. Every secret on a line is now masked in every snippet taken from it. Keyword matches skip key-name values (`ACCESS_TOKEN = "access_token"`) and template placeholders, a vendor match suppresses the duplicate keyword finding for the same value, and publishable Stripe keys no longer fire.+- **A Rust `impl` block has the visibility of the type it implements** (#2427). The block cannot carry a modifier, so every `impl` in every Rust repository was recorded as private.+- **A Python stdlib import no longer resolves to a local file with the same stem** (#2526). `import json` resolved to a repository's `json.py`, 527 false edges on this repository, which also fed the stats page a wrong most-imported file.+- **A community is never named after a third-party module** (#2502). Labels come from the community's own production files.+- **A contract link always names the provider in `contract_id`** (#2530). A link whose ends were spelled differently carried the consumer's id, and went missing from its provider's detail, tests to run and breaking-change consumers.+- **`REPOWISE_MODEL` is honoured** in provider resolution (#2276), and the `opencode` provider's concurrency is configurable through `REPOWISE_OPENCODE_CONCURRENCY` instead of being fixed at one (#2485).+- **Uninstall removes what install added.** The distill allow rules are removed from `~/.claude/settings.json` and the leftover check looks for them (#2483), and `repowise hook rewrite uninstall` clears `distill.commands.enabled` and removes the `AGENTS.md` section even when Codex is no longer installed (#2491).+- A pathless symbol row no longer joins `get_answer`'s homonym union (#2391), an unknown `search_codebase` mode is reported in `ignored_arguments` instead of silently coerced (#2392), and a failed head-commit read in test impact reports as degraded instead of absent (#2529).+- A validation list keeps the test named for the file when it is capped (#2515), `ViewTabs` scrolls only its own row instead of the page (#2498), and the health map and file drawer name the `expected` state (#2520, #2522).++### Documentation++- 0.52.0's detector count is corrected in nine places, documentation drift gets its own page and a README row, and the generated agent brief mentions it (#2480).+- The workspace documentation lists HTTP and database contract support per language (#2527, #2531).++---## [0.52.0] - 2026-09-20A wide cycle. Documentation makes assertions about code, and this repository has the graph to check them, so a fourth deterministic analysis joins the pipeline: it reads the repository's own markdown, extracts the claims each document makes, resolves them against the real tree, and reports the ones the tree refutes. No model is involved, findings refresh on every update, and the reverse view answers which documents name a given file.diff --git a/docs/reference/UPGRADING.md b/docs/reference/UPGRADING.mdindex 80ee0a4ef..7524afbd0 100644--- a/docs/reference/UPGRADING.md+++ b/docs/reference/UPGRADING.md@@ -33,6 +33,14 @@ It is a recommendation, not a requirement. Nothing is wiped until you choose to## Behaviour changes worth knowing about+### 0.53.0: health re-scores once, and workspace contracts re-extract++**Your first `update` re-scores the whole repository.** The health analyzer version moved from 21 to 31 over this cycle: performance plans now claim only what the loop proves, two new performance markers landed, and Pascal gained loop, performance and assertion coverage. Each of those changes how a stored health number is computed, so the first update after upgrading re-scores every file and takes longer than usual. The next one is back to normal.++**Workspace contracts are re-extracted on the next workspace update.** The contract format moved from version 8 to 13 (Laravel, NestJS, Node clients and ORMs, Angular, queues, sockets and RabbitMQ bindings), so `repowise update --workspace` rebuilds the stored contract maps instead of reusing them.++Nothing needs re-indexing: the store format and parser schema are unchanged. The PHP tree-sitter query did change, so that same first update re-parses files instead of reading them from the parse cache. It happens once and needs no action.+### 0.52.0: decision capture is stricter, and health re-scores onceThree changes you may notice after upgrading to 0.52.0.diff --git a/packages/cli/src/repowise/cli/__init__.py b/packages/cli/src/repowise/cli/__init__.pyindex e63fdf504..327fa563b 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.52.0"+__version__ = "0.53.0"diff --git a/packages/core/src/repowise/core/__init__.py b/packages/core/src/repowise/core/__init__.pyindex 789aa60f7..14584f796 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.52.0"+__version__ = "0.53.0"diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.mdindex 0e62eecba..66b25a262 100644--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md@@ -9,14 +9,58 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0----## [Unreleased]+## [0.53.0] - 2026-09-24++A 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.++Performance plans said more than their evidence supported. A plan now claims `proven` only when the loop itself shows that the rewrite returns what the loop returned. Repetition with nothing to change, such as N reads of N files, leaves the default queue. Two new detectors cover shapes with no call in the loop body for the old ones to see: an ORM relationship lazily loaded once per row, and an unbounded read deduplicated in memory.++PHP gets a graph that reads it correctly. Grouped `use` imports were dropped, same-namespace references had no edge, and PHP framework conventions lived nowhere, so a Laravel app's route files, providers and base controller read as dead code. On laravel/framework, dead-code rows drop from 680 to 392. The Architecture page opens on a Files view that bundles the links between communities, and security finding snippets stop storing credential values in plain text.++### Added++- **Laravel is read the way the framework serves it** (#2512). Route chains and nested closure groups keep their prefixes, `resource` / `apiResource` expand (honouring `only`, `except` and `shallow`), and `routes/api.php` is served under `/api` unless `withRouting(apiPrefix:)` or a route provider says otherwise. A prefix that cannot be read, or two declarations that disagree, refuse the route instead of guessing. Listeners, policies, commands, middleware aliases and scheduled jobs get edges from the file that registers them, so an unregistered listener reads as unused. Eloquent models and `Schema::create` migrations become data contracts. On a five-service TypeScript and Laravel workspace, all 39 cross-service HTTP links now match exactly, against 7 before.+- **NestJS routes, Node HTTP clients and Node ORM tables** (#2527). NestJS controllers are served under the global prefix, URI version and controller prefix, read from wherever the bootstrap settings are declared, per app in a monorepo. axios, ky, got and ofetch calls are read directly or through an instance created with `baseURL` / `prefixUrl`, and an exported instance is followed into the files that import it. Tables are read from Prisma, TypeORM, Sequelize, Drizzle and Knex.+- **Angular `HttpClient` calls and Angular entry points** (#2531). Calls on a receiver typed or injected as `HttpClient` are read for every verb, with the base folded from the `environment.ts` the service imports and from class fields built on it. Files `angular.json` or Nx `project.json` names as loaded are anchored, and names written only in router config or module metadata count as used. Over four Angular apps, 129 new consumer contracts, and dead-code rows drop from 315 to 304.+- **Queues, pub/sub and socket events across Laravel and Node** (#2525). Laravel dispatch sites link to the `ShouldQueue` classes that consume them, joined by fully qualified class name. php-amqplib, BullMQ, SQS/SNS, Redis pub/sub and NestJS microservices are read; NATS, Redis and Kafka pattern subscriptions link every publisher they match; two ends link only when they can share a broker. socket.io, NestJS gateways, `ws` and Laravel broadcasting to Echo and pusher-js are read as socket contracts.+- **Topics follow RabbitMQ bindings** (#2501). A `bindQueue` / `queue_bind` links each consumer of the bound queue to the exchange's publishers whose routing key the binding accepts, wherever the binding is declared. Every contract type now runs on one dialect base and one string-expression layer, and topic extraction got faster in the process (307 to 222 ms on a 724-file Python repository).+- **Workspace pages open their evidence in a drawer.** A contract opens its detail and consumer test impact in place, and the contract list pages on the server with search and a linked / unlinked filter; a Needs attention section groups unmatched calls by the matcher's reason (#2497). A co-changing file pair shows each file's recent history, the commit pairs that likely formed it, and whether a contract link explains it, and the page reports which cap trimmed the stored pairs (#2499). Selecting a service or relationship on the System Map opens a non-modal drawer, and blast radius, breaking changes, conformance and the cyclic core are one lens control that recolours the map and lists its findings (#2500). Each surface offers a copyable prompt for an agent.+- **`lazy_load_in_loop`, a new Python performance marker** (#2528). A loop over ORM rows that reads a relationship the query did not load issues one SELECT per row, and with no call in the loop body, `io_in_loop` could not see it. SQLAlchemy, Flask-SQLAlchemy and Django are covered, and the finding names the fix (`selectinload`, `select_related`, `prefetch_related`). Blind-labelled on held-out applications: 29 of 32 correct on a fresh Django repository, 20 of 24 on SQLAlchemy. Advisory, and never the lead of the performance directive.+- **`unbounded_read_reduced_in_memory`, an advisory over-fetch marker** (#2495). A query with no limit whose rows are then deduplicated per key in code; the fix is to select one row per key in the query.+- **An `expected` performance actionability state** (#2514). Filesystem and subprocess repetition has no batch operation to point at, and a loop that already walks its data a chunk at a time is already batched. Both sat in the queue as `investigate` waiting on a prerequisite nothing could supply. On this repository that moved 523 of 629 `investigate` rows to `expected`, one filter away and still counted in every total.+- **Vendor credential shapes and PEM keys are detected by value** (#2223). AWS access keys, GitHub tokens, Slack tokens, Google API keys, Stripe secret keys and PEM private keys are found by their shape, not only by the variable name they are assigned to, in both the file scan and `repowise security scan --history`.+- **The stats page is one report with scoped figures and seven new records** (#2526). Figures drawn from the indexed commit sample say what window they cover. New records: longest function, most patched function, longest name, most reused name, biggest cleanup commit, longest silence between commits, and the test-to-source line ratio.### Changed-- **`HEALTH_ANALYZER_VERSION` is 31.** Pascal opts into assertion detection: DUnit's `Check` / `CheckEquals` / `Fail` family (a new `asserts/lexicon.py` row, broad tier) and DUnitX's `Assert.*` plus the RTL's own `Assert(cond, msg)` (narrow tier — `Assert` is itself an assert-prefixed identifier, so no row was needed). A call in flat statement position sits under a node named `statement`, not the `expression_statement` every other mapped grammar uses, and a `try`'s guarded body and its `except`/`finally` clauses use a distinct `statements` container rather than `block` — both were invisible to the assertion pass, so every assertion inside a `try ... finally Free; end` (close to universal in Delphi tests) went uncounted. Measured on a real ~150-file Delphi codebase's `Test*.dpr` suite: assertion coverage moved from 66/120 files (1,844 assertions) to 86/120 (2,873). `large_assertion_block` / `duplicated_assertion_block` now fire for Pascal; `assertion_free_test` deliberately does not — it gates on a `SHIPPING_LANGUAGES` allowlist that needs its own measured-precision pass before Pascal joins it. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.-- **`HEALTH_ANALYZER_VERSION` is 30.** A Pascal call to a zero-argument procedure may omit its parentheses entirely (`Q.Open;` is as idiomatic as `Q.Open();`), which produces no `exprCall` node at all — just a bare `identifier` / `exprDot` sitting directly under a `statement` wrapper, the same wrapper `Exit;` / `inherited;` use. The performance pass's `call_kinds` gate only recognised `exprCall`, so every parenless call was invisible to it regardless of sink kind — filesystem, subprocess, db and network alike. A new `bare_call_wrapper_kinds` / `PerfDialect.bare_statement_call` hook (default: no-op for every other language) tells a parenless call apart from the wrapper's other tenants; Pascal now finds an `io_in_loop` on `Q.Open;` in a loop exactly as it already did on `Q.Open();`. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.-- **`HEALTH_ANALYZER_VERSION` is 29.** Pascal's `for x in collection do` parses as its own `foreach` node, distinct from the counted `for`, and was missing from `loop_kinds` — the walker skipped it entirely, so any Pascal function using a for-in loop understated both CCN and nesting depth. Pascal also gained a `PerfDialect` (filesystem and subprocess sinks by RTL/VCL/FPC call name, e.g. `CopyFile` / `TFileStream.SaveToFile` / `ShellExecute`), so `io_in_loop` / `hot_path_sync_io` now fire for it instead of the performance pass silently skipping every Pascal file. The `uses` clause now feeds the shared `io_kind` table too (`FireDAC` / `ADODB` → db, `IdHTTP` / `System.Net.HttpClient` → network), so a `TDataSet.Open` / `.ExecSQL` / `.Post` or an HTTP client's `.Get` / `.Post` inside a loop is now a `db` / `network` `io_in_loop` finding when the file's own imports back it up, rather than staying silent — the same file-wide (not receiver-scoped) evidence trade the design already documents for languages with no per-variable type binding. Existing indexes re-score on their next update; `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.+- **Performance plans claim only what they can back** (#2495, #2504, #2513, #2521). Fan-out against a pooled database or network client is advisory with a `bounded_concurrency` prerequisite, since independence says nothing about what the pool can serve. A chunked loop reports `loop_already_chunked` instead of being told to batch. A bulk rewrite is proven only when one bulk call touches exactly the rows the loop did, and not when the loop builds its result in key order, calls something for its effect, or reads through `session.get`, which answers from the identity map when a row is already loaded. Loops report their magnitude (`grows_with_data`, `bounded`, `unknown`), and a raw SQL read with a `LIMIT` no longer claims to grow. Plans carry ordered steps bound to the evidence's locations, and plan validation, which was `unknown` for 330 of 330 plans resolved by id, now resolves for all but 5 of 287.+- **The Architecture page opens on the Files view** (#2503). Each strong pair of communities is drawn as one band sized by its edge count, third-party modules and unconnected files are hidden and counted in the key, and hovering a file draws its real imports, importers and co-change partners in about 1 ms at the default 1,500 nodes. Community colours are keyed by label, so they survive a re-index.+- **PHP has one composer reader and one framework-facts registry** (#2505). Nested manifests, PSR-0 and classmaps are read, and PSR-4 falls back to shorter prefixes as composer's loader does. Grouped and comma-separated `use` statements expand per class, and same-namespace and fully qualified references become edges. A namespaced class no autoload prefix claims is external, so `Illuminate\Http\Request` no longer binds to a local `LoginRequest.php`. Laravel, TYPO3 and Symfony entry points anchor dead-code liveness. Measured on five public PHP repositories: guzzle 10 to 1 dead-code rows, monica 555 to 148, laravel/framework 680 to 392, with graph build time on laravel/framework down from 3.4s to 2.4s.+- **Pascal gains loop, performance and assertion coverage** (#2233). A `for x in collection do` loop was skipped by the complexity walker, understating CCN and nesting. A new performance dialect covers filesystem and subprocess sinks by RTL/VCL/FPC name, the `uses` clause classifies database and network units so `TDataSet.Open` or an HTTP client's `.Get` in a loop is a finding, and a parenless call such as `Q.Open;` is recognised as a call. DUnit and DUnitX assertions are counted, including inside `try ... finally` blocks: on a real ~150-file Delphi test suite, assertion coverage moved from 66 of 120 files to 86 of 120.+- **`HEALTH_ANALYZER_VERSION` moved from 21 to 31** across the performance and Pascal work above, so existing indexes re-score on their next update. `STORE_FORMAT_VERSION` and `PARSER_SCHEMA_VERSION` are unchanged.+- **Workspace contract maps moved from version 8 to 13**, so the next `repowise update --workspace` re-extracts them.+- **LiteLLM reasoning efforts come from the model's own metadata** (#2240), so discovery and execution agree on which effort values a model accepts.+- **Importing one server schema loads one module** (#2507). `from repowise.server.schemas import X` ran all 29 schema submodules; it now loads the one that defines `X`, taking the import from about 1.3s to 0.44s.+- Several server-side folds moved into `repowise.core` as plain functions over rows, with unchanged output: the overview attention ranking (#2506), test impact assembly (#2508), decision acceptance requirements (#2510), `search_codebase` query routing (#2511), knowledge silos and onboarding targets (#2517), owners, module health and reviewer suggestions (#2518), refactoring summary chips (#2519), the per-file health lead (#2494) and the workspace list reads and MCP tool payloads (#2530).+### Fixed++- **Security snippets never store a credential value** (#2496). A value longer than the 120-character snippet cap was cut before masking, so its head was stored raw; `public_env_secret` values were not masked at all; and any other finding on the same line showed the value unmasked. Every secret on a line is now masked in every snippet taken from it. Keyword matches skip key-name values (`ACCESS_TOKEN = "access_token"`) and template placeholders, a vendor match suppresses the duplicate keyword finding for the same value, and publishable Stripe keys no longer fire.+- **A Rust `impl` block has the visibility of the type it implements** (#2427). The block cannot carry a modifier, so every `impl` in every Rust repository was recorded as private.+- **A Python stdlib import no longer resolves to a local file with the same stem** (#2526). `import json` resolved to a repository's `json.py`, 527 false edges on this repository, which also fed the stats page a wrong most-imported file.+- **A community is never named after a third-party module** (#2502). Labels come from the community's own production files.+- **A contract link always names the provider in `contract_id`** (#2530). A link whose ends were spelled differently carried the consumer's id, and went missing from its provider's detail, tests to run and breaking-change consumers.+- **`REPOWISE_MODEL` is honoured** in provider resolution (#2276), and the `opencode` provider's concurrency is configurable through `REPOWISE_OPENCODE_CONCURRENCY` instead of being fixed at one (#2485).+- **Uninstall removes what install added.** The distill allow rules are removed from `~/.claude/settings.json` and the leftover check looks for them (#2483), and `repowise hook rewrite uninstall` clears `distill.commands.enabled` and removes the `AGENTS.md` section even when Codex is no longer installed (#2491).+- A pathless symbol row no longer joins `get_answer`'s homonym union (#2391), an unknown `search_codebase` mode is reported in `ignored_arguments` instead of silently coerced (#2392), and a failed head-commit read in test impact reports as degraded instead of absent (#2529).+- A validation list keeps the test named for the file when it is capped (#2515), `ViewTabs` scrolls only its own row instead of the page (#2498), and the health map and file drawer name the `expected` state (#2520, #2522).++### Documentation++- 0.52.0's detector count is corrected in nine places, documentation drift gets its own page and a README row, and the generated agent brief mentions it (#2480).+- The workspace documentation lists HTTP and database contract support per language (#2527, #2531).++---## [0.52.0] - 2026-09-20A wide cycle. Documentation makes assertions about code, and this repository has the graph to check them, so a fourth deterministic analysis joins the pipeline: it reads the repository's own markdown, extracts the claims each document makes, resolves them against the real tree, and reports the ones the tree refutes. No model is involved, findings refresh on every update, and the reverse view answers which documents name a given file.diff --git a/packages/server/src/repowise/server/__init__.py b/packages/server/src/repowise/server/__init__.pyindex eb8da2008..1daf366ad 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.52.0"+__version__ = "0.53.0"diff --git a/plugins/claude-code/.claude-plugin/plugin.json b/plugins/claude-code/.claude-plugin/plugin.jsonindex ee1f9ce2e..a74273699 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.52.0",+ "version": "0.53.0","author": {"name": "Repowise","email": "[email protected]",diff --git a/plugins/claude-code/CHANGELOG.md b/plugins/claude-code/CHANGELOG.mdindex 1e1bdcf01..c4b10c106 100644--- a/plugins/claude-code/CHANGELOG.md+++ b/plugins/claude-code/CHANGELOG.md@@ -2,6 +2,14 @@All notable changes to the Repowise Claude Code plugin are documented here.+## 0.53.0++### Changed+- Version bump only. No command, skill or hook changed this cycle: the server+ still lists the same 18 tools, every tool named in a command or skill is one+ of them, no CLI flag a command documents changed, and `hooks.json` still+ mirrors the augment matcher in `claude_config.py`.+## 0.52.0### Changeddiff --git a/pyproject.toml b/pyproject.tomlindex b1e79d5a4..bd42dff70 100644--- a/pyproject.toml+++ b/pyproject.toml@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"[project]name = "repowise"-version = "0.52.0"+version = "0.53.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 279802658..602f7ca33 100644--- a/server.json+++ b/server.json@@ -8,12 +8,12 @@"source": "github"},"websiteUrl": "https://www.repowise.dev",- "version": "0.52.0",+ "version": "0.53.0","packages": [{"registryType": "pypi","identifier": "repowise",- "version": "0.52.0",+ "version": "0.53.0","transport": {"type": "stdio"},diff --git a/uv.lock b/uv.lockindex 261f21f18..e4c6eb636 100644--- a/uv.lock+++ b/uv.lock@@ -3051,7 +3051,7 @@ wheels = [[[package]]name = "repowise"-version = "0.52.0"+version = "0.53.0"source = { editable = "." }dependencies = [{ name = "aiosqlite" },