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.57.0 · Change Records with evidence, change policy, charts in chat, models from Settings (#3885)

Raghav Chamadiyafd4f15321e7a
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index 4c4cbeb12..a476e70ac 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.56.0",
+ "version": "0.57.0",
"category": "productivity",
"keywords": [
"codebase",
diff --git a/docs/CHANGELOG.md b/docs/CHANGELOG.md
index e73a9bdca..93afddacb 100644
--- a/docs/CHANGELOG.md
+++ b/docs/CHANGELOG.md
@@ -10,35 +10,136 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
---
-## [Unreleased]
+## [0.57.0] - 2026-10-15
-Chat draws any chart of your repository, from bars and lines to donuts, treemaps and heatmaps, and every chart in the web UI shares one palette. Models and base URLs are set from Settings with live model lists, so a local server such as LM Studio is one form away, and a failed sync says what went wrong and how to fix it. Every merged change becomes a Change Record with its evidence, and the Commits page groups commits by change.
+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.
+
+Chat draws any chart of your repository in one call and checks every figure in an answer against the turn's tool results, and chat runs headless over a session API. Models and base URLs are set from Settings with live model lists, and the dashboard shows what's new after every upgrade. The server authenticates REST, MCP HTTP and webhooks to a principal with repository and tool scope, installed plugins extend named seams, and MCP routes workspace targets to the repository that owns them. Code Health serves every language, labelling the ones still in preview, and its map, file drawer and trend read clearly at any repository size. Astro is indexed at the Full tier, Gitea and Forgejo push webhooks sync, and MassTransit message contracts link C# and VB.NET services.
### Highlights
-- **Charts in chat** · Ask for any chart of your files, findings, changes, health trend, coverage, dead code, dependencies or layers, drawn as bars, lines, donuts, treemaps or heatmaps. → /repos/:id/chat
+- **Commits grouped by change** · Every merged change is a Change Record with its evidence checklist and outcomes, and the Commits page groups commits by the change that landed them. → /repos/:id/commits
+- **Change policy and evidence packs** · `repowise check` runs the rules in `.repowise/policies.yaml` against any change and writes SARIF or JUnit, and `repowise report` writes an assessment, a change evidence pack for a period or a component inventory.
+- **Charts in chat** · Ask for any chart of your files, findings, changes, health trend, coverage, dead code, dependencies or layers, and every figure in the answer is checked against the data. → /repos/:id/chat
- **Models from Settings, with live lists** · Pick a model from the provider's live list or type any id, and point repowise at LM Studio or another local OpenAI-compatible server with no key. → /settings
-- **Sync failures explain themselves** · A rejected key, rate limit, unreachable base URL or missing model shows on the sync with a short hint saying what to do. → /repos/:id/settings
-- **Commits grouped by change** · Every merged change is a Change Record with its evidence checklist, and the Commits page groups commits by the change that landed them. → /repos/:id/commits
-- **One palette for every chart** · Charts and share bars draw from the same eight series colours, and a commit type keeps its colour on every chart.
+- **Suspects for a symptom** · Paste an error, a stack trace or an issue and `repowise suspects` ranks the recent changes to read first, with the evidence for each.
### By the numbers
In the 3 days since 0.56.0:
-- **205 pull requests** merged, from **24 contributors**, **11 of them first-time contributors**
-- **1,226 files** changed, **+103,206 / -11,127** lines
-- **147 fixes, 45 features**, 4 refactors and 6 documentation changes
-- **437 test files** touched, **144** of them new
-- **25 issues** closed
+- **264 pull requests** merged, from **41 contributors**, **25 of them first-time contributors**
+- **1,421 files** changed, **+123,474 / -15,118** lines
+- **192 fixes, 51 features, 3 performance changes**, 5 refactors and 7 documentation changes
+- **504 test files** touched, **168** of them new
+- **53 issues** closed
Thank you to everyone who built this release with us.
+### Added
+
+- **Change Records, rebuilt from git on every index** (#3745). Each first-parent commit of HEAD is one change: a PR, MR, Gerrit change or lone commit, identified by its forge number, then `Change-Id`, then its sha, with ids stable across updates. A merge carries the commits its branch brought in, and a maintainer merge gives up the PR merges and squashes inside it as their own changes. Each record carries its category and three-state provenance with coverage. Served through `repowise changes list|show`, `GET /api/repos/{id}/changes` and a change page in the web UI, and `repowise changes show --format in-toto` exports an in-toto Statement v1. Forge metadata plugs in through a `ChangeMetadataSource`; the default reads `Approved-by` trailers and closing keywords from git.
+- **An evidence checklist on every Change Record** (#3791, #3814). Components touched, declared owners, suggested reviewers, reaching tests (measured or inferred), contracts and consumers in other repositories, decisions crossed, health delta, AI provenance with coverage and the diff size rank, each with a status (`ok`, `attention`, `unknown`), the basis it rests on and its source. Each row reads as a plain sentence. `repowise changes show` prints it, `repowise changes export --since --until --format json|csv` streams a window, and `get_change_risk(include=["evidence"])` and REST return the same record.
+- **Outcomes on Change Records, from explicit links only** (#3812). A record says whether a later commit reverted it, whether a later fix names it as the cause in its own words (quoted, with `Fixes: <sha>` and "regression in" style links), and how many of its files received fixes within 30 days (`changes.outcome_fix_days`). The change page has an Outcomes section, and outcomes flow into the checklist, export and assessment report.
+- **The Commits page groups commits by change, and shows events** (#3803, #3872). A History view switch offers By commit, By change and Events. By change lists each merged change with its category, commits, files, lines, provenance and an Evidence column, with Category and Needs attention filters, and each row opens the change page with its full checklist. Events lists component events newest first.
+- **`repowise check`: local change policy** (#3779). `.repowise/policies.yaml` holds Kyverno-shaped rules that match components by name, tag or criticality, with conditions on attribution and agent tier, reaching tests, contract breaks, decisions crossed and bus factor, and actions `warn`, `require_owner_review`, `require_tests` or `fail`. The security, coverage and doc-drift gates can be wrapped as rules. `repowise check [REVSPEC]` writes a table, JSON, SARIF 2.1.0 or JUnit XML (`--sarif-file` and `--junit-file` from one run), exits 1 when a `fail` rule fires, and reports a condition whose evidence is unavailable as not evaluated. The JSON carries the change's evidence for teams that feed OPA.
+- **`repowise report assessment`: an evidence pack per repository or workspace** (#3805). Components and their posture, hotspots, bus-factor exposure, dead code by tier, test reach, contracts, governing decisions, provenance coverage and a same-stamp trend, each item in OpenSSF Scorecard v2 check shape plus a `method` and `basis`. JSON is canonical, with Markdown, self-contained HTML and CSV renderers, local paths scrubbed, and missing evidence reported as unresolved rather than negative. Sections and renderers are plugin seams.
+- **`repowise report changes`: a change evidence pack for a period** (#3815, #3924). For every change merged in a window: what evidence exists that it was reviewed, tested and policy-checked, which teams are accountable, and whether it was later reverted or named by a fix, with a period summary and a method appendix that states what git cannot attest. Reviewers and individuals are counted, never named. With no `--since` it covers the 90 days before the newest indexed commit, and `--since all` reports every change.
+- **`repowise suspects` ranks recent changes against a symptom** (#3813). Give it issue text, an error message, a stack trace or a list of files, and it ranks the Change Records merged in a window by text, graph distance, co-change, recency and stack-trace signals, combined by reciprocal rank fusion, showing which signals fired for each. The output is a reading order, and the docs give a `git bisect run` recipe to confirm. Also served as `POST /api/repos/{id}/suspects`, `get_context(include=["suspects"])` and a chat tool.
+- **Components, Backstage-shaped** (#3722, #3809). Declare `Component`, `System` and `Group` entities in `.repowise/components.yaml` or `catalog-info.yaml`, with `repowise.dev/*` annotations for paths, criticality, tags and capability; with no file, components are derived from workspace services, module pages or top-level directories, with readable names past route segments. `repowise components check|list`, `get_context(targets=["component:<name>"])` with health, hotspots, bus factor, test reach and dead code rolled up, and `get_overview(include=["components"])`.
+- **Declared owners compared with recent activity** (#3781). Owners from the catalog and CODEOWNERS (GitHub, and GitLab with sections) are matched to the last 90 days of commits, raising four component findings: a high or critical component with no active owner, an owner with no recent changes on its files, a bus factor of 1 on a critical component, and a catalog entry that claims no files. `.repowise/teams.yaml` declares team membership. Served by `repowise components ownership` and `get_context(..., include=["ownership"])`, naming teams only.
+- **Package usage, component inventory and CycloneDX export** (#3806). `repowise packages where <name>` lists import sites with their component, owner teams and reachability. `repowise packages import <file>` joins a Syft, SPDX 2.x, CycloneDX or OSV file you supply to those sites, advisories first. `repowise packages export --format cyclonedx` writes CycloneDX 1.6 with `evidence.occurrences` from the import graph, and `repowise report inventory` lists components with their owners, languages, entry points and packages. Also `get_context(targets=["package:<name>"])` and a REST usage route.
+- **Component snapshots and typed events** (#3799, #3861). Every `init` and `update` stores a snapshot per component, and what moved since the previous run under the same analyzer stamp is stored as a typed event: ownership shift, owner inactive, bus factor drop, new hotspot, contract added, contract broken, decision stale, dead-code growth and test-reach drop. Events are written to `.repowise/events.jsonl` as CloudEvents 1.0.2, served by `repowise events` and `GET /api/repos/{id}/events`, and delivered through a pluggable `event-sink` seam. Each kind is switchable under `events.kinds`.
+- **Three-state AI attribution with coverage** (#3732). Commits are labelled agent, human-attested or unknown, and a commit without a marker is unknown. Every AI share is shown as the agent share of commits with a known source, with that coverage, and is withheld below 30% coverage. git-ai v3 notes are read in full, including human attestations. A new `attribution:` block (`enabled`, `capture`, `agents`) in repo and user config, where the stricter value wins, and `attribution.enabled: false` stores and shows nothing about AI. `repowise attribution status` and `repowise attribution purge`.
+- **Opt-in edit capture for Claude Code, Codex and Cursor** (#3744, #3765). With `attribution.capture: local|notes`, the agent's edit hook records the lines it wrote as content hashes in `.repowise/attribution/` (never prompts, code or identities), and `repowise update` binds them to commits by content. At `notes`, a git-ai v3 compatible note is written under `refs/notes/ai`. `--yes` and `init` never turn capture on, and `DO_NOT_TRACK` keeps it off. The integrations matrix gains an Attribution column.
+- **Attribution backfill from local agent transcripts** (#3792, #3804). `repowise attribution backfill --agent claude-code,codex` binds past commits to the edits recorded in this machine's Claude Code and Codex transcripts, keeping only line hashes and reading only what was appended since the last run. `repowise attribution status` shows coverage before and after, and the next `update` names the backfill as the reason it re-reads history.
+- **Change Records and attribution through MCP and chat** (#3784, #3790). `get_context` accepts `change:<id>` targets (or a commit sha) and `include=["changes"]` and `include=["provenance"]` on files, `get_risk(include=["changes"])` lists each file's recent changes, and `get_overview(include=["changes"])` gives changes by category and week. `repowise context --include` offers the same blocks. Default responses are unchanged.
+- **Scoped authentication for REST, MCP HTTP and webhooks** (#3725). Every authenticated surface resolves the caller to a principal with repository and tool scope. Optional scoped bearer tokens in `~/.repowise/tokens.yaml` (stored as SHA-256 hashes, with `expires_at`) can be limited to repositories and MCP tools, and the MCP streamable HTTP and SSE transports honour the same credentials, with an RFC 9728 protected-resource document. Chat runs tools as the request principal. With no key and no tokens file, every surface behaves as before.
+- **Plugins from entry points, and named seams** (#3717). An installed package extends repowise through a `repowise.plugins` entry point or `REPOWISE_PLUGINS`. Each extension point is a named seam with a local default that a plugin or `REPOWISE_SEAM_<NAME>` can switch, and `repowise plugins` shows what loaded, what failed and which implementation each seam uses. Plugin commands never replace a built-in, and a repository's `.repowise/.env` cannot select plugins.
+- **Charts in chat** (#3860, #3843, #3743, #3780, #3728, #3869, #3865). A `chart` tool draws any of eight repository datasets (files, findings, changes, health trend, coverage, dead code, dependencies, layers) in one call as bars, horizontal bars, lines, areas, donuts, treemaps, heatmaps, scatter or stacked charts. `show_view` builds tables and charts on the server from a turn's tool results, so every plotted number comes from a result, and a small spec filters, groups, aggregates and sorts any result. Each chart keeps a text summary, a Data toggle and a basis line, chats print as documents, and empty chats and each page suggest a chart that fits. Plugins add datasets and views on the `chat-dataset` and `chat-view` seams.
+- **Chat checks every figure in an answer** (#3793). Each number the answer states is looked up in that turn's tool results and views. A figure no result holds is marked with a dotted underline, a tooltip and screen-reader text, and counted in `diagnostics`; a verified figure carries the id of the result it came from.
+- **Evidence cards** (#3718). A versioned, layout-free `EvidenceCard` schema for answers, changes, components, scope, suspects and events, in which every fact says how it is known and where it came from, with a strict validator and a web renderer used by chat.
+- **Headless chat sessions** (#3746). `ChatSession` runs the chat loop without the web server, returning a structured turn result or stream events, over `POST /api/chat/sessions` and `/sessions/{id}/messages` (SSE or JSON). Each session carries a frozen policy (tool allowlist, read-only ceiling, loop cap, token budgets), sends accept an idempotency key, and long conversations are trimmed before each model call. The web chat runs on the same engine.
+- **Model and base URL from the dashboard, with live model lists** (#3849). Repo settings take a base URL with presets for local servers, Test connection, a searchable model field listing the provider's live models that also accepts any typed id, and the source of each value. An OpenAI-compatible server on this machine (LM Studio, Ollama, vLLM) needs no API key, and an unconfirmed `config.yaml` base URL offers "Trust this URL". The chat model menu loads live models too, and `/settings` holds the global default.
+- **What's new after every upgrade** (#3874). After a minor upgrade the dashboard opens What's new once, with the release summary, a By the numbers ribbon, the highlights with links into the current repository, and every change by section; a patch shows a short note. Highlighted pages carry a New mark in the navigation, the upgrade banner names the next release's top highlights, and `repowise whats-new` prints highlights and numbers with `summary`, `highlights` and `stats` in its JSON.
+- **Gitea and Forgejo push webhooks** (#3797). `POST /api/webhooks/gitea` verifies the HMAC-SHA256 signature against `REPOWISE_GITEA_WEBHOOK_SECRET` and syncs on push for both forges.
+- **MCP routes workspace targets to the repository that owns them** (#3740, #3786). In workspace mode, `get_context`, `get_symbol`, `get_risk` and `get_health` send a path or `path::Name` to the repository that has the file, `<alias>:<target>` names one outright, and an ambiguous path returns `candidates`. A bare symbol name such as `render` or `Client.send` routes to the repository that defines it, and `get_symbol` resolves an omission ref from any workspace repository, backed by a derived `.repowise-workspace/workspace.db` that is always safe to delete.
+- **`repo="all"` fans out concurrently with partial results** (#3742). `search_codebase`, `get_dead_code`, `get_why` and `get_overview` query workspace repositories concurrently with a per-repository timeout (`REPOWISE_WORKSPACE_CONCURRENCY`, `REPOWISE_WORKSPACE_REPO_TIMEOUT_S`), naming any that failed in `repos_failed` and any whose index is behind in `repos_stale` while the rest answer.
+- **Astro at the Full tier** (#3164). Frontmatter and every `<script>` body are parsed as TypeScript at their original offsets, frontmatter imports and exports become symbols and edges, PascalCase markup tags become component calls, and pages and endpoints under `src/pages` are entry points.
+- **MassTransit message contracts for C# and VB.NET** (#3070). Publishers (`Publish`, `Send`, request clients, scheduled sends, saga `Init<T>` and wrappers found by shape) and consumers (`IConsumer<T>`, fault consumers, saga events, open-generic consumers) link across workspace repositories by message type.
+- **Spring routes link to their handler methods** (#3650). Each `@GetMapping`, `@PostMapping`, `@RequestMapping` and related method gets a `framework_binds` edge, across positional, `value=` and `path=` arguments, arrays and Kotlin, and the HTTP contract dialect reads the same parser. On three Spring sample applications, route edges go from 0 to 33, all hand-checked correct.
+- **Spring Data and MyBatis calls in Java loops are flagged as database I/O** (#3615). A receiver counts only when its declared type is a Spring Data repository or MyBatis mapper; on one Spring Boot application the performance list goes from 5 to 16 rows, 10 of the 11 new rows judged real costs.
+- **Dart call receivers are typed from fields, parameters and locals** (#3610). On a public Flutter sample repository, call edges go from 979 to 1,086 with no edge lost.
+- **Swift has a complexity map** (#3450). Swift files get function rows (CCN, nesting, cognitive complexity, parameters) and class rows (methods, fields, LCOM4, TCC), and the markers derived from them.
+- **Pascal performance loops say whether they grow with the data** (#3517), including `while not Q.Eof` loops over a data set opened in place.
+- **Refactoring plans carry test commands for Go, Rust, JVM, Ruby and C#** (#3585, #3583, #3613). `go test`, `cargo test -p`, Maven and Gradle module tests, `bundle exec rspec` or `rake test`, and `dotnet test` on the owning test project or solution, stored on the plan in `validation.test_runs` alongside the JS/TS commands so batches rebuild them without a checkout.
+
### Changed
-- **Charts are in colour again, from one palette.** Every chart and share bar in the web UI draws from the same eight series colours, a commit type keeps one colour on every chart, health and risk charts keep their green, amber and red, heatmaps step through the accent orange, and chat charts sit on the conversation without a card around them.
-- **One provider order everywhere.** The CLI, `repowise serve` chat and jobs, and the MCP server now resolve provider, model and base URL as flag or UI choice, then `.repowise/config.yaml`, then the web UI's global default, then `REPOWISE_PROVIDER` / `REPOWISE_MODEL`, so `config.yaml` now wins over those env vars in the CLI. Choosing a model or base URL for a repo in the web UI writes that repo's `config.yaml`, which makes switching models on a local OpenAI-compatible server such as LM Studio a single edit. A base URL in `config.yaml` now beats `OPENAI_BASE_URL` and the other `*_BASE_URL` variables. The default provider and model saved in the web UI settings now also apply to CLI runs in repos whose `config.yaml` names none. A `config.yaml` base URL receives an API key from outside that repo's `.repowise/.env` only when it is a local address or was confirmed in Settings or with `repowise init`.
-- **Current model lists and prices.** Pickers offer GPT-6 Luna and Sol, Claude Sonnet 5.5 and Opus 5.5, Gemini 3.8 Flash and Gemini 4 Argon. DeepSeek now defaults to `deepseek-flash` and LiteLLM to `groq/openai/gpt-oss-120b`, since the old ids were retired. Cost estimates use current rates, and GPT-6 models get the same reasoning, temperature and chat tool handling as GPT-5.6.
+- **Code Health serves every language, with a Preview label where precision is still being measured** (#3867, #2921, #3877). Every finding, refactoring plan, performance cause and dead-code row is served by default; on a language whose layer measured below the precision bar, it carries a preview note with its latest hand-judged measurement (a badge with the measurement in its tooltip on the web, a `preview` field in REST, one compact `_meta.preview` entry in MCP, one line in the CLI). Health findings ship normally on Java, C# and C, each measured at 92.5% or more correct or debatable on a blind sample. Queue counts report language-held rows in a `gated` field.
+- **History markers on production files are context, not defects** (#3867, #3840). Git-history-only markers (ownership, churn and similar) leave the default defect lists and are counted under `history`, while scores, KPIs, `get_risk` and the work queue still use them. Findings on vendored and generated files and history markers on test files are held at serving, and `include=["unverified"]` shows all of them. Long parameter lists leave out parameters bound by framework annotations such as `@PathVariable`.
+- **The Code Health map, file drawer and trend read clearly at any size** (#3879). The map is drawn on canvas with zoom, pan and a Fit control, files circle-packed by folder inside each module, dots in the five score bands, and "Draw more" up to 8,000 files with vendored and generated files behind a toggle. The non-modal drawer opens on the score, one plain sentence and the top three issues with vital signs, with one primary action. The trend chart has a hover and keyboard readout and a movers list.
+- **Charts draw from one palette** (#3871). Every chart and share bar in the web UI draws from the same eight series colours, a commit type keeps one colour on every chart, health and risk charts keep their green, amber and red, heatmaps step through the accent orange, and chat charts sit on the conversation without a card around them.
+- **One provider order everywhere** (#3847). The CLI, `repowise serve` chat and jobs, and the MCP server resolve provider, model and base URL as flag or UI choice, then `.repowise/config.yaml`, then the web UI's global default, then `REPOWISE_PROVIDER` / `REPOWISE_MODEL`, so `config.yaml` takes precedence over those env vars in the CLI. Choosing a model or base URL for a repo in the web UI writes that repo's `config.yaml`, which makes switching models on a local OpenAI-compatible server such as LM Studio a single edit. A base URL in `config.yaml` takes precedence over `OPENAI_BASE_URL` and the other `*_BASE_URL` variables. The default provider and model saved in the web UI settings also apply to CLI runs in repos whose `config.yaml` names none. A `config.yaml` base URL receives an API key from outside that repo's `.repowise/.env` only when it is a local address or was confirmed in Settings or with `repowise init`.
+- **Current model lists and prices** (#3868). Pickers offer GPT-6 Luna and Sol, Claude Sonnet 5.5 and Opus 5.5, Gemini 3.8 Flash and Gemini 4 Argon. DeepSeek defaults to `deepseek-flash` and LiteLLM to `groq/openai/gpt-oss-120b`, matching what those providers serve today. Cost estimates use current rates, and GPT-6 models get the same reasoning, temperature and chat tool handling as GPT-5.6.
+- **Sync shows its progress and explains a failure** (#3838). Sync and full re-index from the dashboard show progress, and a failed or partial run stays on screen with the reason (a rejected key, rate limit, unreachable base URL or missing model) and Retry, Provider settings and Dismiss actions.
+- **Git history reads the newest 5,000 commits by default** (#3833), up from 500, so churn, hotspots, co-change, Change Records, suspects and 90-day counts cover a real span of history on active repositories. The co-change window follows it. An existing index keeps the `commit_limit` its `config.yaml` records (`init` wrote 500 before 0.57), and `update` names that value once; set `commit_limit: 5000` there to read the wider window.
+- **AI shares are reported with coverage** (#3732). `/commits/agent-trend` returns per-label counts, `coverage_pct` and `agent_pct_of_covered` in place of `agent_pct`, the authorship filter gains `unknown` and `human` means human-attested, `get_context` ownership carries one `agent_share` summary in place of `agent_authored_pct`, and AI figures are reported per file, component and repository.
+- **Extract Method plans leave the helper's name to whoever applies them** (#3588). The header, call and stage chaining use a placeholder (`_extracted_helper`, `extractedHelper`, numbered for later stages) with one note to rename it. Judged blind on 107 real refactorings from 19 repositories, names chosen by the applying agent were accepted about 74% of the time. Plan ids are unchanged.
+- **Fix first orders by the function's own change history** (#3565). Inside a value band, items are weighted by how many commits changed the lead function, and the reason names that history ("function changed in 38 commits").
+- **Fix first leads with the stored plan its first step lifts** (#3582, #3662), titled "Split X into N helpers" with "(more stages needed)" when the plan alone leaves the function above the break-up bar, and the dashboard card opens that plan. A Break up reason says what the split buys (#3581).
+- **Change risk leads with the size percentile** (#3664). `repowise risk`, the CI markdown and `get_change_risk` open with "Size and spread: Nth percentile of recent commits (diff size, not a bug predictor)", then the touched files' bug-fix record. The plugin's risk command and change review skill follow the new wording.
+- **`get_answer` grades `confidence` on whether the top hit covers the question** (#3716). `retrieval_quality` moves behind `include=["diagnostics"]`.
+- **Repository health headlines state their sample** (#3641, #3653). A band such as "Excellent" is printed only when at least half of the code files were analysed, each headline says "analysed N of M code files" when some were left out, and every surface names the same worst file and worst test as `get_health`.
+- **The dead code tab leads with what is safe to delete** (#3884), with the flagged count as a secondary sentence and `safe_to_delete_count` on the summary endpoint.
+- **Change risk and suspects answer faster on a running server** (#3925, #3927, #3928). A `get_change_risk` finding drill-down returns in under a second (about 5 s before), test selection reuses its per-file parsing across calls (`get_change_risk` and `get_risk` PR mode about 25% faster), and suspects reads each change's git text once per server (a warm call drops from about 6 s to under 1 s).
+- **Bug-fix commits are recognised in more forms** (#3567). `Fixed`, `Fixes`, `Fixing`, `hotfix`, `bugfix` and `Fixes #N` count as bug fixes.
+
+### Fixed
+
+- **Change Records, events and components.** The reaching-tests checklist item asks for a look only on a measured absence, and partly-known items carry counts (#3814). Component snapshots are taken on repositories with git owners (#3808), contract events are measured after the cross-repository pass extracts contracts (#3861), and derived components with colliding names are qualified by their parent (#3809).
+- **Chat.** Charts and tables cite results from earlier turns, and setup or provider failures end as a readable chat error (#3834). A chart field that plays two roles draws one column (#3865), a new conversation keeps a bare URL (#3576), and taps pass through the hidden conversation row toolbar (#3764).
+- **Graph, Java.** Same-arity overloads, enum-constant methods, anonymous-class methods and `@interface` elements get their own nodes (#3616, #3624, #3670). Overloads are chosen by literal argument types, arity against inherited overloads and the declared types of named arguments, and a tie never lands on an overload that cannot take the call (#3672, #3704, #3625). Call chains, inherited fields, `super` and cast receivers are typed, `S.super.m()` resolves, a member type shadows a same-named import, and the same-package tier offers only the right class's method (#3623, #3671, #3669, #3620).
+- **Graph, Kotlin.** Overloads and same-named extensions get their own ids, and calls whose only argument is a trailing lambda are call sites, including a local assigned from one (#3766, #3783, #3785). Extension calls resolve on a typed receiver and only with the receiver in scope, operator `invoke` binds, multiplatform calls bind only to declarations their source set sees, alias imports bind by alias, and imports of top-level functions and properties resolve (#3707, #3681, #3733, #3831, #3607, #3407, #3737). Constructor properties type receivers, parameters shadow a bare call, and a property is never a bare call's callee (#3609, #3679, #3680).
+- **Graph, Swift, Dart and Python.** Kotlin, Swift and Dart locals are typed from the call that assigns them (#3734). Swift stored properties type receivers, a Swift extension is not a constructible class, a subscript read is not a call, and optional-binding call assignments resolve (#3609, #3619, #3618, #3768). Dart named constructors bind, chained calls are typed by return type, and chains of three or more links resolve (#3701, #3794). Python receivers are typed through properties and returned objects, literal lazy exports are recognised, and test paths anchored at `Path(__file__)` ancestors resolve (#3666, #3570, #3518).
+- **Graph, general.** A module-alias call resolves to the module's top-level name only (#3617), name-only call tiers stay inside the caller's build (#3682), and C++ project export macros are discovered in headers beside target sources (#3706).
+- **Ingestion.** Every module of a Groovy `settings.gradle` include is read and relative Gradle module paths resolve (#3626, #3587). `!` negation rules re-include pruned directories (#3563), Unity state directories are skipped only inside a Unity project (#3866), and C# files in test projects are test material (#3586). Shallow-clone boundary lines are left out of blame ownership (#3073), and suggested reviewers are weighted by each author's own recent commits (#3074).
+- **Code origin.** Dart SDK headers under `dart-sdk/` are vendored, SwiftPM version-specific manifests are build files, Visual C++ resource headers and Dart codegen, minified and webpack output are generated (#3652, #3841, #3842, #3637).
+- **Health metrics.** Declared parameters are counted consistently across languages (#3848), a try block is not a nesting level (#3648), anonymous-class members roll up to their named owner (#3643), C# type arguments stay out of callee names (#3475), and the catch variable is a def in the Java, C# and C++ dataflow dialects (#3483). AVA's `t.*` assertions count in JS/TS tests (#3674).
+- **Health findings.** `ownership_risk` says which rule fired, files under 40 code lines are capped at low, and test-file findings rank after production ones (#3656). A flat boolean chain holds at low in `complex_conditional` (#3665), `developer_congestion` requires recent commits (#3675), sweep commits and inheritance stay out of hidden coupling (#3686), a keyed loop call clears `key_unused` for its line (#3539), and a C# `using` declaration stays with the code it guards (#3463).
+- **Health surfaces.** A repository with no hotspot files reports hotspot health as null in the trend, snapshots and an empty history, and the trend view says so (#3684, #3705, #3713). `get_health` file rows account for every point their score lost, `gap_analysis` agrees with the gap, and plan steps carry no stray `\r` (#3683). Queue counts count a language-held unit once (#3667), every performance finding states its queue reason (#3612), and example-named packages with a production origin stay in Fix first (#3629). Fix first item detail stays about the item itself (#3693), and `--refactoring-targets --recompute` plans carry their findings (#3521).
+- **Refactoring and dataflow.** Extract Method never plans a span over match arms and binds pattern captures (#3782). A write that may not run does not cover a later read (#3589), a write in a TypeScript, Go or Python switch arm is a may-def (#3522), a grouped Go `var` declares its names and taking a Go variable's address is a write (#3472, #3474), and Rust `use` declarations are not variable reads (#3575). Performance rows that are the recommended idiom or stated intent are dropped (#3611).
+- **Dead code.** C# classes found by assembly scanning or MEF, Swift cross-file uses and Java classes named in resources are reachable (#3832). Kotlin operator functions are contract methods, Compose previews and Dagger/Hilt modules are framework-loaded, Gradle and Android convention plugins, test modules and manifests are entry roots, and a module with a program `main` is run (#3695, #3661, #3657, #3645). A co-change edge is not an importer in JVM, Go and C++ reachability (#3658), generated files read as unindexed users (#3639), packages that import their own directory are linked (#3884), and empty safe-only views and withheld `unused_internal` rows say why (#3646, #3668).
+- **Security.** History findings are deduplicated across file versions (#3631), the repository's `.gitleaks.toml` path allowlist is honoured (#3709), other scanners' inline allow markers are honoured, generated, vendored and `.d.ts` files are scanned for secrets only, and sinks in scripts, tools and docs examples are low (#3685). Uppercase identifier values and `__html` type keywords in type positions stay quiet (#3420, #3687).
+- **Public API.** Exported Go identifiers outside `internal` packages and Java and Kotlin public API in published modules are flagged (#3537, #3577).
+- **Change risk.** Repowise's own output stays out of working-tree change risk and test selection, untracked files count the same everywhere, and text templates are data (#3712, #3770, #3767). Every per-file block is scoped to `include_paths`, given as a list or a string (#3730, #3698), the indexed commit is read through one resolver (#3708), the health delta matches findings by identity across renames, line shifts and centrality changes (#3715), the overlap block counts only fixes before the change (#3632), MCP says which checkout and commit it read (#3719), and a missing `git` is named (#3659).
+- **Test selection.** A conftest reading a literal constant or calling a self-contained function reaches only its module, and type-only conftest imports are ignored (#3731, #3772, #3633). A comment or docstring mention does not name a file (#3720), prose suffixes follow the documented extensions (#3729), tests reached through a package barrel are seen (#3651), `@SpringBootTest` integration tests run with every selection (#3636), only the base side of the index gap counts (#3628), and a second call shares a running selection (#3727).
+- **Coverage.** Files changed since a stale coverage report carry no figures (#3735), and any unapplied gate gives way to the project verdict (#3519).
+- **MCP.** Freshness and live files are read from the served checkout (#3644). Caller definition lines are checked live and symbol search folds plurals (#3741), reference edit sets are complete for Go, Java and Kotlin packages (#3642), `Class.method` and `Class::method` targets resolve with no file (#3635), a missed `get_context` target names the nearest symbols (#3638), tree-sitter query and history-tier files are classed as what they are (#3723), `used_by` and search notes agree with their payload (#3699), and `get_risk` states its churn rank as a rank (#3560).
+- **`get_answer` and search.** Retrieval reaches function bodies by rare terms and literals, a class's constructors count as part of the class, a project-name word or directory name carries no extra weight, and a body named only as context is served as evidence (#3736, #3773, #3771). A value is extracted only for the constant the question names, and each file appears once in `best_guesses` (#3700, #3673). Hybrid search scores symbols on content words, and code-punctuation literals are scanned and kept out of path mode (#3677, #3721).
+- **`get_why`.** A target is governed only by exact scope with the reason worded from its basis, rationale comments rank by weighted coverage, commits are deduplicated by full sha, `git_log` is capped at five, and an index with no accepted decisions or a missing path says so (#3769, #3724, #3726, #3655, #3654).
+- **CLI.** `repowise risk` reports git's message for an unknown ref (#3622), `repowise why` prints each history commit once (#3608), `repowise doctor` notes a Claude Code MCP entry that serves another repository (#3649), a keyless index reads as complete and init, status and `get_answer` name the keyless upgrade commands (#3634, #3143), and `generate --unwritten` seeds from model-written pages only (#3811).
+- **Distill.** Verbose `go test` runs keep their failure messages (#3627), and `git log -n` is honoured with each commit's author (#3660).
+- **Providers and integrations.** The default Ollama embedding timeout scales with the batch size (#3578), and OpenCode CLI v2 is supported (#3572).
+- **Decisions.** `superseded_by` is validated against the repository's own decisions (#3748).
+- **Web UI.** The docs Export menu opens above the header (#3778), MetricCard labels and descriptions render as blocks (#3875), UI copy uses correct singulars, ordinals and field names (#3465), charts share one median helper and one effort label map (#3561), and UI components fill in summaries and states when a host omits them (#3566).
+- **Upgrades.** The chat sessions migration is chained after Change Records (#3763), REST responses carry `preview` only on preview cells (#3877), and one shared `git cat-file --batch` reader serves every analysis consumer (#3702).
+- **Release-day hardening.** Suspects runs its git reads off the MCP stdin pipe, so it answers promptly on every platform (#3888), and `get_change_risk` accepts only revisions, never git options (#3893). An oversized omission ref reads through page by page (#3899), the MCP handshake reports the repowise version (#3900), `get_overview` names unknown `include` values in `ignored_arguments` (#3916), and dead-code cross-repo notes list each consuming repository once (#3895).
+- **Index accuracy.** A symbol spotlight retires when its symbol leaves a live file (#3892), test-quality markers read the stamped test flag (#3898), replayed function hotspots are re-measured on upgrade (#3891), update keeps non-code co-change partners such as templates and stylesheets (#3896), git-ignored manifests stay out of package discovery (#3894), and src-layout packages are service boundaries (#3897).
+- **CLI.** `repowise changes show` accepts the forge ref `changes list` prints (#3904), `status` sync totals agree with the pages table (#3889), `doctor` leaves tombstoned pages out of store reconciliation (#3907), distill runs a forward-slash program path on Windows (#3918), and SyntaxWarnings from analysed Python stay off the console (#3890).
+- Internal: the contract-facts refresh and the C# and Swift dead-code passes are split into helpers, and unused code is removed (#3863, #3846, #3538, #3883, #3417, #3339, #3795, #3774, #3696).
+
+### Documentation
+
+- Layer pages for AI attribution and Change Records (#3775), and every layer page rewritten as a scannable present-tense guide with method detail in the architecture docs (#3777).
+- The benchmarks page is rewritten for readers new to repowise, with October scores (#3640).
+- Language support lists class metrics for Dart, F# and Objective-C (#3479), and the architecture docs say semantic search uses LanceDB on every SQL backend (#3155).
+
+### Dependencies
+
+- Core: `tree-sitter-swift` pinned to `>=0.7.4,<0.8` (#3647).
+- Web: the unused `recharts` 2 dependency is removed; charts use recharts 3 from the UI package (#3780).
+- Security updates: fsspec 2026.9.0, Mako 1.4.3, multidict 6.9.1, source-map-js 1.2.2, postcss-selector-parser 7.1.6 and KaTeX 0.18.4 (#3887).
## [0.56.0] - 2026-10-12
diff --git a/docs/reference/CLI_REFERENCE.md b/docs/reference/CLI_REFERENCE.md
index 1d41b7cea..a098cc6c2 100644
--- a/docs/reference/CLI_REFERENCE.md
+++ b/docs/reference/CLI_REFERENCE.md
@@ -1658,7 +1658,7 @@ repowise events [--path PATH] [--since 7d|12h|ISO-DATE] [--kind KIND]... [--limi
Kinds: `ownership_shift`, `owner_inactive`, `bus_factor_drop` (critical components), `new_hotspot` (off by default), `contract_added`, `contract_broken`, `decision_stale`, `dead_code_growth`, `test_reach_drop`. Contract kinds need a workspace: after the cross-repo pass extracts contracts at the run's commit, the run's contract facts are measured and its contract events stored; outside a workspace contracts stay unavailable and those kinds never fire. An index-only `update` (the post-commit hook) skips the cross-repo pass to stay fast, so its run keeps contracts unavailable; contract kinds compare each measured run with the last earlier run that measured them, passing over those runs. Known limit: consumer counts are read at the provider's own runs, so a change in a consumer repo alone moves no contract event. Known limit: past `compact_after_days` compaction keeps one run per week, so the measured run a later run would compare with can be dropped, and the comparison falls back to an older measured run or none. The `events:` block in `.repowise/config.yaml` sets `enabled`, `retention_days` (365), `compact_after_days` (30; older runs keep one per week), per-kind switches under `kinds`, and the `sinks` to deliver to (`jsonl` by default, `stdout` for CI).
-The web UI lists the same events on the repository's Events page, newest first. An empty list says why: `GET /api/repos/{id}/events` returns `snapshot_runs` and `empty_reason` (`baseline_only` until two snapshots exist, `nothing_moved`, or `no_match` under filters), and the same sentence this command prints as `empty_note`.
+The web UI lists the same events in the Events view of the Commits page, newest first. An empty list says why: `GET /api/repos/{id}/events` returns `snapshot_runs` and `empty_reason` (`baseline_only` until two snapshots exist, `nothing_moved`, or `no_match` under filters), and the same sentence this command prints as `empty_note`.
---
diff --git a/package-lock.json b/package-lock.json
index 4ba4018d7..da4f5d1f3 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -19360,7 +19360,7 @@
},
"packages/vscode": {
"name": "repowise",
- "version": "0.11.0",
+ "version": "0.12.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 7507484f9..fa2e2a755 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.56.0"
+__version__ = "0.57.0"
diff --git a/packages/core/src/repowise/core/__init__.py b/packages/core/src/repowise/core/__init__.py
index 801c3ad5d..d95e45d70 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.56.0"
+__version__ = "0.57.0"
diff --git a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
index e73a9bdca..93afddacb 100644
--- a/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
+++ b/packages/core/src/repowise/core/upgrade/_data/CHANGELOG.md
@@ -10,35 +10,136 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
---
-## [Unreleased]
+## [0.57.0] - 2026-10-15
-Chat draws any chart of your repository, from bars and lines to donuts, treemaps and heatmaps, and every chart in the web UI shares one palette. Models and base URLs are set from Settings with live model lists, so a local server such as LM Studio is one form away, and a failed sync says what went wrong and how to fix it. Every merged change becomes a Change Record with its evidence, and the Commits page groups commits by change.
+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.
+
+Chat draws any chart of your repository in one call and checks every figure in an answer against the turn's tool results, and chat runs headless over a session API. Models and base URLs are set from Settings with live model lists, and the dashboard shows what's new after every upgrade. The server authenticates REST, MCP HTTP and webhooks to a principal with repository and tool scope, installed plugins extend named seams, and MCP routes workspace targets to the repository that owns them. Code Health serves every language, labelling the ones still in preview, and its map, file drawer and trend read clearly at any repository size. Astro is indexed at the Full tier, Gitea and Forgejo push webhooks sync, and MassTransit message contracts link C# and VB.NET services.
### Highlights
-- **Charts in chat** · Ask for any chart of your files, findings, changes, health trend, coverage, dead code, dependencies or layers, drawn as bars, lines, donuts, treemaps or heatmaps. → /repos/:id/chat
+- **Commits grouped by change** · Every merged change is a Change Record with its evidence checklist and outcomes, and the Commits page groups commits by the change that landed them. → /repos/:id/commits
+- **Change policy and evidence packs** · `repowise check` runs the rules in `.repowise/policies.yaml` against any change and writes SARIF or JUnit, and `repowise report` writes an assessment, a change evidence pack for a period or a component inventory.
+- **Charts in chat** · Ask for any chart of your files, findings, changes, health trend, coverage, dead code, dependencies or layers, and every figure in the answer is checked against the data. → /repos/:id/chat
- **Models from Settings, with live lists** · Pick a model from the provider's live list or type any id, and point repowise at LM Studio or another local OpenAI-compatible server with no key. → /settings
-- **Sync failures explain themselves** · A rejected key, rate limit, unreachable base URL or missing model shows on the sync with a short hint saying what to do. → /repos/:id/settings
-- **Commits grouped by change** · Every merged change is a Change Record with its evidence checklist, and the Commits page groups commits by the change that landed them. → /repos/:id/commits
-- **One palette for every chart** · Charts and share bars draw from the same eight series colours, and a commit type keeps its colour on every chart.
+- **Suspects for a symptom** · Paste an error, a stack trace or an issue and `repowise suspects` ranks the recent changes to read first, with the evidence for each.
### By the numbers
In the 3 days since 0.56.0:
-- **205 pull requests** merged, from **24 contributors**, **11 of them first-time contributors**
-- **1,226 files** changed, **+103,206 / -11,127** lines
-- **147 fixes, 45 features**, 4 refactors and 6 documentation changes
-- **437 test files** touched, **144** of them new
-- **25 issues** closed
+- **264 pull requests** merged, from **41 contributors**, **25 of them first-time contributors**
+- **1,421 files** changed, **+123,474 / -15,118** lines
+- **192 fixes, 51 features, 3 performance changes**, 5 refactors and 7 documentation changes
+- **504 test files** touched, **168** of them new
+- **53 issues** closed
Thank you to everyone who built this release with us.
+### Added
+
+- **Change Records, rebuilt from git on every index** (#3745). Each first-parent commit of HEAD is one change: a PR, MR, Gerrit change or lone commit, identified by its forge number, then `Change-Id`, then its sha, with ids stable across updates. A merge carries the commits its branch brought in, and a maintainer merge gives up the PR merges and squashes inside it as their own changes. Each record carries its category and three-state provenance with coverage. Served through `repowise changes list|show`, `GET /api/repos/{id}/changes` and a change page in the web UI, and `repowise changes show --format in-toto` exports an in-toto Statement v1. Forge metadata plugs in through a `ChangeMetadataSource`; the default reads `Approved-by` trailers and closing keywords from git.
+- **An evidence checklist on every Change Record** (#3791, #3814). Components touched, declared owners, suggested reviewers, reaching tests (measured or inferred), contracts and consumers in other repositories, decisions crossed, health delta, AI provenance with coverage and the diff size rank, each with a status (`ok`, `attention`, `unknown`), the basis it rests on and its source. Each row reads as a plain sentence. `repowise changes show` prints it, `repowise changes export --since --until --format json|csv` streams a window, and `get_change_risk(include=["evidence"])` and REST return the same record.
+- **Outcomes on Change Records, from explicit links only** (#3812). A record says whether a later commit reverted it, whether a later fix names it as the cause in its own words (quoted, with `Fixes: <sha>` and "regression in" style links), and how many of its files received fixes within 30 days (`changes.outcome_fix_days`). The change page has an Outcomes section, and outcomes flow into the checklist, export and assessment report.
+- **The Commits page groups commits by change, and shows events** (#3803, #3872). A History view switch offers By commit, By change and Events. By change lists each merged change with its category, commits, files, lines, provenance and an Evidence column, with Category and Needs attention filters, and each row opens the change page with its full checklist. Events lists component events newest first.
+- **`repowise check`: local change policy** (#3779). `.repowise/policies.yaml` holds Kyverno-shaped rules that match components by name, tag or criticality, with conditions on attribution and agent tier, reaching tests, contract breaks, decisions crossed and bus factor, and actions `warn`, `require_owner_review`, `require_tests` or `fail`. The security, coverage and doc-drift gates can be wrapped as rules. `repowise check [REVSPEC]` writes a table, JSON, SARIF 2.1.0 or JUnit XML (`--sarif-file` and `--junit-file` from one run), exits 1 when a `fail` rule fires, and reports a condition whose evidence is unavailable as not evaluated. The JSON carries the change's evidence for teams that feed OPA.
+- **`repowise report assessment`: an evidence pack per repository or workspace** (#3805). Components and their posture, hotspots, bus-factor exposure, dead code by tier, test reach, contracts, governing decisions, provenance coverage and a same-stamp trend, each item in OpenSSF Scorecard v2 check shape plus a `method` and `basis`. JSON is canonical, with Markdown, self-contained HTML and CSV renderers, local paths scrubbed, and missing evidence reported as unresolved rather than negative. Sections and renderers are plugin seams.
+- **`repowise report changes`: a change evidence pack for a period** (#3815, #3924). For every change merged in a window: what evidence exists that it was reviewed, tested and policy-checked, which teams are accountable, and whether it was later reverted or named by a fix, with a period summary and a method appendix that states what git cannot attest. Reviewers and individuals are counted, never named. With no `--since` it covers the 90 days before the newest indexed commit, and `--since all` reports every change.
+- **`repowise suspects` ranks recent changes against a symptom** (#3813). Give it issue text, an error message, a stack trace or a list of files, and it ranks the Change Records merged in a window by text, graph distance, co-change, recency and stack-trace signals, combined by reciprocal rank fusion, showing which signals fired for each. The output is a reading order, and the docs give a `git bisect run` recipe to confirm. Also served as `POST /api/repos/{id}/suspects`, `get_context(include=["suspects"])` and a chat tool.
+- **Components, Backstage-shaped** (#3722, #3809). Declare `Component`, `System` and `Group` entities in `.repowise/components.yaml` or `catalog-info.yaml`, with `repowise.dev/*` annotations for paths, criticality, tags and capability; with no file, components are derived from workspace services, module pages or top-level directories, with readable names past route segments. `repowise components check|list`, `get_context(targets=["component:<name>"])` with health, hotspots, bus factor, test reach and dead code rolled up, and `get_overview(include=["components"])`.
+- **Declared owners compared with recent activity** (#3781). Owners from the catalog and CODEOWNERS (GitHub, and GitLab with sections) are matched to the last 90 days of commits, raising four component findings: a high or critical component with no active owner, an owner with no recent changes on its files, a bus factor of 1 on a critical component, and a catalog entry that claims no files. `.repowise/teams.yaml` declares team membership. Served by `repowise components ownership` and `get_context(..., include=["ownership"])`, naming teams only.
+- **Package usage, component inventory and CycloneDX export** (#3806). `repowise packages where <name>` lists import sites with their component, owner teams and reachability. `repowise packages import <file>` joins a Syft, SPDX 2.x, CycloneDX or OSV file you supply to those sites, advisories first. `repowise packages export --format cyclonedx` writes CycloneDX 1.6 with `evidence.occurrences` from the import graph, and `repowise report inventory` lists components with their owners, languages, entry points and packages. Also `get_context(targets=["package:<name>"])` and a REST usage route.
+- **Component snapshots and typed events** (#3799, #3861). Every `init` and `update` stores a snapshot per component, and what moved since the previous run under the same analyzer stamp is stored as a typed event: ownership shift, owner inactive, bus factor drop, new hotspot, contract added, contract broken, decision stale, dead-code growth and test-reach drop. Events are written to `.repowise/events.jsonl` as CloudEvents 1.0.2, served by `repowise events` and `GET /api/repos/{id}/events`, and delivered through a pluggable `event-sink` seam. Each kind is switchable under `events.kinds`.
+- **Three-state AI attribution with coverage** (#3732). Commits are labelled agent, human-attested or unknown, and a commit without a marker is unknown. Every AI share is shown as the agent share of commits with a known source, with that coverage, and is withheld below 30% coverage. git-ai v3 notes are read in full, including human attestations. A new `attribution:` block (`enabled`, `capture`, `agents`) in repo and user config, where the stricter value wins, and `attribution.enabled: false` stores and shows nothing about AI. `repowise attribution status` and `repowise attribution purge`.
+- **Opt-in edit capture for Claude Code, Codex and Cursor** (#3744, #3765). With `attribution.capture: local|notes`, the agent's edit hook records the lines it wrote as content hashes in `.repowise/attribution/` (never prompts, code or identities), and `repowise update` binds them to commits by content. At `notes`, a git-ai v3 compatible note is written under `refs/notes/ai`. `--yes` and `init` never turn capture on, and `DO_NOT_TRACK` keeps it off. The integrations matrix gains an Attribution column.
+- **Attribution backfill from local agent transcripts** (#3792, #3804). `repowise attribution backfill --agent claude-code,codex` binds past commits to the edits recorded in this machine's Claude Code and Codex transcripts, keeping only line hashes and reading only what was appended since the last run. `repowise attribution status` shows coverage before and after, and the next `update` names the backfill as the reason it re-reads history.
+- **Change Records and attribution through MCP and chat** (#3784, #3790). `get_context` accepts `change:<id>` targets (or a commit sha) and `include=["changes"]` and `include=["provenance"]` on files, `get_risk(include=["changes"])` lists each file's recent changes, and `get_overview(include=["changes"])` gives changes by category and week. `repowise context --include` offers the same blocks. Default responses are unchanged.
+- **Scoped authentication for REST, MCP HTTP and webhooks** (#3725). Every authenticated surface resolves the caller to a principal with repository and tool scope. Optional scoped bearer tokens in `~/.repowise/tokens.yaml` (stored as SHA-256 hashes, with `expires_at`) can be limited to repositories and MCP tools, and the MCP streamable HTTP and SSE transports honour the same credentials, with an RFC 9728 protected-resource document. Chat runs tools as the request principal. With no key and no tokens file, every surface behaves as before.
+- **Plugins from entry points, and named seams** (#3717). An installed package extends repowise through a `repowise.plugins` entry point or `REPOWISE_PLUGINS`. Each extension point is a named seam with a local default that a plugin or `REPOWISE_SEAM_<NAME>` can switch, and `repowise plugins` shows what loaded, what failed and which implementation each seam uses. Plugin commands never replace a built-in, and a repository's `.repowise/.env` cannot select plugins.
+- **Charts in chat** (#3860, #3843, #3743, #3780, #3728, #3869, #3865). A `chart` tool draws any of eight repository datasets (files, findings, changes, health trend, coverage, dead code, dependencies, layers) in one call as bars, horizontal bars, lines, areas, donuts, treemaps, heatmaps, scatter or stacked charts. `show_view` builds tables and charts on the server from a turn's tool results, so every plotted number comes from a result, and a small spec filters, groups, aggregates and sorts any result. Each chart keeps a text summary, a Data toggle and a basis line, chats print as documents, and empty chats and each page suggest a chart that fits. Plugins add datasets and views on the `chat-dataset` and `chat-view` seams.
+- **Chat checks every figure in an answer** (#3793). Each number the answer states is looked up in that turn's tool results and views. A figure no result holds is marked with a dotted underline, a tooltip and screen-reader text, and counted in `diagnostics`; a verified figure carries the id of the result it came from.
+- **Evidence cards** (#3718). A versioned, layout-free `EvidenceCard` schema for answers, changes, components, scope, suspects and events, in which every fact says how it is known and where it came from, with a strict validator and a web renderer used by chat.
+- **Headless chat sessions** (#3746). `ChatSession` runs the chat loop without the web server, returning a structured turn result or stream events, over `POST /api/chat/sessions` and `/sessions/{id}/messages` (SSE or JSON). Each session carries a frozen policy (tool allowlist, read-only ceiling, loop cap, token budgets), sends accept an idempotency key, and long conversations are trimmed before each model call. The web chat runs on the same engine.
+- **Model and base URL from the dashboard, with live model lists** (#3849). Repo settings take a base URL with presets for local servers, Test connection, a searchable model field listing the provider's live models that also accepts any typed id, and the source of each value. An OpenAI-compatible server on this machine (LM Studio, Ollama, vLLM) needs no API key, and an unconfirmed `config.yaml` base URL offers "Trust this URL". The chat model menu loads live models too, and `/settings` holds the global default.
+- **What's new after every upgrade** (#3874). After a minor upgrade the dashboard opens What's new once, with the release summary, a By the numbers ribbon, the highlights with links into the current repository, and every change by section; a patch shows a short note. Highlighted pages carry a New mark in the navigation, the upgrade banner names the next release's top highlights, and `repowise whats-new` prints highlights and numbers with `summary`, `highlights` and `stats` in its JSON.
+- **Gitea and Forgejo push webhooks** (#3797). `POST /api/webhooks/gitea` verifies the HMAC-SHA256 signature against `REPOWISE_GITEA_WEBHOOK_SECRET` and syncs on push for both forges.
+- **MCP routes workspace targets to the repository that owns them** (#3740, #3786). In workspace mode, `get_context`, `get_symbol`, `get_risk` and `get_health` send a path or `path::Name` to the repository that has the file, `<alias>:<target>` names one outright, and an ambiguous path returns `candidates`. A bare symbol name such as `render` or `Client.send` routes to the repository that defines it, and `get_symbol` resolves an omission ref from any workspace repository, backed by a derived `.repowise-workspace/workspace.db` that is always safe to delete.
+- **`repo="all"` fans out concurrently with partial results** (#3742). `search_codebase`, `get_dead_code`, `get_why` and `get_overview` query workspace repositories concurrently with a per-repository timeout (`REPOWISE_WORKSPACE_CONCURRENCY`, `REPOWISE_WORKSPACE_REPO_TIMEOUT_S`), naming any that failed in `repos_failed` and any whose index is behind in `repos_stale` while the rest answer.
+- **Astro at the Full tier** (#3164). Frontmatter and every `<script>` body are parsed as TypeScript at their original offsets, frontmatter imports and exports become symbols and edges, PascalCase markup tags become component calls, and pages and endpoints under `src/pages` are entry points.
+- **MassTransit message contracts for C# and VB.NET** (#3070). Publishers (`Publish`, `Send`, request clients, scheduled sends, saga `Init<T>` and wrappers found by shape) and consumers (`IConsumer<T>`, fault consumers, saga events, open-generic consumers) link across workspace repositories by message type.
+- **Spring routes link to their handler methods** (#3650). Each `@GetMapping`, `@PostMapping`, `@RequestMapping` and related method gets a `framework_binds` edge, across positional, `value=` and `path=` arguments, arrays and Kotlin, and the HTTP contract dialect reads the same parser. On three Spring sample applications, route edges go from 0 to 33, all hand-checked correct.
+- **Spring Data and MyBatis calls in Java loops are flagged as database I/O** (#3615). A receiver counts only when its declared type is a Spring Data repository or MyBatis mapper; on one Spring Boot application the performance list goes from 5 to 16 rows, 10 of the 11 new rows judged real costs.
+- **Dart call receivers are typed from fields, parameters and locals** (#3610). On a public Flutter sample repository, call edges go from 979 to 1,086 with no edge lost.
+- **Swift has a complexity map** (#3450). Swift files get function rows (CCN, nesting, cognitive complexity, parameters) and class rows (methods, fields, LCOM4, TCC), and the markers derived from them.
+- **Pascal performance loops say whether they grow with the data** (#3517), including `while not Q.Eof` loops over a data set opened in place.
+- **Refactoring plans carry test commands for Go, Rust, JVM, Ruby and C#** (#3585, #3583, #3613). `go test`, `cargo test -p`, Maven and Gradle module tests, `bundle exec rspec` or `rake test`, and `dotnet test` on the owning test project or solution, stored on the plan in `validation.test_runs` alongside the JS/TS commands so batches rebuild them without a checkout.
+
### Changed
-- **Charts are in colour again, from one palette.** Every chart and share bar in the web UI draws from the same eight series colours, a commit type keeps one colour on every chart, health and risk charts keep their green, amber and red, heatmaps step through the accent orange, and chat charts sit on the conversation without a card around them.
-- **One provider order everywhere.** The CLI, `repowise serve` chat and jobs, and the MCP server now resolve provider, model and base URL as flag or UI choice, then `.repowise/config.yaml`, then the web UI's global default, then `REPOWISE_PROVIDER` / `REPOWISE_MODEL`, so `config.yaml` now wins over those env vars in the CLI. Choosing a model or base URL for a repo in the web UI writes that repo's `config.yaml`, which makes switching models on a local OpenAI-compatible server such as LM Studio a single edit. A base URL in `config.yaml` now beats `OPENAI_BASE_URL` and the other `*_BASE_URL` variables. The default provider and model saved in the web UI settings now also apply to CLI runs in repos whose `config.yaml` names none. A `config.yaml` base URL receives an API key from outside that repo's `.repowise/.env` only when it is a local address or was confirmed in Settings or with `repowise init`.
-- **Current model lists and prices.** Pickers offer GPT-6 Luna and Sol, Claude Sonnet 5.5 and Opus 5.5, Gemini 3.8 Flash and Gemini 4 Argon. DeepSeek now defaults to `deepseek-flash` and LiteLLM to `groq/openai/gpt-oss-120b`, since the old ids were retired. Cost estimates use current rates, and GPT-6 models get the same reasoning, temperature and chat tool handling as GPT-5.6.
+- **Code Health serves every language, with a Preview label where precision is still being measured** (#3867, #2921, #3877). Every finding, refactoring plan, performance cause and dead-code row is served by default; on a language whose layer measured below the precision bar, it carries a preview note with its latest hand-judged measurement (a badge with the measurement in its tooltip on the web, a `preview` field in REST, one compact `_meta.preview` entry in MCP, one line in the CLI). Health findings ship normally on Java, C# and C, each measured at 92.5% or more correct or debatable on a blind sample. Queue counts report language-held rows in a `gated` field.
+- **History markers on production files are context, not defects** (#3867, #3840). Git-history-only markers (ownership, churn and similar) leave the default defect lists and are counted under `history`, while scores, KPIs, `get_risk` and the work queue still use them. Findings on vendored and generated files and history markers on test files are held at serving, and `include=["unverified"]` shows all of them. Long parameter lists leave out parameters bound by framework annotations such as `@PathVariable`.
+- **The Code Health map, file drawer and trend read clearly at any size** (#3879). The map is drawn on canvas with zoom, pan and a Fit control, files circle-packed by folder inside each module, dots in the five score bands, and "Draw more" up to 8,000 files with vendored and generated files behind a toggle. The non-modal drawer opens on the score, one plain sentence and the top three issues with vital signs, with one primary action. The trend chart has a hover and keyboard readout and a movers list.
+- **Charts draw from one palette** (#3871). Every chart and share bar in the web UI draws from the same eight series colours, a commit type keeps one colour on every chart, health and risk charts keep their green, amber and red, heatmaps step through the accent orange, and chat charts sit on the conversation without a card around them.
+- **One provider order everywhere** (#3847). The CLI, `repowise serve` chat and jobs, and the MCP server resolve provider, model and base URL as flag or UI choice, then `.repowise/config.yaml`, then the web UI's global default, then `REPOWISE_PROVIDER` / `REPOWISE_MODEL`, so `config.yaml` takes precedence over those env vars in the CLI. Choosing a model or base URL for a repo in the web UI writes that repo's `config.yaml`, which makes switching models on a local OpenAI-compatible server such as LM Studio a single edit. A base URL in `config.yaml` takes precedence over `OPENAI_BASE_URL` and the other `*_BASE_URL` variables. The default provider and model saved in the web UI settings also apply to CLI runs in repos whose `config.yaml` names none. A `config.yaml` base URL receives an API key from outside that repo's `.repowise/.env` only when it is a local address or was confirmed in Settings or with `repowise init`.
+- **Current model lists and prices** (#3868). Pickers offer GPT-6 Luna and Sol, Claude Sonnet 5.5 and Opus 5.5, Gemini 3.8 Flash and Gemini 4 Argon. DeepSeek defaults to `deepseek-flash` and LiteLLM to `groq/openai/gpt-oss-120b`, matching what those providers serve today. Cost estimates use current rates, and GPT-6 models get the same reasoning, temperature and chat tool handling as GPT-5.6.
+- **Sync shows its progress and explains a failure** (#3838). Sync and full re-index from the dashboard show progress, and a failed or partial run stays on screen with the reason (a rejected key, rate limit, unreachable base URL or missing model) and Retry, Provider settings and Dismiss actions.
+- **Git history reads the newest 5,000 commits by default** (#3833), up from 500, so churn, hotspots, co-change, Change Records, suspects and 90-day counts cover a real span of history on active repositories. The co-change window follows it. An existing index keeps the `commit_limit` its `config.yaml` records (`init` wrote 500 before 0.57), and `update` names that value once; set `commit_limit: 5000` there to read the wider window.
+- **AI shares are reported with coverage** (#3732). `/commits/agent-trend` returns per-label counts, `coverage_pct` and `agent_pct_of_covered` in place of `agent_pct`, the authorship filter gains `unknown` and `human` means human-attested, `get_context` ownership carries one `agent_share` summary in place of `agent_authored_pct`, and AI figures are reported per file, component and repository.
+- **Extract Method plans leave the helper's name to whoever applies them** (#3588). The header, call and stage chaining use a placeholder (`_extracted_helper`, `extractedHelper`, numbered for later stages) with one note to rename it. Judged blind on 107 real refactorings from 19 repositories, names chosen by the applying agent were accepted about 74% of the time. Plan ids are unchanged.
+- **Fix first orders by the function's own change history** (#3565). Inside a value band, items are weighted by how many commits changed the lead function, and the reason names that history ("function changed in 38 commits").
+- **Fix first leads with the stored plan its first step lifts** (#3582, #3662), titled "Split X into N helpers" with "(more stages needed)" when the plan alone leaves the function above the break-up bar, and the dashboard card opens that plan. A Break up reason says what the split buys (#3581).
+- **Change risk leads with the size percentile** (#3664). `repowise risk`, the CI markdown and `get_change_risk` open with "Size and spread: Nth percentile of recent commits (diff size, not a bug predictor)", then the touched files' bug-fix record. The plugin's risk command and change review skill follow the new wording.
+- **`get_answer` grades `confidence` on whether the top hit covers the question** (#3716). `retrieval_quality` moves behind `include=["diagnostics"]`.
+- **Repository health headlines state their sample** (#3641, #3653). A band such as "Excellent" is printed only when at least half of the code files were analysed, each headline says "analysed N of M code files" when some were left out, and every surface names the same worst file and worst test as `get_health`.
+- **The dead code tab leads with what is safe to delete** (#3884), with the flagged count as a secondary sentence and `safe_to_delete_count` on the summary endpoint.
+- **Change risk and suspects answer faster on a running server** (#3925, #3927, #3928). A `get_change_risk` finding drill-down returns in under a second (about 5 s before), test selection reuses its per-file parsing across calls (`get_change_risk` and `get_risk` PR mode about 25% faster), and suspects reads each change's git text once per server (a warm call drops from about 6 s to under 1 s).
+- **Bug-fix commits are recognised in more forms** (#3567). `Fixed`, `Fixes`, `Fixing`, `hotfix`, `bugfix` and `Fixes #N` count as bug fixes.
+
+### Fixed
+
+- **Change Records, events and components.** The reaching-tests checklist item asks for a look only on a measured absence, and partly-known items carry counts (#3814). Component snapshots are taken on repositories with git owners (#3808), contract events are measured after the cross-repository pass extracts contracts (#3861), and derived components with colliding names are qualified by their parent (#3809).
+- **Chat.** Charts and tables cite results from earlier turns, and setup or provider failures end as a readable chat error (#3834). A chart field that plays two roles draws one column (#3865), a new conversation keeps a bare URL (#3576), and taps pass through the hidden conversation row toolbar (#3764).
+- **Graph, Java.** Same-arity overloads, enum-constant methods, anonymous-class methods and `@interface` elements get their own nodes (#3616, #3624, #3670). Overloads are chosen by literal argument types, arity against inherited overloads and the declared types of named arguments, and a tie never lands on an overload that cannot take the call (#3672, #3704, #3625). Call chains, inherited fields, `super` and cast receivers are typed, `S.super.m()` resolves, a member type shadows a same-named import, and the same-package tier offers only the right class's method (#3623, #3671, #3669, #3620).
+- **Graph, Kotlin.** Overloads and same-named extensions get their own ids, and calls whose only argument is a trailing lambda are call sites, including a local assigned from one (#3766, #3783, #3785). Extension calls resolve on a typed receiver and only with the receiver in scope, operator `invoke` binds, multiplatform calls bind only to declarations their source set sees, alias imports bind by alias, and imports of top-level functions and properties resolve (#3707, #3681, #3733, #3831, #3607, #3407, #3737). Constructor properties type receivers, parameters shadow a bare call, and a property is never a bare call's callee (#3609, #3679, #3680).
+- **Graph, Swift, Dart and Python.** Kotlin, Swift and Dart locals are typed from the call that assigns them (#3734). Swift stored properties type receivers, a Swift extension is not a constructible class, a subscript read is not a call, and optional-binding call assignments resolve (#3609, #3619, #3618, #3768). Dart named constructors bind, chained calls are typed by return type, and chains of three or more links resolve (#3701, #3794). Python receivers are typed through properties and returned objects, literal lazy exports are recognised, and test paths anchored at `Path(__file__)` ancestors resolve (#3666, #3570, #3518).
+- **Graph, general.** A module-alias call resolves to the module's top-level name only (#3617), name-only call tiers stay inside the caller's build (#3682), and C++ project export macros are discovered in headers beside target sources (#3706).
+- **Ingestion.** Every module of a Groovy `settings.gradle` include is read and relative Gradle module paths resolve (#3626, #3587). `!` negation rules re-include pruned directories (#3563), Unity state directories are skipped only inside a Unity project (#3866), and C# files in test projects are test material (#3586). Shallow-clone boundary lines are left out of blame ownership (#3073), and suggested reviewers are weighted by each author's own recent commits (#3074).
+- **Code origin.** Dart SDK headers under `dart-sdk/` are vendored, SwiftPM version-specific manifests are build files, Visual C++ resource headers and Dart codegen, minified and webpack output are generated (#3652, #3841, #3842, #3637).
+- **Health metrics.** Declared parameters are counted consistently across languages (#3848), a try block is not a nesting level (#3648), anonymous-class members roll up to their named owner (#3643), C# type arguments stay out of callee names (#3475), and the catch variable is a def in the Java, C# and C++ dataflow dialects (#3483). AVA's `t.*` assertions count in JS/TS tests (#3674).
+- **Health findings.** `ownership_risk` says which rule fired, files under 40 code lines are capped at low, and test-file findings rank after production ones (#3656). A flat boolean chain holds at low in `complex_conditional` (#3665), `developer_congestion` requires recent commits (#3675), sweep commits and inheritance stay out of hidden coupling (#3686), a keyed loop call clears `key_unused` for its line (#3539), and a C# `using` declaration stays with the code it guards (#3463).
+- **Health surfaces.** A repository with no hotspot files reports hotspot health as null in the trend, snapshots and an empty history, and the trend view says so (#3684, #3705, #3713). `get_health` file rows account for every point their score lost, `gap_analysis` agrees with the gap, and plan steps carry no stray `\r` (#3683). Queue counts count a language-held unit once (#3667), every performance finding states its queue reason (#3612), and example-named packages with a production origin stay in Fix first (#3629). Fix first item detail stays about the item itself (#3693), and `--refactoring-targets --recompute` plans carry their findings (#3521).
+- **Refactoring and dataflow.** Extract Method never plans a span over match arms and binds pattern captures (#3782). A write that may not run does not cover a later read (#3589), a write in a TypeScript, Go or Python switch arm is a may-def (#3522), a grouped Go `var` declares its names and taking a Go variable's address is a write (#3472, #3474), and Rust `use` declarations are not variable reads (#3575). Performance rows that are the recommended idiom or stated intent are dropped (#3611).
+- **Dead code.** C# classes found by assembly scanning or MEF, Swift cross-file uses and Java classes named in resources are reachable (#3832). Kotlin operator functions are contract methods, Compose previews and Dagger/Hilt modules are framework-loaded, Gradle and Android convention plugins, test modules and manifests are entry roots, and a module with a program `main` is run (#3695, #3661, #3657, #3645). A co-change edge is not an importer in JVM, Go and C++ reachability (#3658), generated files read as unindexed users (#3639), packages that import their own directory are linked (#3884), and empty safe-only views and withheld `unused_internal` rows say why (#3646, #3668).
+- **Security.** History findings are deduplicated across file versions (#3631), the repository's `.gitleaks.toml` path allowlist is honoured (#3709), other scanners' inline allow markers are honoured, generated, vendored and `.d.ts` files are scanned for secrets only, and sinks in scripts, tools and docs examples are low (#3685). Uppercase identifier values and `__html` type keywords in type positions stay quiet (#3420, #3687).
+- **Public API.** Exported Go identifiers outside `internal` packages and Java and Kotlin public API in published modules are flagged (#3537, #3577).
+- **Change risk.** Repowise's own output stays out of working-tree change risk and test selection, untracked files count the same everywhere, and text templates are data (#3712, #3770, #3767). Every per-file block is scoped to `include_paths`, given as a list or a string (#3730, #3698), the indexed commit is read through one resolver (#3708), the health delta matches findings by identity across renames, line shifts and centrality changes (#3715), the overlap block counts only fixes before the change (#3632), MCP says which checkout and commit it read (#3719), and a missing `git` is named (#3659).
+- **Test selection.** A conftest reading a literal constant or calling a self-contained function reaches only its module, and type-only conftest imports are ignored (#3731, #3772, #3633). A comment or docstring mention does not name a file (#3720), prose suffixes follow the documented extensions (#3729), tests reached through a package barrel are seen (#3651), `@SpringBootTest` integration tests run with every selection (#3636), only the base side of the index gap counts (#3628), and a second call shares a running selection (#3727).
+- **Coverage.** Files changed since a stale coverage report carry no figures (#3735), and any unapplied gate gives way to the project verdict (#3519).
+- **MCP.** Freshness and live files are read from the served checkout (#3644). Caller definition lines are checked live and symbol search folds plurals (#3741), reference edit sets are complete for Go, Java and Kotlin packages (#3642), `Class.method` and `Class::method` targets resolve with no file (#3635), a missed `get_context` target names the nearest symbols (#3638), tree-sitter query and history-tier files are classed as what they are (#3723), `used_by` and search notes agree with their payload (#3699), and `get_risk` states its churn rank as a rank (#3560).
+- **`get_answer` and search.** Retrieval reaches function bodies by rare terms and literals, a class's constructors count as part of the class, a project-name word or directory name carries no extra weight, and a body named only as context is served as evidence (#3736, #3773, #3771). A value is extracted only for the constant the question names, and each file appears once in `best_guesses` (#3700, #3673). Hybrid search scores symbols on content words, and code-punctuation literals are scanned and kept out of path mode (#3677, #3721).
+- **`get_why`.** A target is governed only by exact scope with the reason worded from its basis, rationale comments rank by weighted coverage, commits are deduplicated by full sha, `git_log` is capped at five, and an index with no accepted decisions or a missing path says so (#3769, #3724, #3726, #3655, #3654).
+- **CLI.** `repowise risk` reports git's message for an unknown ref (#3622), `repowise why` prints each history commit once (#3608), `repowise doctor` notes a Claude Code MCP entry that serves another repository (#3649), a keyless index reads as complete and init, status and `get_answer` name the keyless upgrade commands (#3634, #3143), and `generate --unwritten` seeds from model-written pages only (#3811).
+- **Distill.** Verbose `go test` runs keep their failure messages (#3627), and `git log -n` is honoured with each commit's author (#3660).
+- **Providers and integrations.** The default Ollama embedding timeout scales with the batch size (#3578), and OpenCode CLI v2 is supported (#3572).
+- **Decisions.** `superseded_by` is validated against the repository's own decisions (#3748).
+- **Web UI.** The docs Export menu opens above the header (#3778), MetricCard labels and descriptions render as blocks (#3875), UI copy uses correct singulars, ordinals and field names (#3465), charts share one median helper and one effort label map (#3561), and UI components fill in summaries and states when a host omits them (#3566).
+- **Upgrades.** The chat sessions migration is chained after Change Records (#3763), REST responses carry `preview` only on preview cells (#3877), and one shared `git cat-file --batch` reader serves every analysis consumer (#3702).
+- **Release-day hardening.** Suspects runs its git reads off the MCP stdin pipe, so it answers promptly on every platform (#3888), and `get_change_risk` accepts only revisions, never git options (#3893). An oversized omission ref reads through page by page (#3899), the MCP handshake reports the repowise version (#3900), `get_overview` names unknown `include` values in `ignored_arguments` (#3916), and dead-code cross-repo notes list each consuming repository once (#3895).
+- **Index accuracy.** A symbol spotlight retires when its symbol leaves a live file (#3892), test-quality markers read the stamped test flag (#3898), replayed function hotspots are re-measured on upgrade (#3891), update keeps non-code co-change partners such as templates and stylesheets (#3896), git-ignored manifests stay out of package discovery (#3894), and src-layout packages are service boundaries (#3897).
+- **CLI.** `repowise changes show` accepts the forge ref `changes list` prints (#3904), `status` sync totals agree with the pages table (#3889), `doctor` leaves tombstoned pages out of store reconciliation (#3907), distill runs a forward-slash program path on Windows (#3918), and SyntaxWarnings from analysed Python stay off the console (#3890).
+- Internal: the contract-facts refresh and the C# and Swift dead-code passes are split into helpers, and unused code is removed (#3863, #3846, #3538, #3883, #3417, #3339, #3795, #3774, #3696).
+
+### Documentation
+
+- Layer pages for AI attribution and Change Records (#3775), and every layer page rewritten as a scannable present-tense guide with method detail in the architecture docs (#3777).
+- The benchmarks page is rewritten for readers new to repowise, with October scores (#3640).
+- Language support lists class metrics for Dart, F# and Objective-C (#3479), and the architecture docs say semantic search uses LanceDB on every SQL backend (#3155).
+
+### Dependencies
+
+- Core: `tree-sitter-swift` pinned to `>=0.7.4,<0.8` (#3647).
+- Web: the unused `recharts` 2 dependency is removed; charts use recharts 3 from the UI package (#3780).
+- Security updates: fsspec 2026.9.0, Mako 1.4.3, multidict 6.9.1, source-map-js 1.2.2, postcss-selector-parser 7.1.6 and KaTeX 0.18.4 (#3887).
## [0.56.0] - 2026-10-12
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 0afb66eec..a2d3b4bd0 100644
--- a/packages/core/src/repowise/core/upgrade/_data/release_stats.json
+++ b/packages/core/src/repowise/core/upgrade/_data/release_stats.json
@@ -19,24 +19,24 @@
"test_files_new": 158,
"issues_closed": 76
},
- "unreleased": {
+ "0.57.0": {
"since": "0.56.0",
"days": 3,
- "prs": 205,
- "contributors": 24,
- "first_time_contributors": 11,
- "files_changed": 1226,
- "lines_added": 103206,
- "lines_removed": 11127,
+ "prs": 264,
+ "contributors": 41,
+ "first_time_contributors": 25,
+ "files_changed": 1421,
+ "lines_added": 123474,
+ "lines_removed": 15118,
"types": {
- "fixes": 147,
- "features": 45,
- "perf": 0,
- "refactors": 4,
- "docs": 6
+ "fixes": 192,
+ "features": 51,
+ "perf": 3,
+ "refactors": 5,
+ "docs": 7
},
- "test_files_touched": 437,
- "test_files_new": 144,
- "issues_closed": 25
+ "test_files_touched": 504,
+ "test_files_new": 168,
+ "issues_closed": 53
}
}
diff --git a/packages/server/src/repowise/server/__init__.py b/packages/server/src/repowise/server/__init__.py
index 7e1b095e6..ef72af829 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.56.0"
+__version__ = "0.57.0"
diff --git a/packages/vscode/CHANGELOG.md b/packages/vscode/CHANGELOG.md
index 2e03b01e8..a7dd1bb7b 100644
--- a/packages/vscode/CHANGELOG.md
+++ b/packages/vscode/CHANGELOG.md
@@ -7,6 +7,56 @@ 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.12.0
+
+Every dashboard now shares one set of states, palette and controls, Code Health
+gets a clearer map with a file drawer and trend, refactoring plans carry their tests, decisions and consumers,
+and the extension follows your VS Code theme more closely.
+
+**Requires repowise 0.47.0 or newer.** The minimum has not moved. The "No dead
+code" confirmation in the Dead Code tree needs repowise 0.56.0 and reads "Not
+analysed yet" on an older server; agent prompts for refactoring plans come from
+the server on 0.56.0 and are built locally on older ones.
+
+### Code Health
+
+- The map, file drawer and trend work for repositories of every size.
+- The headline band is held back when most code files are not analysed, so the
+ score only appears when it reflects the repository.
+- Fix first leads with work that pays, and each item carries its first step and
+ verify command. A plan-led finding opens its stored plan.
+- Repositories with no hotspot files say so plainly.
+
+### Refactoring
+
+- Extract Method plans can be staged across several helpers, each step with its
+ own verify, anchored by its first and last lines. The helper's name is left to
+ whoever applies the plan.
+- A plan can be exported as a recipe, and the agent prompt for a plan or
+ opportunity is rendered by the server so every surface hands an agent the same
+ text.
+- Plans list the tests that guard them and carry decisions, consumers, dead code
+ and recent edits.
+
+### Views and trees
+
+- Loading uses the thinking orb. Empty, not-yet, filtered and error states are
+ told apart across Code Health, Refactoring, Decisions and the sidebar trees,
+ and a failed tree row offers one click to retry.
+- The Dead Code tree says "Not analysed yet" until an analysis has run, then
+ "No dead code" with a pass icon.
+- Risk leads with the size percentile, and files changed since a stale coverage
+ report wait for a fresh report before showing coverage.
+- One chart palette and one share bar are used everywhere.
+
+### Docs
+
+- The docs Export menu opens above the header.
+
+### Theme and accessibility
+
+- Views follow your VS Code theme, with consistent names and accessible controls.
+
## 0.11.0
Code Health gets a shorter lede and a grey "Not analysed" state, markdown
diff --git a/packages/vscode/package.json b/packages/vscode/package.json
index 2f8a339b0..c069384d0 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.11.0",
+ "version": "0.12.0",
"publisher": "repowise-dev",
"license": "AGPL-3.0-or-later",
"homepage": "https://www.repowise.dev",
diff --git a/plugins/claude-code/.claude-plugin/plugin.json b/plugins/claude-code/.claude-plugin/plugin.json
index a20f59ee4..3ec315085 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.56.0",
+ "version": "0.57.0",
"author": {
"name": "Repowise",
"email": "[email protected]",
diff --git a/plugins/claude-code/CHANGELOG.md b/plugins/claude-code/CHANGELOG.md
index bbe20832c..baa21567b 100644
--- a/plugins/claude-code/CHANGELOG.md
+++ b/plugins/claude-code/CHANGELOG.md
@@ -2,6 +2,16 @@
All notable changes to the Repowise Claude Code plugin are documented here.
+## 0.57.0
+
+### Changed
+- `/repowise:risk` and the change-review skill lead with the change's size
+ percentile ("size and spread, not a bug predictor"), then the touched files'
+ bug-fix record (#3664).
+- The codebase-exploration skill reads `confidence` as whether the top hit
+ covers the question, with `retrieval_quality` behind
+ `include=["diagnostics"]` (#3716).
+
## 0.56.0
### Changed
diff --git a/plugins/codex/.codex-plugin/plugin.json b/plugins/codex/.codex-plugin/plugin.json
index 0ecee1458..016a9f22e 100644
--- a/plugins/codex/.codex-plugin/plugin.json
+++ b/plugins/codex/.codex-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "codex",
- "version": "0.6.1",
+ "version": "0.7.0",
"description": "Repowise codebase intelligence for Codex.",
"author": {
"name": "Repowise",
diff --git a/pyproject.toml b/pyproject.toml
index 160e4fa4f..43c3d1e8a 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -7,7 +7,7 @@ build-backend = "setuptools.build_meta"
[project]
name = "repowise"
-version = "0.56.0"
+version = "0.57.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 4f533b68b..bfbe77fc6 100644
--- a/server.json
+++ b/server.json
@@ -8,12 +8,12 @@
"source": "github"
},
"websiteUrl": "https://www.repowise.dev",
- "version": "0.56.0",
+ "version": "0.57.0",
"packages": [
{
"registryType": "pypi",
"identifier": "repowise",
- "version": "0.56.0",
+ "version": "0.57.0",
"transport": {
"type": "stdio"
},
diff --git a/uv.lock b/uv.lock
index d60269953..c1fd1b8c1 100644
--- a/uv.lock
+++ b/uv.lock
@@ -3114,7 +3114,7 @@ wheels = [
[[package]]
name = "repowise"
-version = "0.56.0"
+version = "0.57.0"
source = { editable = "." }
dependencies = [
{ name = "aiosqlite" },