Merge pull request #25 from Litenova-Solutions/feature/v4-finish

v4 finish: launch-ready public face, verification loop, and corpus-v2 benchmarks

Author: litenova

.cursor/plans/benchmark_agent_and_peer_layers_7c41fa92.plan.md

@@ -0,0 +1,37 @@
+name: Bug report
+description: Report incorrect behavior in Fuse CLI or MCP tools
+title: "[Bug]: "
+labels: ["bug"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      description: What did you expect, and what did Fuse do instead?
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Fuse version
+      description: Output of `fuse --version`
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      description: Commands, MCP tool calls, or a minimal repository layout
+    validations:
+      required: true
+  - type: dropdown
+    id: surface
+    attributes:
+      label: Surface
+      options:
+        - CLI
+        - MCP server
+        - Documentation
+        - Other
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,33 @@
+name: Feature request
+description: Suggest an improvement to Fuse
+title: "[Feature]: "
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem
+      description: What task is hard today with Fuse or without it?
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed behavior
+      description: What should Fuse do?
+    validations:
+      required: true
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - Verification (fuse_check)
+        - Retrieval / scoping
+        - .NET wiring graph
+        - MCP tools
+        - CLI
+        - Documentation
+        - Other
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -15,7 +15,7 @@ The server exposes a loop-shaped surface of eight tools, each one mental act, pl
 - **`fuse_context`** - emit scoped, reduced source with a semantic manifest and per-file provenance for selected seeds.
 - **`fuse_impact`** - blast radius for a symbol (callers, implementers, referencing types) from the persisted graph; also a NuGet upgrade break set via `package:{id,fromVersion,toVersion}`.
 - **`fuse_check`** - typecheck a proposed single-file edit and return the diagnostics it would produce, with repair packets on API-shape errors. The verification-grade ladder means it never shrugs: oracle-grade against the build-captured compilation when tier-1 is available, else build-grade by running `dotnet build` scoped to the owning project, abstaining only when even the toolchain cannot run.
-- **`fuse_test`** - run the covering tests for a symbol (the tests that reach it through the persisted `tests` edges), scoped by filter so the whole suite never runs.
+- **`fuse_test`** - run the covering tests for a symbol (the tests that reach it through the persisted `tests` edges), scoped by filter so the whole suite never runs. Candidate racing (`candidates`): speculatively typecheck several proposed single-file edits against one resident compilation and get a per-candidate verdict plus a winner by strict dominance (a clean candidate beats any with errors; ties reported), so an agent weighing plausible fixes learns which survives without picking on vibes.
 - **`fuse_refactor`** - compiler-executed, verify-gated refactors staged as a diff: rename, add/remove/reorder-parameter, add-cancellation-token, extract-interface, move-type, apply-codefix. Each recompiles and returns the diff only when no new diagnostic is introduced, else abstains.
 - **`fuse_review`** - diff-first change impact and packed context, opening with a public API delta and carrying a paste-ready PR handoff packet (`handoff=true`) gated on a clean check session.
 - **`fuse_reduce`** - compact a known set of files or raw content; the one utility outside the loop.
@@ -24,7 +24,7 @@ The MCP server also exposes playbook prompts (anchored plans that teach the veri
 
 ### Verification and honesty
 
-- **The verification-grade ladder.** Every `fuse_check` answer is stamped `oracle` (a speculative in-memory typecheck against the tier-1 build-captured compilation), `build` (the real `dotnet build` toolchain scoped to the owning project, parsed into the same shape), or `abstain` (only when even the toolchain cannot run, always naming the missing prerequisite). The build-grade path never writes the working tree; it mirrors the owning project to a temporary directory with the one file replaced and project references rewritten to absolute paths.
+- **The verification-grade ladder.** Every `fuse_check` answer is stamped `oracle` (a speculative in-memory typecheck against the tier-1 build-captured compilation), `build` (the real `dotnet build` toolchain scoped to the owning project, parsed into the same shape), or `abstain` (only when even the toolchain cannot run, always naming the missing prerequisite). The build-grade path never writes the working tree; it mirrors the owning project to a temporary directory with the one file replaced and project references rewritten to absolute paths. Because a rehydrated compilation is analyzed, never emitted, strong-name signing is neutralized before its diagnostics are read, so a captured relative key-file path that does not resolve in the rehydration sandbox never surfaces as a spurious signing error (CS7027) nor drops a cleanly building strong-named repository below tier-1.
 - **Delta mode and persisted sessions.** Pass a `session` id with no content and `fuse_check` returns the diagnostics your on-disk edits introduced or resolved since the session baseline. Baselines persist to the store, so a restarted process resumes intact; `markGreen` resets the baseline and `full` returns the whole current set. Delta mode never runs a build; it reads whole-state diagnostics from a live resident workspace and abstains when none serves the root.
 - **Repair packets.** An API-shape diagnostic (a missing member, an unknown type, a missing argument, a wrong-type assignment) carries a machine-applicable fix (the offending token and the nearest recorded name to substitute), rendered as an `apply: replace 'X' with 'Y'` line, drawn from the persisted symbol table so the fix costs no round-trip.
 - **Analyzer and nullable parity.** When a resident workspace serves the root, `fuse_check` also runs the repository's configured analyzers and nullable warnings against the overlay at the editorconfig severities, so a green check matches what CI's build step enforces. On by default for the single-file verify, off for the hot per-edit delta path.
@@ -46,7 +46,7 @@ One `fuse host` daemon per repository can hold the resident workspace as a share
 
 - **The persistent index.** A single SQLite database at `.fuse/fuse.db` (WAL mode) holds files, projects, symbols, chunks, a typed semantic graph, routes, and an FTS5 full-text index. The workspace loads through MSBuild and Roslyn with a syntax-only fallback; re-indexing is incremental per changed file, and no read tool serves silently stale data (a warm store is reconciled against the current on-disk content before it answers).
 - **The wiring analyzers.** The semantic analyzers resolve DI registration and constructor injection (including keyed DI), MediatR request-to-handler, ASP.NET route-to-action, options binding, EF Core, Scrutor decoration, factory and hosted-service registration, pipeline behaviors, minimal-API, gRPC, and SignalR. Persisted `references` and DI-resolved `tests` edges back `fuse_impact` and covering-test selection.
-- **Retrieval.** A deterministic lexical channel (BM25F over the FTS5 table) with offline subword, stem, and comment bridges plus dependency-centrality and git co-change priors. No model is fetched or shipped. Ranked task localization is the fallback mode; the precise path is an anchor (symbol, route, service, request, config, git base) resolved through the graph.
+- **Retrieval.** A deterministic lexical channel (BM25F over the FTS5 table) with offline subword, stem, and comment bridges plus a dependency-centrality prior. No model is fetched or shipped. Ranked task localization is the fallback mode; the precise path is an anchor (symbol, route, service, request, config, git base) resolved through the graph. The git co-change prior is off by default: its semantic-mode re-adjudication on corpus v2 recorded it as net-negative to ranking (MRR 0.434 with the prior versus 0.489 without), so it was dropped from the shipping default; the ranking gate keeps it measured behind a diagnostic config.
 - **Multi-language syntax tier.** A provider seam drives the syntax tier; C# is first-party, and Python and JavaScript/TypeScript are supported at the syntax tier. Each indexed file carries a `language` tag. The deep typed graph is C#/Roslyn only.
 - **Tier-1 build capture is default-on and the worker is bundled.** The oracle is the product: the build-capture worker ships inside the global tool (under `build-capture/` beside `fuse`) and is discovered with no configuration, and tier-1 build capture is attempted by default. It degrades cleanly when no build target exists or a build fails (to the MSBuild and syntax tiers), and opts out with `FUSE_BUILD_CAPTURE=0`. In `fuse mcp serve` the cold start is syntax-first with a supervised background upgrade to the semantic/tier-1 graph, so the first reads return in seconds while the build runs behind them; the availability header names when a build is running for tier-1, and `FUSE_BG_UPGRADE=0` opts back into a synchronous first read. `fuse index` on the CLI is always synchronous.
 - **Portable capture bundles.** `fuse capture --out <bundle>` builds once and packages the compiler log, the extracted graph, and a versioned manifest; `fuse index --from-capture <bundle>` rehydrates the semantic graph and answers `fuse_check` at oracle grade on a machine that cannot restore or build, with no build. The bundle never ships the MSBuild binary log, and a planted secret fails the capture closed. An in-repo GitHub Action captures a bundle on `main`. `fuse capture --merge <dir>` assembles a bundle from per-project fragment binary logs (a build-target channel), equal in extracted graph to a direct capture; the bundle format is backward-compatible (a newer Fuse reads an older bundle; a bundle newer than the running Fuse is refused with an actionable message).