Skip to content

Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.

release: v0.58.0 (#4316)

Raghav Chamadiyab28c49d711a4
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index a476e70ac..ac6704565 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.57.0",
+ "version": "0.58.0",
"category": "productivity",
"keywords": [
"codebase",
diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
index cb94ceef0..68cb01c36 100644
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@ -10,6 +10,125 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
---
+## [0.58.0] - 2026-10-20
+
+repowise 0.58 makes the first run read like a plan. `repowise init` opens on one plan screen with the scan, an ETA and every step it will run, shows progress as a checklist of finished steps with counts and times, and ends on one finish panel that leads with `repowise serve`. A logged-in Claude Code, Codex or OpenCode is offered with its quota, agents get `--progress json`, a folder of repositories gets the same screen with `--repos`, and init, status and update share one set of mode names, with `repowise update --full` taking a fast index to a full one.
+
+The web UI is redesigned around what to do next: a short Overview, Commits led by each change's health delta and recent wins, an Ownership page built around knowledge coverage and off-boarding, a zoomable folder map with lenses, coupling by area pairs, and Tests and Security pages in a grouped sidebar.
+
+`repowise health check` gates a change in CI on the code-health findings it introduces, using git alone, and flags added suppressions, weakened tests and test-only branches. Health scoring follows a saturating curve per category, names the production-code score beside the headline, and scores files from disk with `repowise health --score` and `--against`. Change risk follows code that moves between files, `get_overview` lays out every package and its front doors in a lean default, GitHub Copilot CLI joins the providers, and every release carries an `openapi.json`.
+
+### Highlights
+
+- **A guided `repowise init`** · One plan screen before the run, a readable checklist of every step while it runs, and a finish panel that opens with `repowise serve`; agents follow along with `--progress json`.
+- **A redesigned Code Health page** · A zoomable folder map with lenses, a Performance tab that opens on the fixes worth making now, what each file's score lost to code shape, history and coverage, and quieter findings with a prompt ready for your agent. → /repos/:id/code-health
+- **An Overview that opens on what to do** · One health reading, a folded Do next, questions drawn from your repository and Explore cards, in a grouped sidebar where Tests and Security have their own pages. → /repos/:id/overview
+- **`repowise health check` in CI** · Fail a change on the code-health findings it writes, with git alone, and warn on added suppressions, weakened tests and test-only branches.
+- **Commits led by code health** · Every commit and change opens on its health delta, the page leads with the period's wins, and a commit sheet hands your agent a prompt for what got worse. → /repos/:id/commits
+- **Ownership and off-boarding** · See how much of your recently changed code more than one person knows, which files one person holds, and what happens to the code if someone leaves. → /repos/:id/owners
+
+### By the numbers
+
+In the 5 days since 0.57.0:
+
+- **278 pull requests** merged, from **35 contributors**, **19 of them first-time contributors**
+- **1,609 files** changed, **+157,134 / -64,952** lines
+- **92 fixes, 80 features, 9 performance changes**, 79 refactors and 7 documentation changes
+- **462 test files** touched, **181** of them new
+- **58 issues** closed
+
+Thank you to everyone who built this release with us.
+
+### Added
+
+- **One plan screen for `repowise init`** (#4253, #4256). An interactive init shows the repository scan, an ETA in seconds ("Under a minute" on a small repository) and the plan (index, decisions, documentation, search, connect, sync) on one screen. Enter runs the free run, `m` picks a model, `e` edits the plan, `s` keeps the global MCP entry where it is, and `q` quits and removes the `.repowise/` the run just made. A model is a visible opt-in that names the detected key or the logged-in CLI, and the screen offers to keep machine-specific files out of git.
+- **Progress you can read** (#4251). Each finished step leaves a row with its count and time, running rows show the current file or page, a time-left figure appears once a step has a known total and a measured rate, and a Next line lists the stages still to run. A step running past 10 s says Ctrl-C is safe and names `repowise init --resume`. One progress display serves init, workspace init, `update`, `update --full` and `reindex`.
+- **Short lines when piped, and `--progress json` for agents** (#4254). Init exits 0 on a clean run, 2 when it finishes with gaps and 130 when interrupted (#4242, #4269).
+- **One finish panel that leads with `repowise serve`** (#4248, #4263). It names what the run built and which agent is connected (with the Claude Code restart it needs), gives two example questions, `repowise serve` with its port, at most two more steps, the files init added and whether auto-sync is on. A workspace run ends on the same panel with a Scope row and a per-repository documentation list.
+- **Logged-in Claude Code, Codex and OpenCode, offered with their quota** (#4247). A logged-in subscription CLI appears in the provider picker and the generation plan with its cost as model calls, parallel processes and minutes, and it runs only when you pick it. The picker defaults to what `--yes` would run.
+- **A brand theme with ASCII fallbacks** (#4257). Init honours `NO_COLOR`, every glyph has an ASCII form for non-UTF-8 terminals, and the mini owl ends the run showing how it went.
+- **The same plan screen for a folder of repositories, and `init --repos`** (#4262, #4260, #4264). A workspace init lists its repositories and `r` chooses which to include. `--repos` picks them by name or path in scripts, a re-run that picks a subset keeps the others in `.repowise-workspace.yaml`, linked git worktrees are skipped, and `workspace add` builds documentation from code by default.
+- **Init asks before pointing the global MCP entry at this repository** (#4246). It names where the Claude Code and Claude Desktop entry points today and where it will point. `--yes` and scripted runs register and print both targets.
+- **`repowise update --full` takes a fast index to a full one** (#4244), with no API key needed for a Built from code index, and every surface names that command. After a keyless init, `generate` and `update --full` with a model also read the decision sources the fast run skipped, priced on their own line (#4243).
+- **`repowise status` says what the next update re-scores** (#4301). One line names a pending health re-score or security rescan, and `status --format json` reports `rescore_pending`.
+- **A lean CLAUDE.md and AGENTS.md block** (#4235, #4294). It carries the date and commit, the files that need care, one code-health line, the top three decisions, three working bullets and the tool table, and the sections you want can be added back.
+- **A redesigned web UI** (#4163, #4157, #4138, #4164, #4142). The Overview, Code Health, Commits and Ownership pages open on what to do next, findings carry a prompt for your agent, and the sidebar groups every page. The entries below cover each page.
+- **A short Overview that opens on what to do** (#4163, #3966). One health reading, a folded Do next with its count in the heading, an ask box with questions drawn from the repository, and six Explore cards whose figures match the pages they open.
+- **Commits and Changes lead with code health** (#4137, #4141, #4154, #4133). Every commit row opens on its health delta (better, worse, mixed or neutral) and marks hotspot touches. The page opens on a period headline that counts improvements first, then recent wins, then filters for health impact, hotspots, time window, author and area kept in the URL. The commit sheet reads the verdict, Got better and Got worse grouped by file, with a prompt to fix what got worse, and Change Records lead with their health rollup and say where a moved finding came from. `GET /wins` lists resolved findings, files whose score rose and refactorings that landed.
+- **Ownership around knowledge coverage and off-boarding** (#4136, #4153). The page opens on knowledge coverage, the share of recently changed code held by two or more people, beside single-owner hotspots, quiet owners and the truck factor, with tabs for knowledge risks, knowledge loss and an off-boarding what-if (`?leave=&threshold=`). A person's page leads with what depends on them and who could take it over. `GET /owners/summary` and `GET /owners/knowledge-matrix` serve the figures.
+- **A zoomable folder map with lenses** (#4157, #4135). Code Health's Map shows each directory as a disc inside its parent and opens areas into sub-areas and files as you zoom, with `?area=` in the URL, lenses including main author and knowledge risk, and a context rail with the area's score, 30-day delta, trend, worst files, hotspots, owners and top findings. `GET /areas/tree` and `GET /areas/{path}` serve directory rollups at any depth, and JSON responses over 1 KB are gzipped (the map payload goes out at 51 KB from 634 KB).
+- **Hotspots searched and paged over the whole set** (#4162), with server search by path and owner, filters for bus factor 1, accelerating and bug magnets, sorting on any column and facet counts.
+- **Coupling opens on area pairs** (#4152). The tab leads with the area pairs that change together with no import to explain it, ranked by unexplained file pairs, and drills into one pair's files. Each row copies a decouple prompt, and `GET /coupling/areas` serves the pairs.
+- **Tests and Security pages, in a grouped sidebar** (#4142, #4186). The repository sidebar groups pages into Understand, Code quality, People & History and Settings, Tests and Security have their own pages, and the sidebar stays open on Docs.
+- **What each file's score lost** (#4124, #4132). File drawers and pages split the deduction under the score into code shape, change history and test coverage.
+- **`repowise health check`: a CI gate on the findings a change introduces** (#4302). `repowise health check origin/main...HEAD` needs git only: it analyses the changed files at base and head and matches findings by file, marker and symbol. It exits 1 on a code-shape finding written on the change's own lines at high severity or above (`--fail-at medium|high|critical`), and `--fail-on worsened` also fails findings the change made worse. Moved and renamed code is context, rules in `.repowise/health-rules.json` are read from the base, and output comes as a table, JSON, Markdown, GitHub annotations, SARIF or GitLab Code Quality. Exit codes are 0 passed, 1 failed, 2 could not evaluate.
+- **Diff-risk rules in `health check`** (#4312). `added-suppression` (a new lint, type-check, coverage or repowise suppression), `weakened-tests` (a new skip or focus marker, fewer test cases or assertions, a looser coverage threshold) and `test-only-branch` (a test-environment check in production code) warn by default. `--diff-risk warn|error|off`, or `RULE=LEVEL`, sets each level.
+- **Baseline-growth gates for security and doc drift** (#4299). `--fail-on-baseline-growth` (action input `fail-on-baseline-growth`) fails the gate when the committed baseline lists a finding the base's copy does not. A first baseline passes.
+- **`repowise health --score` and `--against`** (#4139, #4155). `--score <paths>` scores files from disk with the index's git history, coverage, test pairing and dependents, so a file reads as the next update would score it. `--against <rev>` scores the same files at a revision and prints before, after and the weighted average.
+- **`get_health(include=["what_if"])`** (#4130). For the worst files or the targets, each code-shape finding's points, what removing it gains the file, the headline and the hotspot average, the file's ceiling, and the best single fixes across them. Metric rows carry `structure_deduction` and `history_deduction` (#4108).
+- **Production code's score beside the headline** (#4204). `repowise health` names Production code beside Code health while tests are in the reading, and `get_health` kpis carry `production_average`. Files with fewer than 5 commits report `history: "short"` (#4117).
+- **Change risk follows moved code** (#4109, #4112, #4125, #4127). Symbols a change moves across files are mapped, findings pair across the move, a pure split reads as moved, and improved findings are counted and stored with `moved_from`.
+- **`health_delta` per changed file** (#4123, #4128). `get_change_risk` lists up to 10 analysed files with base and head score, structure deduction and size, largest move first, and both sides read the index's dependents.
+- **`get_overview` lays out every package** (#4214, #4207). The lean default carries the week's top three actions, the headline health with the production score and band counts, the five riskiest files and a compact scope digest, plus every package with its front doors, layer roots and build, test and lint commands. `include=["tools"]`, `["actions"]` and `["scope"]` add the rest.
+- **MCP tool annotations** (#2762), built from each tool's safety class.
+- **`get_answer` cites the files its answer names** (#4202), and `get_why` anchors a question on the indexed file it names, reported in `anchored_on` (#4203).
+- **A symptom for suspects over MCP** (#4205). `get_context` takes `symptom` (issue text, an error or a stack trace) for `include=["suspects"]`, `repowise context --symptom` does the same, and path targets feed suspects their stem, symbol and directory names.
+- **GitHub Copilot CLI as a provider** (#3710).
+- **`openapi.json` on every GitHub release** (#3948). Each operation carries `x-repowise-stability: stable` for integration routes or `internal` for dashboard payloads.
+- **PHP dataflow and Extract Method plans** (#3466).
+- **Prior defects counted by conventional commit type** (#4126), including an unknown type that names a fix.
+- **Performance loops sized by the tables they read** (#4236). A loop that grows only by reading small tables is bounded with reason `small_table`.
+- **Language reach.** Dart for-in loop variables are typed from the container they walk (#3853), and C# 14 `extension` block members are extension methods (#3920).
+- Old docs links on the website land on the matching docs.repowise.dev page (#4238).
+
+### Changed
+
+- **One set of mode names** (#4249, #4284, #4309). Init, status, update and the editor files say Built from code, Written by <model> and Index only, "Documentation" names the pages, and each mode names the same next command everywhere (`repowise update --full`, then `repowise generate`). Flags, state and JSON values are unchanged.
+- **Health scoring saturates per category** (#4144, #4129). Each defect category follows `A * (1 - exp(-raw / A))` with `A` at 3.09 times the category cap, findings on one function count the largest whole and the rest at 0.25, history findings are de-stacked the same way before their cap, and the score breakdown reports each category's ceiling.
+- **`bumpy_road` is `repeated_nesting`, and `brain_method` is advisory** (#4113, #4115). Old ids keep working in `health-rules.json`, findings and filters, and `brain_method` is listed without a deduction since the size markers already charge that function. Five markers read as Deep nesting, Long function, Compound condition, Many authors and Fading ownership (#4119), and size markers read judged CCN and code lines (#4116).
+- **Health findings fit the code they describe.** `primitive_obsession` skips test material (#4118), coverage markers skip re-export-only files (#4110), a docs folder counts as docs only at the root or beside a docs-site config (#4200), and a critical code-shape marker ranks as high in Fix first (#4199).
+- **One performance headline, led by the causes worth fixing now** (#4231, #4227, #4138, #4165). CLAUDE.md, AGENTS.md, `get_health`, `repowise health`, `repowise status`, the Overview and Code Health share one figure, Fix first and Do next name performance work once its cost is confirmed, and the Performance tab opens on the changes worth making now, grouped by area with a bulk agent prompt.
+- **Do next acts on a week's regressions** (#4198, #3966). Its Now group holds defect-class regressions with proven cost and lost measured coverage, the week's code-shape findings become one row to plan, and only a live credential is critical.
+- **A leaner `get_change_risk` default** (#4221, #4215, #4210). It keeps every fact an agent acts on, leads the headline, reasons, actions and findings with the same finding ("1 of 6 new findings needs review"), and trims a requested evidence checklist inside its rows so a 75-file commit returns one.
+- **Quieter findings cards** (#4164). Hairline outlines, severity as a dot and a word, the path printed once, and "Copy prompt for your agent" as a ghost button, with one filled prompt for the filtered rows.
+- **One `FilePath` everywhere** (#4161). The file name is never cut, the directory shortens first, and the full path is the tooltip.
+- **Dead code is tiered after the cross-repository cut** (#4196), so `safe_only` and the summary counts agree.
+- **Workspace views** state `code_files` from one population with a real summary per repository (#4216), and five workspace error replies are clearer (#3943).
+- **`repowise reindex` turns semantic search on after a keyless init** (#4240) with a detected embedder, and every run names its embedder.
+- **The knowledge graph's layer-naming prompt** lists each layer's largest folders with file counts (#4206).
+- **Code health reads as technical debt in the UI** (#4180), and clearer labels in `risk`, dead code, `whats-new` and the generation report (#4197).
+- **Faster updates and MCP calls.** A prose-only update reuses stored clone and dead-code results, saving 17-32 s and 12-27 s (#4217), the commit-health scan per update is capped at 10 s and drains newest first (#4213), SQLite statistics refresh after each index write (#4229), health rows are replaced in one statement (#4226), and the architecture map classifies each path once (#4222). A repeated committed `get_change_risk` range is served from a per-process cache (#4209), test selection runs off the event loop and is reused per change (#4208), change health reuses parses by content (#4311), and `get_why` looks up named files in one query (#4218). Repositories open through a `Repo` that closes without a full garbage collection, about 1 s per pass on Windows (#4212).
+- **Behaviour pinned by golden snapshots** (#3970, #3971, #3972, #3974) across scanning, dead code, health, the parser, persistence order and MCP payloads, while init, update, workspace, serve, doctor, the pipeline, git indexing, health, dead code, security scanning and the MCP tools are organised into small staged modules (#3951, #3973, #3976, #3977, #3979, #3980, #3981, #3982, #3983, #3985, #3986, #3987, #3988, #3989, #3997, #3999, #4000, #4001, #4002, #4003, #4004, #4005, #4006, #4007, #4008, #4010, #4011, #4013, #4016, #4017, #4018, #4020, #4021, #4022, #4025, #4038, #4039, #4040, #4041, #4042, #4043, #4044, #4045, #4046, #4047, #4048, #4049, #4050, #4051, #4052, #4053, #4054, #4055, #4056, #4057, #4058, #4059, #4060, #4062, #4063, #4064, #4065, #4066, #4067, #4068, #4069, #4070, #4071, #4072, #4073, #4074, #4075, #4076, #4077, #4078, #4080, #4081, #4082, #4265, #4268, #4270).
+- **`HEALTH_ANALYZER_VERSION` moved from 40 to 41** with the scoring changes above, so existing indexes re-score on their next update. **`PARSER_SCHEMA_VERSION` moved from 8 to 9** (Kotlin calls chained on calls), so the parse cache refreshes once, automatically. `STORE_FORMAT_VERSION` is unchanged and nothing needs re-indexing.
+
+### Fixed
+
+- **Init and update.** `--no-prose` makes no model calls with a key set (#4239). A re-run skips the files init wrote and a fast re-init keeps the documentation (#4245). `status` and `state.json` describe the index the last command left, with "Index in progress" while init runs (#4241). Workspace init and `workspace add` stamp each repository so the first `update` has nothing to redo (#4293, #4310). `init --repos` with no names is a usage error (#4300), customize keeps `-x` excludes (#4061), `update --full` works on an index copied to a new path (#4308), `update` recounts the file-page scope every run (#4220) and retires template pages the selection drops (#4211), and a docs-mode update records its repair marker (#4026). `generate` counts model-free pages correctly in its summary (#3776).
+- **Workspace.** Repository aliases are kept and cancellation propagates (#4107), any `state.json` shape reads (#4036), errors reading saved exclude patterns are logged (#3054), and `workspace list` counts like `status` (#3984).
+- **Doctor and serve.** `doctor` exits 1 in table mode when a check fails (#4289) and runs in linked git worktrees (#1952). `serve` keeps web UI archive members inside its cache directory (#3975).
+- **Editor files.** Key modules and architecture skip structure-only preambles (#3261).
+- **Graph.** Go calls through interface-typed variables bind to the interface's method specs (#3850). A Kotlin call chained on a call is typed (#3845), Kotlin and Swift properties initialised with a constructor are typed (#3789), a Kotlin typealias leads to the class it names (#3787), and top-level Kotlin declarations with two annotations are symbols (#3839). A Python name alias reaches its real definition (#2799), Rust `cfg` build variants get their own ids (#3020), C# object-initializer locals bind (#3957), and React Native platform files resolve to import edges (#3711).
+- **Ingestion and classification.** Stored signatures and docstrings use LF line endings (#3929), `test-helpers` and `test-utils` directories are test support (#3257), and PHP production classes named `Test.php` outside a testsuite are production code (#3399).
+- **Dead code.** A Swift extension whose member name is declared elsewhere (#3876), C and C++ files listed in CMake, `.vcxproj` or `.rc` (#4121), Kotlin `@Suppress("unused")` (#3873), C# classes with custom MEF export attributes (#4009), C# cmdlets, source generators and benchmarks (#3926), Spring servlet initializers (#3921) and `@GlideModule` (#3886) are all recognised as used. A module's dead-code penalty is normalised by its symbol count (#4083).
+- **Health.** `repowise health --format json` keeps withheld finding types (#4111), the headline shows Hotspot only when a figure exists (#4295), findings stored under a renamed marker id get their advice (#4305, #4177), `.repowise/health-rules.json` applies when rescoring commits (#4179), `score_breakdown` lists defect findings only (#4178), active contributors count by canonical identity (#4086), cut-off signatures and stub bodies are declarations (#3950), and C++ condition declarations count as reads (#4122).
+- **Performance and refactoring.** A cause reached by a request, consumer or job role is entry reachable (#4234), queue rows are numbered by their place (#4233), the characterization step names the changed function and the tests that reach it (#4232), Java helper types and throws are kept (#3882), Extract Method helpers return what the caller reads (#3938), and dataflow builds try regions inside switch arms (#3694).
+- **Coverage and tests.** The recommended per-test coverage command exists (#3676), the inferred basis reads the cached test-reach walk (#4158), test selection runs only the tests that read a changed fixture file (#4267), and test-reachability reads batch their `IN` lists (#3933).
+- **Security.** Allow markers work in prose without a comment opener (#4143), a truncated digest or a cache key's md5 reads as an id (#4201), and public API in published C# projects is flagged (#3579).
+- **MCP and suspects.** Bare symbol names defined only in excluded files are gated (#4084), and suspects says when candidates reach the change index cap (#3930).
+- **Web UI.** Code Health, Overview, Commits and Owners render payloads from the previous release's server (#4304, #4306, #4303), the Overview Tests card's route and command can be set by a host (#4307), and the Why this score arithmetic names the 1.0 floor (#4132).
+- **Events, decisions and doc drift.** Tied owners at the ownership margin are ignored (#3870), a hand-recorded proposed decision reads as hand-recorded (#4015), doc-drift paths join by normalised segments (#4023), and a failing `on_error` leaves a guarded step's result intact (#4079).
+- **VS Code.** Doc drift diagnostics follow live edits (#2782).
+- **Cost.** Gemini 3 preview models are priced at their own rates (#3967).
+
+### Documentation
+
+- The quickstart has a human path and an agent path, serves first, and lists every mode with its upgrade command (#4250), and every page that teaches init says what the CLI does (#4255).
+- Change evidence, components, policy and reports in the README and docs (#3947), the README's benchmark tile matches the benchmark method (#3969), and the untested hotspot conditions and complexity README are corrected (#3449, #4169).
+
+### Dependencies
+
+- Security updates: aiohttp 3.14.4 and mcp 1.30.0 (declared floor `mcp>=1.30.0,<2`) (#4292).
+
## [0.57.0] - 2026-10-15
repowise 0.57 reads every merged change as a Change Record, rebuilt from git with an evidence checklist (owners, reaching tests, contracts, decisions crossed, provenance with coverage) and its outcomes, and the Commits page groups commits by change. On top of those records, `repowise check` evaluates a local change policy from `.repowise/policies.yaml` and writes SARIF or JUnit, `repowise report` writes assessment, change evidence and inventory packs, and `repowise suspects` ranks recent changes against a symptom with the evidence for each. Components follow the Backstage model, compare declared owners with recent activity, and export package usage as CycloneDX. AI attribution is three-state with coverage, with opt-in edit capture for Claude Code, Codex and Cursor.
diff --git a/package-lock.json b/package-lock.json
index da4f5d1f3..bfdc43db7 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -19360,7 +19360,7 @@
},
"packages/vscode": {
"name": "repowise",
- "version": "0.12.0",
+ "version": "0.13.0",
"license": "AGPL-3.0-or-later",
"devDependencies": {
"@repowise-dev/api-client": "*",
diff --git a/packages/cli/src/repowise/cli/__init__.py b/packages/cli/src/repowise/cli/__init__.py
index fa2e2a755..9f9ac9209 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.57.0"
+__version__ = "0.58.0"
diff --git a/packages/core/src/repowise/core/__init__.py b/packages/core/src/repowise/core/__init__.py
index d95e45d70..9c2a8b216 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 o
Namespace package: repowise.core is part of the repowise namespace.
"""
-__version__ = "0.57.0"
+__version__ = "0.58.0"
diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
index cb94ceef0..68cb01c36 100644
--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
@@ -10,6 +10,125 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
---
+## [0.58.0] - 2026-10-20
+
+repowise 0.58 makes the first run read like a plan. `repowise init` opens on one plan screen with the scan, an ETA and every step it will run, shows progress as a checklist of finished steps with counts and times, and ends on one finish panel that leads with `repowise serve`. A logged-in Claude Code, Codex or OpenCode is offered with its quota, agents get `--progress json`, a folder of repositories gets the same screen with `--repos`, and init, status and update share one set of mode names, with `repowise update --full` taking a fast index to a full one.
+
+The web UI is redesigned around what to do next: a short Overview, Commits led by each change's health delta and recent wins, an Ownership page built around knowledge coverage and off-boarding, a zoomable folder map with lenses, coupling by area pairs, and Tests and Security pages in a grouped sidebar.
+
+`repowise health check` gates a change in CI on the code-health findings it introduces, using git alone, and flags added suppressions, weakened tests and test-only branches. Health scoring follows a saturating curve per category, names the production-code score beside the headline, and scores files from disk with `repowise health --score` and `--against`. Change risk follows code that moves between files, `get_overview` lays out every package and its front doors in a lean default, GitHub Copilot CLI joins the providers, and every release carries an `openapi.json`.
+
+### Highlights
+
+- **A guided `repowise init`** · One plan screen before the run, a readable checklist of every step while it runs, and a finish panel that opens with `repowise serve`; agents follow along with `--progress json`.
+- **A redesigned Code Health page** · A zoomable folder map with lenses, a Performance tab that opens on the fixes worth making now, what each file's score lost to code shape, history and coverage, and quieter findings with a prompt ready for your agent. → /repos/:id/code-health
+- **An Overview that opens on what to do** · One health reading, a folded Do next, questions drawn from your repository and Explore cards, in a grouped sidebar where Tests and Security have their own pages. → /repos/:id/overview
+- **`repowise health check` in CI** · Fail a change on the code-health findings it writes, with git alone, and warn on added suppressions, weakened tests and test-only branches.
+- **Commits led by code health** · Every commit and change opens on its health delta, the page leads with the period's wins, and a commit sheet hands your agent a prompt for what got worse. → /repos/:id/commits
+- **Ownership and off-boarding** · See how much of your recently changed code more than one person knows, which files one person holds, and what happens to the code if someone leaves. → /repos/:id/owners
+
+### By the numbers
+
+In the 5 days since 0.57.0:
+
+- **278 pull requests** merged, from **35 contributors**, **19 of them first-time contributors**
+- **1,609 files** changed, **+157,134 / -64,952** lines
+- **92 fixes, 80 features, 9 performance changes**, 79 refactors and 7 documentation changes
+- **462 test files** touched, **181** of them new
+- **58 issues** closed
+
+Thank you to everyone who built this release with us.
+
+### Added
+
+- **One plan screen for `repowise init`** (#4253, #4256). An interactive init shows the repository scan, an ETA in seconds ("Under a minute" on a small repository) and the plan (index, decisions, documentation, search, connect, sync) on one screen. Enter runs the free run, `m` picks a model, `e` edits the plan, `s` keeps the global MCP entry where it is, and `q` quits and removes the `.repowise/` the run just made. A model is a visible opt-in that names the detected key or the logged-in CLI, and the screen offers to keep machine-specific files out of git.
+- **Progress you can read** (#4251). Each finished step leaves a row with its count and time, running rows show the current file or page, a time-left figure appears once a step has a known total and a measured rate, and a Next line lists the stages still to run. A step running past 10 s says Ctrl-C is safe and names `repowise init --resume`. One progress display serves init, workspace init, `update`, `update --full` and `reindex`.
+- **Short lines when piped, and `--progress json` for agents** (#4254). Init exits 0 on a clean run, 2 when it finishes with gaps and 130 when interrupted (#4242, #4269).
+- **One finish panel that leads with `repowise serve`** (#4248, #4263). It names what the run built and which agent is connected (with the Claude Code restart it needs), gives two example questions, `repowise serve` with its port, at most two more steps, the files init added and whether auto-sync is on. A workspace run ends on the same panel with a Scope row and a per-repository documentation list.
+- **Logged-in Claude Code, Codex and OpenCode, offered with their quota** (#4247). A logged-in subscription CLI appears in the provider picker and the generation plan with its cost as model calls, parallel processes and minutes, and it runs only when you pick it. The picker defaults to what `--yes` would run.
+- **A brand theme with ASCII fallbacks** (#4257). Init honours `NO_COLOR`, every glyph has an ASCII form for non-UTF-8 terminals, and the mini owl ends the run showing how it went.
+- **The same plan screen for a folder of repositories, and `init --repos`** (#4262, #4260, #4264). A workspace init lists its repositories and `r` chooses which to include. `--repos` picks them by name or path in scripts, a re-run that picks a subset keeps the others in `.repowise-workspace.yaml`, linked git worktrees are skipped, and `workspace add` builds documentation from code by default.
+- **Init asks before pointing the global MCP entry at this repository** (#4246). It names where the Claude Code and Claude Desktop entry points today and where it will point. `--yes` and scripted runs register and print both targets.
+- **`repowise update --full` takes a fast index to a full one** (#4244), with no API key needed for a Built from code index, and every surface names that command. After a keyless init, `generate` and `update --full` with a model also read the decision sources the fast run skipped, priced on their own line (#4243).
+- **`repowise status` says what the next update re-scores** (#4301). One line names a pending health re-score or security rescan, and `status --format json` reports `rescore_pending`.
+- **A lean CLAUDE.md and AGENTS.md block** (#4235, #4294). It carries the date and commit, the files that need care, one code-health line, the top three decisions, three working bullets and the tool table, and the sections you want can be added back.
+- **A redesigned web UI** (#4163, #4157, #4138, #4164, #4142). The Overview, Code Health, Commits and Ownership pages open on what to do next, findings carry a prompt for your agent, and the sidebar groups every page. The entries below cover each page.
+- **A short Overview that opens on what to do** (#4163, #3966). One health reading, a folded Do next with its count in the heading, an ask box with questions drawn from the repository, and six Explore cards whose figures match the pages they open.
+- **Commits and Changes lead with code health** (#4137, #4141, #4154, #4133). Every commit row opens on its health delta (better, worse, mixed or neutral) and marks hotspot touches. The page opens on a period headline that counts improvements first, then recent wins, then filters for health impact, hotspots, time window, author and area kept in the URL. The commit sheet reads the verdict, Got better and Got worse grouped by file, with a prompt to fix what got worse, and Change Records lead with their health rollup and say where a moved finding came from. `GET /wins` lists resolved findings, files whose score rose and refactorings that landed.
+- **Ownership around knowledge coverage and off-boarding** (#4136, #4153). The page opens on knowledge coverage, the share of recently changed code held by two or more people, beside single-owner hotspots, quiet owners and the truck factor, with tabs for knowledge risks, knowledge loss and an off-boarding what-if (`?leave=&threshold=`). A person's page leads with what depends on them and who could take it over. `GET /owners/summary` and `GET /owners/knowledge-matrix` serve the figures.
+- **A zoomable folder map with lenses** (#4157, #4135). Code Health's Map shows each directory as a disc inside its parent and opens areas into sub-areas and files as you zoom, with `?area=` in the URL, lenses including main author and knowledge risk, and a context rail with the area's score, 30-day delta, trend, worst files, hotspots, owners and top findings. `GET /areas/tree` and `GET /areas/{path}` serve directory rollups at any depth, and JSON responses over 1 KB are gzipped (the map payload goes out at 51 KB from 634 KB).
+- **Hotspots searched and paged over the whole set** (#4162), with server search by path and owner, filters for bus factor 1, accelerating and bug magnets, sorting on any column and facet counts.
+- **Coupling opens on area pairs** (#4152). The tab leads with the area pairs that change together with no import to explain it, ranked by unexplained file pairs, and drills into one pair's files. Each row copies a decouple prompt, and `GET /coupling/areas` serves the pairs.
+- **Tests and Security pages, in a grouped sidebar** (#4142, #4186). The repository sidebar groups pages into Understand, Code quality, People & History and Settings, Tests and Security have their own pages, and the sidebar stays open on Docs.
+- **What each file's score lost** (#4124, #4132). File drawers and pages split the deduction under the score into code shape, change history and test coverage.
+- **`repowise health check`: a CI gate on the findings a change introduces** (#4302). `repowise health check origin/main...HEAD` needs git only: it analyses the changed files at base and head and matches findings by file, marker and symbol. It exits 1 on a code-shape finding written on the change's own lines at high severity or above (`--fail-at medium|high|critical`), and `--fail-on worsened` also fails findings the change made worse. Moved and renamed code is context, rules in `.repowise/health-rules.json` are read from the base, and output comes as a table, JSON, Markdown, GitHub annotations, SARIF or GitLab Code Quality. Exit codes are 0 passed, 1 failed, 2 could not evaluate.
+- **Diff-risk rules in `health check`** (#4312). `added-suppression` (a new lint, type-check, coverage or repowise suppression), `weakened-tests` (a new skip or focus marker, fewer test cases or assertions, a looser coverage threshold) and `test-only-branch` (a test-environment check in production code) warn by default. `--diff-risk warn|error|off`, or `RULE=LEVEL`, sets each level.
+- **Baseline-growth gates for security and doc drift** (#4299). `--fail-on-baseline-growth` (action input `fail-on-baseline-growth`) fails the gate when the committed baseline lists a finding the base's copy does not. A first baseline passes.
+- **`repowise health --score` and `--against`** (#4139, #4155). `--score <paths>` scores files from disk with the index's git history, coverage, test pairing and dependents, so a file reads as the next update would score it. `--against <rev>` scores the same files at a revision and prints before, after and the weighted average.
+- **`get_health(include=["what_if"])`** (#4130). For the worst files or the targets, each code-shape finding's points, what removing it gains the file, the headline and the hotspot average, the file's ceiling, and the best single fixes across them. Metric rows carry `structure_deduction` and `history_deduction` (#4108).
+- **Production code's score beside the headline** (#4204). `repowise health` names Production code beside Code health while tests are in the reading, and `get_health` kpis carry `production_average`. Files with fewer than 5 commits report `history: "short"` (#4117).
+- **Change risk follows moved code** (#4109, #4112, #4125, #4127). Symbols a change moves across files are mapped, findings pair across the move, a pure split reads as moved, and improved findings are counted and stored with `moved_from`.
+- **`health_delta` per changed file** (#4123, #4128). `get_change_risk` lists up to 10 analysed files with base and head score, structure deduction and size, largest move first, and both sides read the index's dependents.
+- **`get_overview` lays out every package** (#4214, #4207). The lean default carries the week's top three actions, the headline health with the production score and band counts, the five riskiest files and a compact scope digest, plus every package with its front doors, layer roots and build, test and lint commands. `include=["tools"]`, `["actions"]` and `["scope"]` add the rest.
+- **MCP tool annotations** (#2762), built from each tool's safety class.
+- **`get_answer` cites the files its answer names** (#4202), and `get_why` anchors a question on the indexed file it names, reported in `anchored_on` (#4203).
+- **A symptom for suspects over MCP** (#4205). `get_context` takes `symptom` (issue text, an error or a stack trace) for `include=["suspects"]`, `repowise context --symptom` does the same, and path targets feed suspects their stem, symbol and directory names.
+- **GitHub Copilot CLI as a provider** (#3710).
+- **`openapi.json` on every GitHub release** (#3948). Each operation carries `x-repowise-stability: stable` for integration routes or `internal` for dashboard payloads.
+- **PHP dataflow and Extract Method plans** (#3466).
+- **Prior defects counted by conventional commit type** (#4126), including an unknown type that names a fix.
+- **Performance loops sized by the tables they read** (#4236). A loop that grows only by reading small tables is bounded with reason `small_table`.
+- **Language reach.** Dart for-in loop variables are typed from the container they walk (#3853), and C# 14 `extension` block members are extension methods (#3920).
+- Old docs links on the website land on the matching docs.repowise.dev page (#4238).
+
+### Changed
+
+- **One set of mode names** (#4249, #4284, #4309). Init, status, update and the editor files say Built from code, Written by <model> and Index only, "Documentation" names the pages, and each mode names the same next command everywhere (`repowise update --full`, then `repowise generate`). Flags, state and JSON values are unchanged.
+- **Health scoring saturates per category** (#4144, #4129). Each defect category follows `A * (1 - exp(-raw / A))` with `A` at 3.09 times the category cap, findings on one function count the largest whole and the rest at 0.25, history findings are de-stacked the same way before their cap, and the score breakdown reports each category's ceiling.
+- **`bumpy_road` is `repeated_nesting`, and `brain_method` is advisory** (#4113, #4115). Old ids keep working in `health-rules.json`, findings and filters, and `brain_method` is listed without a deduction since the size markers already charge that function. Five markers read as Deep nesting, Long function, Compound condition, Many authors and Fading ownership (#4119), and size markers read judged CCN and code lines (#4116).
+- **Health findings fit the code they describe.** `primitive_obsession` skips test material (#4118), coverage markers skip re-export-only files (#4110), a docs folder counts as docs only at the root or beside a docs-site config (#4200), and a critical code-shape marker ranks as high in Fix first (#4199).
+- **One performance headline, led by the causes worth fixing now** (#4231, #4227, #4138, #4165). CLAUDE.md, AGENTS.md, `get_health`, `repowise health`, `repowise status`, the Overview and Code Health share one figure, Fix first and Do next name performance work once its cost is confirmed, and the Performance tab opens on the changes worth making now, grouped by area with a bulk agent prompt.
+- **Do next acts on a week's regressions** (#4198, #3966). Its Now group holds defect-class regressions with proven cost and lost measured coverage, the week's code-shape findings become one row to plan, and only a live credential is critical.
+- **A leaner `get_change_risk` default** (#4221, #4215, #4210). It keeps every fact an agent acts on, leads the headline, reasons, actions and findings with the same finding ("1 of 6 new findings needs review"), and trims a requested evidence checklist inside its rows so a 75-file commit returns one.
+- **Quieter findings cards** (#4164). Hairline outlines, severity as a dot and a word, the path printed once, and "Copy prompt for your agent" as a ghost button, with one filled prompt for the filtered rows.
+- **One `FilePath` everywhere** (#4161). The file name is never cut, the directory shortens first, and the full path is the tooltip.
+- **Dead code is tiered after the cross-repository cut** (#4196), so `safe_only` and the summary counts agree.
+- **Workspace views** state `code_files` from one population with a real summary per repository (#4216), and five workspace error replies are clearer (#3943).
+- **`repowise reindex` turns semantic search on after a keyless init** (#4240) with a detected embedder, and every run names its embedder.
+- **The knowledge graph's layer-naming prompt** lists each layer's largest folders with file counts (#4206).
+- **Code health reads as technical debt in the UI** (#4180), and clearer labels in `risk`, dead code, `whats-new` and the generation report (#4197).
+- **Faster updates and MCP calls.** A prose-only update reuses stored clone and dead-code results, saving 17-32 s and 12-27 s (#4217), the commit-health scan per update is capped at 10 s and drains newest first (#4213), SQLite statistics refresh after each index write (#4229), health rows are replaced in one statement (#4226), and the architecture map classifies each path once (#4222). A repeated committed `get_change_risk` range is served from a per-process cache (#4209), test selection runs off the event loop and is reused per change (#4208), change health reuses parses by content (#4311), and `get_why` looks up named files in one query (#4218). Repositories open through a `Repo` that closes without a full garbage collection, about 1 s per pass on Windows (#4212).
+- **Behaviour pinned by golden snapshots** (#3970, #3971, #3972, #3974) across scanning, dead code, health, the parser, persistence order and MCP payloads, while init, update, workspace, serve, doctor, the pipeline, git indexing, health, dead code, security scanning and the MCP tools are organised into small staged modules (#3951, #3973, #3976, #3977, #3979, #3980, #3981, #3982, #3983, #3985, #3986, #3987, #3988, #3989, #3997, #3999, #4000, #4001, #4002, #4003, #4004, #4005, #4006, #4007, #4008, #4010, #4011, #4013, #4016, #4017, #4018, #4020, #4021, #4022, #4025, #4038, #4039, #4040, #4041, #4042, #4043, #4044, #4045, #4046, #4047, #4048, #4049, #4050, #4051, #4052, #4053, #4054, #4055, #4056, #4057, #4058, #4059, #4060, #4062, #4063, #4064, #4065, #4066, #4067, #4068, #4069, #4070, #4071, #4072, #4073, #4074, #4075, #4076, #4077, #4078, #4080, #4081, #4082, #4265, #4268, #4270).
+- **`HEALTH_ANALYZER_VERSION` moved from 40 to 41** with the scoring changes above, so existing indexes re-score on their next update. **`PARSER_SCHEMA_VERSION` moved from 8 to 9** (Kotlin calls chained on calls), so the parse cache refreshes once, automatically. `STORE_FORMAT_VERSION` is unchanged and nothing needs re-indexing.
+
+### Fixed
+
+- **Init and update.** `--no-prose` makes no model calls with a key set (#4239). A re-run skips the files init wrote and a fast re-init keeps the documentation (#4245). `status` and `state.json` describe the index the last command left, with "Index in progress" while init runs (#4241). Workspace init and `workspace add` stamp each repository so the first `update` has nothing to redo (#4293, #4310). `init --repos` with no names is a usage error (#4300), customize keeps `-x` excludes (#4061), `update --full` works on an index copied to a new path (#4308), `update` recounts the file-page scope every run (#4220) and retires template pages the selection drops (#4211), and a docs-mode update records its repair marker (#4026). `generate` counts model-free pages correctly in its summary (#3776).
+- **Workspace.** Repository aliases are kept and cancellation propagates (#4107), any `state.json` shape reads (#4036), errors reading saved exclude patterns are logged (#3054), and `workspace list` counts like `status` (#3984).
+- **Doctor and serve.** `doctor` exits 1 in table mode when a check fails (#4289) and runs in linked git worktrees (#1952). `serve` keeps web UI archive members inside its cache directory (#3975).
+- **Editor files.** Key modules and architecture skip structure-only preambles (#3261).
+- **Graph.** Go calls through interface-typed variables bind to the interface's method specs (#3850). A Kotlin call chained on a call is typed (#3845), Kotlin and Swift properties initialised with a constructor are typed (#3789), a Kotlin typealias leads to the class it names (#3787), and top-level Kotlin declarations with two annotations are symbols (#3839). A Python name alias reaches its real definition (#2799), Rust `cfg` build variants get their own ids (#3020), C# object-initializer locals bind (#3957), and React Native platform files resolve to import edges (#3711).
+- **Ingestion and classification.** Stored signatures and docstrings use LF line endings (#3929), `test-helpers` and `test-utils` directories are test support (#3257), and PHP production classes named `Test.php` outside a testsuite are production code (#3399).
+- **Dead code.** A Swift extension whose member name is declared elsewhere (#3876), C and C++ files listed in CMake, `.vcxproj` or `.rc` (#4121), Kotlin `@Suppress("unused")` (#3873), C# classes with custom MEF export attributes (#4009), C# cmdlets, source generators and benchmarks (#3926), Spring servlet initializers (#3921) and `@GlideModule` (#3886) are all recognised as used. A module's dead-code penalty is normalised by its symbol count (#4083).
+- **Health.** `repowise health --format json` keeps withheld finding types (#4111), the headline shows Hotspot only when a figure exists (#4295), findings stored under a renamed marker id get their advice (#4305, #4177), `.repowise/health-rules.json` applies when rescoring commits (#4179), `score_breakdown` lists defect findings only (#4178), active contributors count by canonical identity (#4086), cut-off signatures and stub bodies are declarations (#3950), and C++ condition declarations count as reads (#4122).
+- **Performance and refactoring.** A cause reached by a request, consumer or job role is entry reachable (#4234), queue rows are numbered by their place (#4233), the characterization step names the changed function and the tests that reach it (#4232), Java helper types and throws are kept (#3882), Extract Method helpers return what the caller reads (#3938), and dataflow builds try regions inside switch arms (#3694).
+- **Coverage and tests.** The recommended per-test coverage command exists (#3676), the inferred basis reads the cached test-reach walk (#4158), test selection runs only the tests that read a changed fixture file (#4267), and test-reachability reads batch their `IN` lists (#3933).
+- **Security.** Allow markers work in prose without a comment opener (#4143), a truncated digest or a cache key's md5 reads as an id (#4201), and public API in published C# projects is flagged (#3579).
+- **MCP and suspects.** Bare symbol names defined only in excluded files are gated (#4084), and suspects says when candidates reach the change index cap (#3930).
+- **Web UI.** Code Health, Overview, Commits and Owners render payloads from the previous release's server (#4304, #4306, #4303), the Overview Tests card's route and command can be set by a host (#4307), and the Why this score arithmetic names the 1.0 floor (#4132).
+- **Events, decisions and doc drift.** Tied owners at the ownership margin are ignored (#3870), a hand-recorded proposed decision reads as hand-recorded (#4015), doc-drift paths join by normalised segments (#4023), and a failing `on_error` leaves a guarded step's result intact (#4079).
+- **VS Code.** Doc drift diagnostics follow live edits (#2782).
+- **Cost.** Gemini 3 preview models are priced at their own rates (#3967).
+
+### Documentation
+
+- The quickstart has a human path and an agent path, serves first, and lists every mode with its upgrade command (#4250), and every page that teaches init says what the CLI does (#4255).
+- Change evidence, components, policy and reports in the README and docs (#3947), the README's benchmark tile matches the benchmark method (#3969), and the untested hotspot conditions and complexity README are corrected (#3449, #4169).
+
+### Dependencies
+
+- Security updates: aiohttp 3.14.4 and mcp 1.30.0 (declared floor `mcp>=1.30.0,<2`) (#4292).
+
## [0.57.0] - 2026-10-15
repowise 0.57 reads every merged change as a Change Record, rebuilt from git with an evidence checklist (owners, reaching tests, contracts, decisions crossed, provenance with coverage) and its outcomes, and the Commits page groups commits by change. On top of those records, `repowise check` evaluates a local change policy from `.repowise/policies.yaml` and writes SARIF or JUnit, `repowise report` writes assessment, change evidence and inventory packs, and `repowise suspects` ranks recent changes against a symptom with the evidence for each. Components follow the Backstage model, compare declared owners with recent activity, and export package usage as CycloneDX. AI attribution is three-state with coverage, with opt-in edit capture for Claude Code, Codex and Cursor.
diff --git a/packages/core/src/repowise/core/upgrade/_data/release_stats.json b/packages/core/src/repowise/core/upgrade/_data/release_stats.json
index a2d3b4bd0..57a7084f0 100644
--- a/packages/core/src/repowise/core/upgrade/_data/release_stats.json
+++ b/packages/core/src/repowise/core/upgrade/_data/release_stats.json
@@ -38,5 +38,25 @@
"test_files_touched": 504,
"test_files_new": 168,
"issues_closed": 53
+ },
+ "0.58.0": {
+ "since": "0.57.0",
+ "days": 5,
+ "prs": 278,
+ "contributors": 35,
+ "first_time_contributors": 19,
+ "files_changed": 1609,
+ "lines_added": 157134,
+ "lines_removed": 64952,
+ "types": {
+ "fixes": 92,
+ "features": 80,
+ "perf": 9,
+ "refactors": 79,
+ "docs": 7
+ },
+ "test_files_touched": 462,
+ "test_files_new": 181,
+ "issues_closed": 58
}
}
diff --git a/packages/core/src/repowise/core/upgrade/version.py b/packages/core/src/repowise/core/upgrade/version.py
index 9a1328795..38afe9553 100644
--- a/packages/core/src/repowise/core/upgrade/version.py
+++ b/packages/core/src/repowise/core/upgrade/version.py
@@ -89,14 +89,15 @@ STORE_FORMAT_VERSION: int = 2
#: A Dart call chained on a call (``a.b().c()``) carries that inner call too,
#: and a Dart function's signature carries its declared return type.
#: A Kotlin function's signature carries its declared return type.
-#: A Kotlin call chained on a call (``a.b().c()``) is a call site and carries
-#: that inner call.
#: Kotlin overloads and same-named extensions in one scope get their own ids
#: the Java way, an extension's receiver leading its types
#: (``toHexString#0(Byte)``, ``g#0(Int?)``), and a Kotlin trailing lambda counts as an
#: argument.
#: A Kotlin call whose only argument is a trailing lambda (``AppTheme { }``,
#: ``s.forEachSegment { }``) is a call site, with one argument.
+#:
+#: v9: a Kotlin call chained on a call (``a.b().c()``) is a call site and
+#: carries that inner call.
#: A Kotlin ``typealias`` signature carries its target (``typealias Repo =
#: DefaultRepository``), so a call through the alias reaches the repo class.
#: A top-level Kotlin declaration keeps the annotations the grammar splits off
@@ -104,7 +105,7 @@ STORE_FORMAT_VERSION: int = 2
#: A top-level Kotlin declaration with two annotations (``@Preview @Composable
#: private fun f()``) that the grammar read as an expression is re-parsed with its
#: leading annotations blanked, so it becomes a symbol again.
-PARSER_SCHEMA_VERSION: int = 8
+PARSER_SCHEMA_VERSION: int = 9
#: state.json key holding the store format version that wrote the store.
STORE_FORMAT_VERSION_KEY = "store_format_version"
diff --git a/packages/server/src/repowise/server/__init__.py b/packages/server/src/repowise/server/__init__.py
index ef72af829..eee75e796 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.57.0"
+__version__ = "0.58.0"
diff --git a/packages/vscode/CHANGELOG.md b/packages/vscode/CHANGELOG.md
index a7dd1bb7b..15c4d9dd0 100644
--- a/packages/vscode/CHANGELOG.md
+++ b/packages/vscode/CHANGELOG.md
@@ -7,6 +7,34 @@ is the minimum server version it checks against.
This file starts at 0.7.0. Earlier releases are described in the repository's
release history.
+## 0.13.0
+
+The Overview opens on what to do next, Code Health gets a zoomable folder map,
+and findings read more calmly, each with an agent prompt ready to copy.
+
+**Requires repowise 0.47.0 or newer.** The minimum has not moved; repowise
+0.58.0 fills every view in this release.
+
+### Overview
+
+- A short Overview leads with what to do, and Do next folds open on request.
+- The performance headline names the causes worth fixing now.
+
+### Code Health
+
+- A zoomable folder map with lenses, a held-out scope and a context rail.
+- Each file shows what its score lost to code shape, change history and test
+ coverage.
+- Health markers carry plain display labels; bumpy road is called repeated
+ nesting.
+- Findings cards use hairline outlines with a ghost agent prompt, and the
+ performance queue follows the same treatment.
+
+### Everywhere
+
+- File paths keep the filename visible however narrow the panel.
+- Doc drift diagnostics follow your edits as you type (#2782).
+
## 0.12.0
Every dashboard now shares one set of states, palette and controls, Code Health
diff --git a/packages/vscode/package.json b/packages/vscode/package.json
index c069384d0..974e10dba 100644
--- a/packages/vscode/package.json
+++ b/packages/vscode/package.json
@@ -2,7 +2,7 @@
"name": "repowise",
"displayName": "Repowise",
"description": "Know what your change breaks before you push. Health signals, architecture maps, and refactoring plans in your editor, and the same intelligence for your AI agent via MCP. Local and free.",
- "version": "0.12.0",
+ "version": "0.13.0",
"publisher": "repowise-dev",
"license": "AGPL-3.0-or-later",
"homepage": "https://www.repowise.dev",
diff --git a/packages/web/messages/en.json b/packages/web/messages/en.json
index 52574b42d..17cd4ff7e 100644
--- a/packages/web/messages/en.json
+++ b/packages/web/messages/en.json
@@ -532,7 +532,7 @@
"coChangeNoticeTitle": "Health scores changed in this release.",
"coChangeNoticeMore": "What changed",
"coChangeNoticeLess": "Hide",
- "coChangeNoticeBody": "Several false findings are gone: classes whose methods share no state no longer read as low cohesion, chained ternaries and conditional expressions no longer count as deep nesting, import cycles count only imports that run, and expected-exception tests and noqa lines no longer flag swallowed exceptions, so many files score higher. Functions defined inside other functions are now measured, and a test-named Python module that pytest does not collect is scored as production code, so some files score lower. PHP files now get complexity, cohesion and test-assertion checks, so PHP scores move as well.",
+ "coChangeNoticeBody": "Large, well-structured code scores fairer. A file's code-shape deductions follow a saturating curve, and several findings on one function count as one group, so a single big function no longer sinks a whole file, while a critical function still costs more the further it passes its threshold. brain_method is advisory, so it no longer deducts on top of the complexity and size findings it summarises. Repeated change-history findings count the largest in full and the rest at a fraction. Parameter counts cover C, C++ and Kotlin, so primitive_obsession reaches those languages, and the bumpy-road marker is called repeated nesting. Most files score higher; functions far past their thresholds, and C, C++ and Kotlin files, can move either way.",
"tabs": {
"performance": "Performance",
"findings": "Findings",
diff --git a/packages/web/messages/zh-CN.json b/packages/web/messages/zh-CN.json
index d89414da4..40a4ea900 100644
--- a/packages/web/messages/zh-CN.json
+++ b/packages/web/messages/zh-CN.json
@@ -532,7 +532,7 @@
"coChangeNoticeTitle": "本次发布中健康分数发生了变化。",
"coChangeNoticeMore": "有哪些变化",
"coChangeNoticeLess": "收起",
- "coChangeNoticeBody": "一些误报已被移除:方法之间不共享状态的类不再被判为低内聚,链式三元表达式和条件表达式不再计为深层嵌套,导入循环只统计实际运行的导入,预期异常的测试和带 noqa 的行不再被标记为吞掉异常,因此许多文件的分数会升高。定义在其他函数内部的函数现在也会被度量,pytest 不会收集的、以测试命名的 Python 模块会按生产代码评分,因此部分文件的分数会降低。PHP 文件现在会进行复杂度、内聚性和测试断言检查,因此 PHP 的分数也会变化。",
+ "coChangeNoticeBody": "结构良好的大型代码得分更公平。文件的代码形态扣分采用饱和曲线,同一函数上的多个发现按一组计算,因此单个大函数不会再拖垮整个文件,而严重超标的函数超出阈值越多,扣分仍然越多。brain_method 改为提示性标记,不再在其概括的复杂度和规模发现之外重复扣分。重复的变更历史发现中,最大的一项全额计入,其余按比例计入。参数计数覆盖 C、C++ 和 Kotlin,primitive_obsession 也随之适用于这些语言;bumpy-road 标记更名为 repeated nesting(重复嵌套)。大多数文件的分数会升高;远超阈值的函数以及 C、C++ 和 Kotlin 文件的分数可能升高也可能降低。",
"tabs": {
"performance": "性能",
"findings": "发现",
diff --git a/packages/web/src/app/repos/[id]/code-health/code-health-view.tsx b/packages/web/src/app/repos/[id]/code-health/code-health-view.tsx
index 7d28af38a..95750b670 100644
--- a/packages/web/src/app/repos/[id]/code-health/code-health-view.tsx
+++ b/packages/web/src/app/repos/[id]/code-health/code-health-view.tsx
@@ -385,7 +385,7 @@ export function CodeHealthView() {
release's version so a reader who dismissed an earlier one sees it. */}
<ReleaseNotice
id="health-scoring"
- version="0.56.0"
+ version="0.58.0"
detail={t("coChangeNoticeBody")}
detailLabel={t("coChangeNoticeMore")}
hideLabel={t("coChangeNoticeLess")}
diff --git a/plugins/claude-code/.claude-plugin/plugin.json b/plugins/claude-code/.claude-plugin/plugin.json
index 3ec315085..0779def5c 100644
--- a/plugins/claude-code/.claude-plugin/plugin.json
+++ b/plugins/claude-code/.claude-plugin/plugin.json
@@ -2,7 +2,7 @@
"name": "repowise",
"displayName": "Repowise",
"description": "Codebase intelligence for Claude Code. Indexes your codebase into five layers (Graph, Git, Docs, Decisions, Code Health) and exposes them through 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.57.0",
+ "version": "0.58.0",
"author": {
"name": "Repowise",
"email": "[email protected]",
diff --git a/plugins/claude-code/CHANGELOG.md b/plugins/claude-code/CHANGELOG.md
index baa21567b..f5d76a211 100644
--- a/plugins/claude-code/CHANGELOG.md
+++ b/plugins/claude-code/CHANGELOG.md
@@ -2,6 +2,20 @@
All notable changes to the Repowise Claude Code plugin are documented here.
+## 0.58.0
+
+### Changed
+- `/repowise:init` follows the CLI's plan screen: one set of mode names (Built
+ from code, Written by a model, Index only), a logged-in Claude Code, Codex or
+ OpenCode offered but never used unasked, `--repos` for a folder of repos,
+ `--progress json` for agents, and an existing `.repowise/` upgraded with
+ `repowise update --full` (#4255).
+- `/repowise:update` maps "full" to `repowise update --full`, and
+ `/repowise:reindex` names `--embedder <name>` (#4255).
+- `/repowise:search` says what to try next when a query returns nothing (#4255).
+- `/repowise:coverage` recommends a per-test coverage command that exists (#3676).
+- Lens reads the folder health map's area filter (#4135, #4157).
+
## 0.57.0
### Changed
diff --git a/pyproject.toml b/pyproject.toml
index ca9deb9ab..3aef9ee94 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "repowise"
-version = "0.57.0"
+version = "0.58.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.json
index bfbe77fc6..4cdb91cb8 100644
--- a/server.json
+++ b/server.json
@@ -8,12 +8,12 @@
"source": "github"
},
"websiteUrl": "https://www.repowise.dev",
- "version": "0.57.0",
+ "version": "0.58.0",
"packages": [
{
"registryType": "pypi",
"identifier": "repowise",
- "version": "0.57.0",
+ "version": "0.58.0",
"transport": {
"type": "stdio"
},
diff --git a/uv.lock b/uv.lock
index 900cdc0ed..533e0c87f 100644
--- a/uv.lock
+++ b/uv.lock
@@ -3156,7 +3156,7 @@ wheels = [
[[package]]
name = "repowise"
-version = "0.57.0"
+version = "0.58.0"
source = { editable = "." }
dependencies = [
{ name = "aiosqlite" },