feat(session): add explicit provider registry and target binding

Introduce deterministic deep-provider discovery and immutable per-target routing while retaining disjoint artifact and native capability families.

Expose provider selection consistently through MCP, CLI, environment configuration, session status, prompt completion, typed diagnostics, and generated documentation. Preserve exact provider/profile provenance without request racing or transparent fallback.

Cover overlapping providers, ambiguity, rejection details, cancellation, restoration, package installation, and real Hopper target switching.
This commit is contained in:
N0zoM1z0
2026-07-15 22:13:48 +09:00
committed by N0zoM1z0
parent bd3cf964d6
commit 941d7101dd
174 changed files with 5370 additions and 648 deletions
+5 -4
View File
@@ -12,10 +12,11 @@ additively; Devin is reported but left unchanged.
Ghidra is the accepted direction for REA's second deep static-analysis provider,
but it is not shipped yet. The first implementation is planned as a bring-your-
own Ghidra and Java installation with read-only headless analysis, explicit
provider selection, isolated temporary projects, and truthful unavailable
capabilities. Setup must not install Java. Automatic Ghidra acquisition, if
added later, must remain a separately planned and approved related-tool change.
own Ghidra and Java installation with read-only headless analysis, the shipped
explicit provider selection and target binding, isolated temporary projects,
and truthful unavailable capabilities. Setup must not install Java. Automatic
Ghidra acquisition, if added later, must remain a separately planned and
approved related-tool change.
## Capability-selective setup