chore: sync branch with latest main
This commit is contained in:
@@ -144,6 +144,13 @@ Start with the default result and use its inline Evidence and graph context.
|
||||
Do not repeat an identical tool call. Make a focused follow-up only when the
|
||||
returned result leaves a specific question unanswered.
|
||||
|
||||
If MCP reports `resource_constraint` with `details.resource: "transport"`, use
|
||||
its reported same-session Evidence reference with a focused application tool,
|
||||
or call `export_evidence_bundle` to write the complete session to a selected
|
||||
path. The analysis remains complete in the ledger; avoid repeating it merely
|
||||
to request the same oversized response. Complete CLI JSON output also streams
|
||||
without a single MCP frame.
|
||||
|
||||
Every conclusion must distinguish observations, inferences, and unknowns. Cite
|
||||
Evidence IDs, preserve limitations and incomplete coverage, and never imply
|
||||
that static analysis observed execution. Runtime requests execute the declared
|
||||
|
||||
@@ -2,10 +2,17 @@
|
||||
|
||||
Use `analyze_javascript_application` directly on the operator-supplied ASAR or
|
||||
extracted tree. The complete result, graph, and Evidence context are returned
|
||||
inline. Source-map contents are part of the static analysis. Start from its
|
||||
inline when they fit the MCP frame. Source-map contents are part of the static analysis. Start from its
|
||||
findings, coverage, unknowns, and graph context, then make a focused follow-up
|
||||
only when a specific question remains unanswered.
|
||||
|
||||
An oversized response reports `resource_constraint` and
|
||||
`details.resource: "transport"`. Reuse
|
||||
`details.reported_limits.evidence_reference` with `trace_application_feature`
|
||||
for the module or feature under investigation. `export_evidence_bundle` writes
|
||||
the complete canonical session to a caller-selected file. Both workflows keep
|
||||
the original Evidence and coverage; a broad follow-up can also exceed framing.
|
||||
|
||||
BrowserWindow preferences, preload and contextBridge surfaces, IPC
|
||||
registrations, utility processes, and native binding requests are static syntax
|
||||
observations. Only a unique exact literal IPC channel match supports an inferred
|
||||
|
||||
Reference in New Issue
Block a user