release: v0.43.0 (#1612)

Version bump across pyproject, the three package __init__ constants, the two
Claude Code plugin manifests and server.json, with uv.lock regenerated. The
lockfile also picks up tree-sitter-pascal, which #1353 added to pyproject
without relocking.

Changelog for the cycle, resynced into the bundled copy the whats-new panel
reads.

Plugin parity: four commands documented behaviour that has moved.
- risk now leads with fix history; the score measures diff size and spread,
  omitting the revspec scores uncommitted work, and --baseline / --target exist
- --no-editor-setup now also skips the four project-local files, and
  --save-key / --no-save-key are new
- decision add records from flags with no prompting
- why answers about --target, and refuses a question the store cannot answer
Edited in plugins/shared and re-rendered, so the Codex prompts move with them.

Codex plugin to 0.6.0: it shipped a hooks change this cycle. README language
count to 19 for Object Pascal.

Author: RaghavChamadiya

.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.42.0",
+      "version": "0.43.0",
       "category": "productivity",
       "keywords": [
         "codebase",

README.md

@@ -128,7 +128,7 @@ queryable from the CLI, the MCP tools, and the local dashboard.
 
 | Layer | What it gives you | Edge |
 |---|---|---|
-| **◈ Graph** | Dependency graph across 18 languages · file + symbol nodes · 3-tier call resolution · Leiden communities · PageRank and execution flows · route→handler edges across 22 frameworks | A real graph most tools never build |
+| **◈ Graph** | Dependency graph across 19 languages · file + symbol nodes · 3-tier call resolution · Leiden communities · PageRank and execution flows · route→handler edges across 22 frameworks | A real graph most tools never build |
 | **◈ Git** | Hotspots (decayed churn + activity floors) · ownership % · co-change pairs (hidden coupling) · bus factor · which files actually get bug-fixed, and how recently | Behavioural signals static analysis cannot see |
 | **◈ Docs** | A generated wiki page per module and file · rebuilt incrementally every commit · freshness and confidence scoring · hybrid search (full-text + vector) · selectable style and output language | Stays current instead of rotting |
 | **◈ Decisions** | Architectural decisions mined from five sources, evidence-backed, each traced to a verbatim source span and stamped exact / fuzzy / unverified | **★ Captured nowhere else** |
@@ -404,7 +404,7 @@ the orchestrators. Full matrix and the contributor recipe:
 
 ## Supported languages
 
-**18 languages parsed to AST · 13 at the Full tier · framework-aware across all of them.**
+**19 languages parsed to AST · 13 at the Full tier · framework-aware across all of them.**
 
 <p>
   <strong>Full tier &nbsp;</strong>
@@ -428,6 +428,7 @@ the orchestrators. Full matrix and the contributor recipe:
   <img src="https://img.shields.io/badge/Swift-F05138?style=flat-square&logo=swift&logoColor=white" alt="Swift" />
   <img src="https://img.shields.io/badge/PHP-777BB4?style=flat-square&logo=php&logoColor=white" alt="PHP" />
   <img src="https://img.shields.io/badge/Dart-0175C2?style=flat-square&logo=dart&logoColor=white" alt="Dart" />
+  <img src="https://img.shields.io/badge/Delphi-EE1F35?style=flat-square&logo=delphi&logoColor=white" alt="Object Pascal / Delphi" />
   &nbsp;<strong>· Partial &nbsp;</strong>
   <img src="https://img.shields.io/badge/Luau-00A2FF?style=flat-square&logo=lua&logoColor=white" alt="Luau" />
 </p>

docs/CHANGELOG.md

@@ -16,4 +16,4 @@
 # is already UTF-8.
 _ensure_utf8_stdio()
 
-__version__ = "0.42.0"
+__version__ = "0.43.0"

packages/cli/src/repowise/cli/__init__.py

@@ -24,7 +24,12 @@ sources and tracks them for staleness and conflicts. This command drives the
 - **show** — `repowise decision show <id>` — full record: rationale, evidence
   spans, status, and the supersession lineage.
 - **add** — `repowise decision add` — guided interactive capture (~90s). Use when
-  the user makes a decision during the session and wants it recorded.
+  the user makes a decision during the session and wants it recorded. With both
+  `--title` and `--decision` it records without prompting and prints the id
+  (`--format json` to parse it back), which is the form to use with no terminal.
+  The rest are optional: `--context`, `--rationale`, `--alternative`,
+  `--consequence`, `--affects`, `--tag`, the last four repeatable. A flag-driven
+  record lands `proposed` for a person to `confirm`.
 - **confirm** — `repowise decision confirm` — review decisions auto-proposed from
   git history and accept or reject them.
 - **deprecate / dismiss** — `repowise decision deprecate <id>` (optionally
@@ -35,5 +40,6 @@ sources and tracks them for staleness and conflicts. This command drives the
 - For *querying* why code looks the way it does mid-task, prefer the `get_why`
   MCP tool (the `architectural-decisions` skill) — it returns lineage and an
   alignment score. This command is for *managing* the decision records themselves.
-- `add` and `confirm` are interactive; tell the user when a step needs their input.
+- `confirm` is interactive, and so is `add` unless you pass `--title` and
+  `--decision`; tell the user when a step needs their input.
 - If unsure of an exact subcommand or flag, run `repowise decision --help`.

packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-decision.md

@@ -96,11 +96,22 @@ Git:
   --follow-renames       Track files across renames (slower but more accurate history)
 
 Editor integration:
-  --editor-setup /       Register (default) or skip the global MCP server entry
-  --no-editor-setup      and Claude Code hooks in ~/.claude/settings.json and
-                         Claude Desktop's config, plus the distill rewrite-hook
-                         offer. There is one 'repowise' MCP entry per config, so
-                         a later init from another repo repoints it. See Step 3b.
+  --editor-setup /       Wire repowise into your editors (default), or skip it
+  --no-editor-setup      entirely. Covers both halves: the machine-wide config
+                         (~/.claude/settings.json, Claude Desktop's config, the
+                         Claude Code hooks, the distill rewrite-hook offer) and
+                         the project-local files (.mcp.json, .claude/CLAUDE.md,
+                         .vscode/mcp.json, .vscode/extensions.json). With
+                         --no-editor-setup only .repowise/ is touched. There is
+                         one 'repowise' MCP entry per machine-wide config, so a
+                         later init from another repo repoints it. See Step 3b.
+
+Keys:
+  --save-key /           Save the provider key this run authenticated with to
+  --no-save-key          .repowise/.env (gitignored, owner-only). Default: on,
+                         so the MCP server can answer later without the shell
+                         that set it. Use --no-save-key in CI or on a shared
+                         machine.
 
 Output:
   --no-claude-md         Don't generate/update CLAUDE.md
@@ -122,8 +133,10 @@ Then ask if they want you to construct a command or if they'll handle it.
 Every path reaches this step. It is about the repo, not the provider.
 
 By default `init` registers repowise as the user's global MCP server, in
-`~/.claude/settings.json` and Claude Desktop's config. There is **one**
-`repowise` key in each file, so this repo replaces whatever repo is registered
+`~/.claude/settings.json` and Claude Desktop's config, and writes four
+project-local files into the repo (`.mcp.json`, `.claude/CLAUDE.md`,
+`.vscode/mcp.json`, `.vscode/extensions.json`). There is **one** `repowise` key
+in each machine-wide config, so this repo replaces whatever repo is registered
 now. That is the right default for the repo someone actually works in, and the
 wrong one for a checkout that is about to disappear.
 
@@ -138,9 +151,11 @@ Also add it if the user says they don't want their editor or MCP setup touched.
 Do **not** infer that from "just index it" or "don't ask me questions" — those
 are about prompts, not config.
 
-The index, the wiki, and every project-local file are identical either way.
-Only the machine-wide registration is skipped, and it can be done later by
-re-running `repowise init` in that repo without the flag.
+The index and the wiki are identical either way. What the flag skips is both
+the machine-wide registration and the four project-local files, so with it only
+`.repowise/` is touched. (`.repowise/mcp.json` is still written: it is what
+`repowise mcp .` prints, and it is how you opt back in.) Either half can be
+done later by re-running `repowise init` in that repo without the flag.
 
 Whichever you pick, say which in one line so the user can correct you.
 
@@ -218,10 +233,11 @@ After init completes successfully:
 3. Tell the user:
    - "Repowise has indexed your codebase. The MCP tools are now active — I can answer questions about your architecture, ownership, dependencies, and more."
      **Only if you did not pass `--no-editor-setup`.** With that flag nothing was
-     registered, so say instead: "The index is built. I did not register it as
-     your global MCP server (this looked like a temporary checkout). The
-     repowise plugin's tools still work here; to make this the repo the MCP
-     server points at, re-run `repowise init` without `--no-editor-setup`."
+     registered and nothing was written into the repo outside `.repowise/`, so
+     say instead: "The index is built. I did not register it as your global MCP
+     server and wrote no editor files into the repo (this looked like a
+     temporary checkout). The repowise plugin's tools still work here; to wire
+     it up properly, re-run `repowise init` without `--no-editor-setup`."
    - "Try asking me something like 'how does the auth module work?' or 'what depends on utils.py?'"
    - "Run `/prompts:repowise-status` anytime to check the health of your index."
    - "Run `/prompts:repowise-update` after making code changes to keep the wiki in sync."

packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-init.md

@@ -4,28 +4,33 @@ description: Score the defect risk of a change — a commit or a base..head rang
 
 # Repowise Risk
 
-Score a *change* (not a file) for defect risk. Repowise reads the diff shape —
-lines added/deleted, files, directories, subsystems, change entropy, and author
-familiarity — and returns a 0–10 score with an attributable driver breakdown.
-Pure git + learned constants: no LLM, no network. A natural pre-merge / PR gate.
+Score a *change* (not a file) for defect risk. The response leads with
+`fix_history`: the recency-weighted bug-fix record of the files the change
+touches, which of them carry it, and where that sits among the repo's own
+fix-bearing files. The 0–10 score sits beside it and measures diff size and
+spread (named in `score_measures`) rather than danger, so read the fix history
+first. Pure git + learned constants: no LLM, no network. A natural pre-merge /
+PR gate.
 
 ## Steps
 
 1. If `.repowise/` doesn't exist: "This repo isn't indexed yet. Run `/prompts:repowise-init` first." Stop.
 2. Resolve the target from `$ARGUMENTS`, run `repowise risk`, and present the
-   score, level, and top drivers — calling out *why* it's risky (e.g. wide
-   diffusion across subsystems, low author familiarity).
+   fix history first (which files keep breaking, and the repo-relative
+   percentile), then the score and its drivers.
 
 ## Choosing the revspec
 
-- No args → `repowise risk` (scores `HEAD`)
+- No args → `repowise risk` (scores uncommitted work, or `HEAD` when the tree is clean)
 - A commit SHA → `repowise risk <sha>`
 - A range / PR / branch → `repowise risk <base>..<head>` (e.g. `repowise risk main..HEAD`)
 
 Useful flags:
 - `--ext .py,.ts` — only count changes in those file types
 - `-x, --exclude <pattern>` — gitignore-style pattern to drop from the diff (repeatable; also honors a `.riskignore` file)
-- `--format json` — machine-readable score + features + drivers
+- `--format json` — machine-readable fix history + score + features + drivers
+- `--baseline <n>` — how many recent commits to rank the change against (0 disables)
+- `-t, --target <path>` — score what history says about named files instead of a change (repeatable; reads the index)
 - `--path <dir>` — point at a different git repo
 
 ## How this differs from the other risk views

packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-risk.md

@@ -24,8 +24,10 @@ command **queries** why something is shaped a certain way.
 - File path (governing decisions + origin story) → `repowise why src/api/auth.py`
 - Target-anchored search → `repowise why "why the retry cap?" --target src/api/client.py`
   (`--target` is repeatable)
-- No args → `repowise why` (decision-health dashboard: stale / proposed /
-  ungoverned hotspots)
+- `--target` with no question → answers about those files: one target behaves
+  like passing the path, several get a card each
+- No args and no target → `repowise why` (decision-health dashboard: stale /
+  proposed / ungoverned hotspots)
 - Machine-readable / raw payload → `--format json` / `--full`
 
 ```
@@ -40,8 +42,13 @@ tool-adapter commands.
 
 ## Notes
 
-- Falls back to git archaeology when a path has no decisions, so it is never
-  empty — call that out so the user knows it is reconstructed, not recorded.
+- A *path* falls back to git archaeology when it has no decisions, so it is
+  never empty — call that out so the user knows it is reconstructed, not
+  recorded.
+- A *question* the store cannot answer comes back with no decisions, one
+  sentence on why, and a pointer to the tool that fits the question's shape.
+  Relay the redirect rather than filling the gap: an empty result there means
+  the decision store has nothing, not that the question is unanswerable.
 - For *managing* ADR records (add / confirm / deprecate), use
   `/prompts:repowise-decision`.
 - Before contradicting an existing decision, surface it to the user first.

packages/cli/src/repowise/cli/agent_targets/_data/codex_prompts/repowise-why.md

@@ -6,4 +6,4 @@
 Namespace package: repowise.core is part of the repowise namespace.
 """
 
-__version__ = "0.42.0"
+__version__ = "0.43.0"