feat(javascript): return a retained summary view on request (#1568)

analyze_javascript_application returns the complete application graph
inline, which repeats tens of kilobytes even for a few source lines and
exceeds the default 10 MiB MCP frame for a 300-function source file.

The new optional detail input keeps complete delivery by default. With
detail "summary" the server records the complete analysis Evidence in
the session and returns its inspect_analysis_view summary, whose
parent_evidence_id lets callers page modules, select items, or pass the
retained reference to application workflows. A server without Evidence
retention refuses summary detail with capability_unavailable rather
than returning a summary whose analysis cannot be reached.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

docs/javascript-artifact-reconstruction.md

@@ -129,6 +129,16 @@ documents. Their runtime string-limit failures report a resource constraint
 with the selected path, observed bytes and UTF-16 limit, rather than malformed
 JSON.
 
+`analyze_javascript_application` returns the complete analysis Evidence by
+default. Select `"detail": "summary"` to retain that complete Evidence in the
+current session and receive only its `inspect_analysis_view` summary: artifact
+identity, statistics, Electron surface counts, application and semantic
+coverage, limitations, and `normalized_result.parent_evidence_id`. Pass that ID
+to `inspect_analysis_view` for module pages or items, or to the application
+workflows as a retained reference. The summary does not repeat or truncate the
+analysis; a server without session retention refuses summary detail with
+`capability_unavailable`. CLI output is unchanged and always complete.
+
 MCP prepares the complete repeated response incrementally against the pinned
 SDK's 10 MiB stdio receive-buffer budget. Oversized results return an actionable
 transport constraint and the exact same-session Evidence reference. Use

docs/mcp-contracts.md

@@ -318,6 +318,13 @@ Ordinary responses keep their existing complete result contract.
 
 ## Retained application Evidence inputs
 
+`analyze_javascript_application` accepts `detail`: `complete` (default) returns
+the complete analysis Evidence; `summary` records that complete Evidence in the
+session and returns the derived `inspect_analysis_view` summary Evidence
+instead. Its `normalized_result.parent_evidence_id` and `evidence_links` name
+the retained analysis, so later views and application workflows read it without
+repeating analysis or moving the complete graph through the response.
+
 `inspect_analysis_view` projects a caller-selected view of already completed
 `inspect_binary_layout`, `analyze_javascript_application`, or `analyze_function`
 Evidence. Native views select procedure, pseudocode, assembly, basic blocks,